First of all, why do you start the container by your own docker command? The launcher script will do it after a successful rebuild/bootstrap. Many people do it in that way without issue.

And what’s the point of mention python -m BaseHTTPServer 80 works OK? Your docker command mapped external port to 8080, which has nothing to do with whether 80 is accessible. You firewall may still blocking 8080.

What hosing provider are you using? Do they have any external firewall in front of your server?

The netstate -na command you logged indicates that 8080 port is only listened on ipv6 address not ipv4. Is there any setting you’ve done regarding this?

Try curl http://127.0.0.1:8080 and curl http://<your server IP>:8080 on your Discourse server to see whether you can access the 8080 port. If yes, that means your Discourse is up but some firewall between your client and server blocked it. If no, that means your Discourse is not listening on ipv4 address.

If useful I see this log many many times by doing > ./launcher logs app :

nginx: [emerg] host not found in upstream “avatars.discourse.org” in /etc/nginx/conf.d/discourse.conf:215

Moreover, I have done a ssh tunnel (80->80) towards my local machine and connecting to my localhost:80 the connection is enstablished (TCP: SYN, ACK) but no welcome page (no page at all), the connection does not reach http level…

If useful I see this log many many times by doing > ./launcher logs app :

nginx: [emerg] host not found in upstream “avatars.discourse.org” in /etc/nginx/conf.d/discourse.conf:215

This is very suspicious. Why you have a upstream pointed to avatars.discourse.org? You may need to upload the content of your app.yml file(with sensitive information removed) so we can check whether there is any incorrect configuration.

I don’t see any incorrect settings in your app.yml. If you are following the official docker installation guide, you should have no problem. Could you describe any divergence from the official guide you did during installation?

You may also upload the /etc/nginx/conf.d/discourse.conf file in your discourse container so we can see where the mysterious nginx error came from.

As far as I remember, nginx just won’t start if it encounter an emerg level problem. I believe that’s why you cannot access your Discourse - your nginx is just not running, it keeps starting but never can success. So you see a lot of those logs and your site is not accessible.

Even if you don’t believe so and try to find and solve the issue elsewhere, you still need to fix this problem eventually, so why not solve it now?

What modification? Change the upstream avatars.discourse.org to disourse? You shouldn’t do so. Seeing the welcome page up doesn’t mean it is running correctly. I’m not sure but the location for avatars.discourse.org seems are for avatar functions, changing that may cause problems related to that.