Hi, I’m trying to install Discourse on a cloud server from Hetzner but when running ./discourse-setup I get the message that ports are blocked ( domain.de is obviously not the real domain): WARNING: Port 443 of computer does not appear to be accessible using hostname: discourse.domain.de. WARNING:…

I’ve had a forum search to see if anyone else had encountered a similar issue and found this, though unfortunately not a ‘true solution’ as such: [afbeelding] Hetzner experiences There was one new issue that I discovered – the discourse-setup failed on error message which suggested that port 443…

Have you looked up the DNS using an external service? Ie. One that is not routing through your cloud host provider? [afbeelding] DNS Lookup Tool – Check DNS Records and Nameservers Explore fast and reliable DNS lookup tools, domain information, and essential network utilities all in on…

I have not done that before, thanks for the tip. It shows the correct IPv4 address.

You are getting that message because those ports are being blocked by Hetzner.

Somehow off topic but do you know why Hetzner would block such important and yet trivial ports?

Okay, thank you. I will contact the support of Hetzner.

To avoid abuse. https://docs.hetzner.com/cloud/servers/faq/ 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 …

That is common solution and one reason why self hosted email server is close to impossíble. But OP had issues with ports 80 and 443. Or did I miss something?

You are right. I mixed up two different issues. Apologies for the confusion.

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. Or am I again missing something?

Manual configuration of app.yml is the solution to the problem for me as well. Thanks! I also found this thread, but I guess I didn’t read it carefully enough… :see_no_evil:

Poorten geblokkeerd (Hetzner cloudserver)

Ondersteuning Installatie

Richie (Richie Rich) 24 april 2022 om 11:29 2

Have you looked up the DNS using an external service?

Ie. One that is not routing through your cloud host provider?

Topic		Antwoorden	Weergaven
After Discourse installation can’t reach it in browser Self-hosting	24	4117	5 september 2020
Cannot access Discourse installation Self-hosting	25	1982	29 december 2019
Port 80/443 not accessible while installing Discourse Self-hosting	4	1423	30 september 2023
Ports 443/80 show as closed after installation Self-hosting	12	950	20 april 2024
Troubleshooting Port Access Self-hosting	25	1703	18 augustus 2020

Poorten geblokkeerd (Hetzner cloudserver)

Gerelateerde topics