I have been trying to setup Docker in Windows Server 2016 in an AWS instance to run an IIS program.
From this question,
Cannot access an IIS container from browser - Docker, IIS has been setup inside a container and it is accessible from the host without port mapping.
However, if I want to allow other users from the Internet/Intranet to access the website, after Google-ing it, I guess we do need port mapping...
The error I have encountered in port mapping is given in the above question so... I guess using nat is not the correct option. Therefore, my team and I tried to create another network (custom/bridge) following instructions from
https://docs.docker.com/v17.09/engine/userguide/networking/#user-defined-networks
However, we cannot create a network as follows:
; Googled answer:
https://github.com/docker/for-win/issues/1960
My team guessed maybe its because AWS blocked that option, if anyone can confirm me, please do.
Another thing that I notice is: when we create an ECS instance in AWS,
So... only default = NAT network mode is accepted in Windows server?
Our objective: put the container hosted IIS application to Internet/Intranet in Windows Server 2016...
If anyone has any suggestion/advice, please tell me, many thanks.
Related
We are migrating to / experimenting with AWS. We have chosen Lightsail, as our needs are pretty simple and this seems like a great, simple, affordable option. With that said, we have hit an early roadblock! I cannot figure out how to setup SFTP (or alternatively FTPS) to transfer files to the server?!
FWIW, I am a total AWS newbie. I have searched fairly extensively, and there are troves of information on how to do this on Lightsail w/ Linux, but nothing on Windows.
On our existing infrastructure we simply set up a third party SSH server (it's called Bitvise - FYI), and opened port 22 for it (IP restricted, etc). We can then connect with our FTP client of choice (whether that be FileZilla or our IDEs, etc). However, the same approach did not work on our Lightsail instance (no idea why)!
Does anyone have any idea how to do this? Any assistance is hugely appreciated. Thanks!
I'm unfamiliar with this terrain, so if any one can guide me in a step by step manner- it would really help. My MySQL database sits on a AWS host X- "ec2-xxx-xxx-xxx-xx.compute-1.amazonaws.com". It is blocked to access from individual local machines and is usually accessed from another working server Y- "ec2-yy-yyy-yyy-yy.compute-1.amazonaws.com" through port '3306'. Now it is especially inconvenient to access this via terminal SSH every time and scripts while they run, its hard to prototype or build an elaborate app. I'd like to set up a SSH tunnel from my local to server Y to be able to access MySQL host X from my local machine, to run queries from my locally deployed Jupyter notebook as well as local working-in-progress Django web app.
The reason why I ask for something more step-by-step is that I have to port forward to another server hosting a redis database which again is accessible through a specific server only. So, I'll be able to carry the solution from here to there too. I'm willing to go into chat as well if needed, but I need to resolve this rather quickly. Thanks!
PS: I've tried many guides off of the internet, but nothing has worked, it's become clear to me that I'm missing some foundational understanding or pathway. That's why I'm here, trying to start from the ground.
I have a google VM. I got public as well for the same (using which I am RDP'ing to that VM). But when I am trying to access any webservice hosted in VM from outside world using ip:port, it is not connecting to that webservice.
To be more precise :
I have hosted a sample webservice using nodejs on port 8080.
I have tried accessing http://:8080 . No luck. But it is working with localhost:8080 inside VM.
I have googled about external ip etc, but all went out of my head. Can any one please help me how to resolve this issue ? do I need to make any config changes etc? if yes, could you please provide me the required steps.
Update :
I have created fire wall rule saying : port : allow all, target tags : all instances, IP : 0.0.0.,0/0 . even then it is not working.
OS : windows 10
As I understand, the GCP firewall rules are applicable on the network level. You might need to configure the virtual machine specific firewall rules (according to the OS you are using). For example, in CenOS you may need to use firewall-cmd commands to configure the internal firewall.
Finally solved this. All the time I was thinking to enable port in networks for google cloud, but the problem is at my windows firewall. once I disabled it, I could access my webserver from outside environment.
I've used the following guide in order to connect to a Debian 8 Server with GUI using a DigitalOcean server:
https://www.digitalocean.com/community/tutorials/how-to-set-up-vnc-server-on-debian-8
I know this works, however under Azure and now Google's Cloud Compute I am unable to connect. I think there should be some setting on Google's side that is blocking outside connections through VNC to the Debian 8 instance.
I only have the free support level, and I don't want to upgrade just to resolve this issue alone. Here is a screenshot from my console that perhaps has some relevant information:
Console Screenshot
I'd appreciate any input anybody could give me. I've tried trouble shooting this before under Azure, but after getting it to work on DigitalOcean, I know the problem isn't from my end.
The resolution was simple. I just had to allow the port tcp:5901 through Google's firewall in order to connect to my VNC server.
I have RAILO (Railo 3.1.2.001 final) installed on an AMAZON EC2 instance and everything seems to be working fine for the tests I have done. I can connect to mySQL and simple commands work. The applications I am planning to run on it make extensive use of CFFTP to pull files in from clients and process them. The OPEN command works fine and I get a succeeded in Active and Passive mode, but when I try to do anything (check for a file, put a file, download) I get : 500 Illegal PORT command.
My thought here is the AMAZON firewall is blocking some ports and something needs to be setup for this to function.
Anyone have any experience with this and can point me in the correct direction?
Thanks in advance,
Jeff
do you connect from outside amazon to the instance ? if you do check the security group and allow the ip/port for your application.