Port 80 not opened to my container after creating firewall rules

[Lucky Adogun]

Hi,

I have a container running Django, Nginx, and Gunicorn running on Compute Engine

I can successfully deploy and SSH into the VM but cannot access the external URL to the container despite creating several firewall rules.

It seems to be closed to port 80 even after exposing it from within the VM.

how do I fix this?

Here's a copy of my:

docker-compose file: https://codeshare.io/aJZBWd

NGINX conf: https://codeshare.io/5grWOB

Here's a similar step I followed in setting up the VM: https://stackoverflow.com/questions/60965622/why-is-google-compute-engine-not-running-my-container

Here's the error I get when I try to access port 80: curl: (7) Failed to connect to 35.XXX.XX.XXX port 80: Connection refused

[Jedihomer Townend]

I may be reading that wrong, but it looks like you are mapping port 1337 to 80 in your docker-compose file.

So although you have NGINX listening on port 80 (inside the docker) you are actually listening on port 1337 on the VM

[Lucky Adogun]

Yes. 1337 is mapped to 80. Visiting HTTP://my-external-ip:1337 doesn't return a proper response.

[Jedihomer Townend]

So I also assume that you've opened port 1337 in your GCP firewall rules?  From your initial email I read that as you've opened port 80 in the firewall...

[Lucky Adogun]

Thanks. Yes, I have that port opened as well.

[Wilfred L. (Cloud Platform Support)]

Hi, your nginx file has the following line:

listen [::]:80 ipv6only=on;

Have you tried remove it?

[Lucky Adogun]

Yes. I've removed it. Made changes and tested locally - which works.

Updated the image on Artifact Registry and the VM.

Here's what I get when I SSH into it and checked the journalctl logs: 

konlet-startup.service: Main process exited, code=exited, status=1/FAILURE

konlet-startup.service: Failed with result 'exit-code'

Any clue what may be wrong as the container isn't running?