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.
(Alright I couldn’t share this image as a new user, but on cloudflare I have forum (since it autofills the .vnfreaks.com) set to my IP address with the grey cloud, since that allows DNS connections to happen)
I have it set to my IP address on porkbun:
(Alright I couldn’t include this image since I am a new user. But I have an A address record set to forum.vnfreaks.com tied to my VPS IP address.)
I set a rule on my windows firewall to allow inbound access through ports 22, 80, and 443.
In my putty terminal, I am connected to my server IP. I even turned off my firewall on my router.
The grey cloud on my cloudflare should have everything set, so I really have no idea why I continue to have this issue if I’m being honest.
Only thing I could think is that maybe I need to set something up on my cloudpanel for forum.vnfreaks.com, but I don’t really see why I would need to do that.
If anyone has any suggestions for things I could try, it would be greatly appreciated. (Also, for additional info, I am running off a rented VPS, and using putty to ssh into it.)
I can also add the images I couldn’t fit into this post in the comments if that helps.
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.
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 skipped. Not sure why it would fail with CF proxying disabled though, but you should at least be able to get past the bootstrap step by doing the above.
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 again, and then go that route.
I also see stuff in the documentation about running a “ —skip-connection-test “ I’ve been wondering how I even do that or how I should enter that code, when I should enter it, etc.
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.
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 residential internet setup, you’ll need to do some firewall magic to make that happen.
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
Yeah. Probably there’s some reverse proxy that’s running there, so discourse-setup isn’t an option (without some extra editing to remove ssl and letsencrypt templates).
I had tried to setup a reverse proxie following a different set of instructions is what happened. I’ll just remove that when I get home. I’ll toy around with it some more and see if I can get everything sorted out though.
