Alright folks, I have tried everything I can think of here, so I am hoping someone is able to help. I have continual errors with the DNS port 443 and Port 80 failure. [image] I set forum.vnfreaks.com to my IP address on cloudflare: (Alright I couldn’t share this image as a new user, but on clou…

Just as a bit of information on extra things I have tried - I tried setting my default port to just be 443, and I also tried doing the discourse setup through my VNC menu via my VPS control panel.

[imagem] Wolf_Witch: set a rule on my windows firewall to allow inbound access through ports 22, 80, and 443. And that io address points to a virtual machine running Linux? That is accessible from the internet?

The rules don’t point to anything, they just allow access from those ports. I felt like it must be some kind of firewall issue because I got the error even when I was trying to use one of the free discourse subdomains.

After that domain check fails, you will have an app.yml generated in /var/discourse/containers. You can edit your subdomain manually into that file, as well as the other required info (like SMTP credentials and dev/admin email address). Then you will be able to rebuild, as the domain check is skippe…

Yeah, I was thinking that might be the route. I tried following a different guide but it gave me some different errors. It do give me experience in editing the app.yml though. Probably the best thing for me to do is delete everything that would have previously been generated by discourse, run it aga…

If accessing that IP address on port 80 and 443 from the public internet don’t get to the Linux VM that you’re trying to run Discourse on, it won’t work. You can skip the test, but unless you’re sure you know what you’re doing, it won’t work, which is why the test exists in the first place.

So do you have any thoughts on how I can get that to work? I’m not sure why my virtual server would not be able to access it on those ports.

It’s not that your virtual server can access it; it’s that everyone on the internet can access it. You need to make sure that your virtual server can be accessed from the internet. You’ll need to search for whatever virtual machine manager you’re using, and if you’re behind a firewall, like in a r…

I mean, my virtual server can be accessed otherwise - I have two other websites that haven’t had issues being accessed from that server.

root@www-hub:~# curl -IL http://forum.vnfreaks.com/ curl: (52) Empty reply from server root@www-hub:~# curl -IL https://forum.vnfreaks.com/ curl: (60) SSL certificate problem: unable to get local issuer certificate I would claim the issue is webserver, vhost etc.

Erros contínuos de DNS não importa o que eu tente

Suporte Instalação

pfaffman (Jay Pfaffman) 18 Fevereiro , 2026 02:38 3

E esse endereço de IP aponta para uma máquina virtual rodando Linux? Que é acessível pela internet?

Tópico		Respostas	Vistas
Port 443 of computer does not appear to be accessible using Self-hosting	26	5529	2 Julho , 2021
Port 443 isn't accessible via hostname Self-hosting unsupported-install	8	1395	24 Setembro , 2020
‘Port 443 of computer does not appear to be accessible’ Self-hosting	6	245	17 Março , 2025
Error - Port 443 not open? Self-hosting	10	1267	7 Setembro , 2022
Port 443 and 80 unavailable Self-hosting	2	279	5 Junho , 2024

Erros contínuos de DNS não importa o que eu tente

Related topics