So I think the firewall is not the reason for the message above. Is it possible that there is something else that is blocking the ports? I’ve read that Apache could cause such a problem but it is not installed on the cloud server.
I tried telnet discourse.domain.de 443 to see if the ports are open and I got
telnet: Unable to connect to remote host: Network is unreachable
Does anyone have an idea how to fix this problem?
Unfortunately, email spammers and scammers like to use cloud hosting providers. And we at Hetzner naturally want to prevent this. That’s why we block ports 25 and 465 by default on all cloud servers. This is a very common practice in the cloud hosting industry because it prevents abuse. We want to build trust with our new customers before we unblock these mail ports. Once you have been with us for a month and paid your first invoice, you can create a limit request to unblock these ports for a valid use case. In your request, you can tell us details about your use case. We make decisions on a case-by-case basis.
As an alternative, you can also use port 587 to send emails via external mail delivery services. Port 587 is not blocked and can be used without sending a limit request.
I’m still confused, but at Digital Ocean firewall must be set up. Clean install doesn’t have any ports open (except for SSH but that is dfferent thing). I don’t know how Hetzner works. And if VPS is behind closed ports, it doesn’t matter what we have on app.yml.
I think so. When I start a VPS (Ubuntu 20), nginx isn’t installed by default: discourse-setup installs it.
I’ve installed Discourse numerous times on Hetzner VPS without any problem for years (the last time was in February).
That’s why I’m puzzled about this topic.
edit: for some reasons my brain mixed up docker and nginx