Proxying new setup with reverse proxy

Support Self-hosting
1

i know im a couple of months late on this but i finally took the plunge and started my self hosted journey with this new script. I already had a proxmox/ubuntu vm running docker compose so i figured id continue in there. Since this was simply for testing purposes (my site doesnt even exist yet), I did not expect to need anything opened in my firewall. But as many of you probably already know, the sub-domain verification will fail if you dont do anything other than run the wget script.

re running ./discourse-setup --skip-connection-test will at least allow you past but it does not solve the problem…My inexperienced self took a few too many google searches to find someone mentioning this skip method so i just wanted to add that in here in case someone comes across it.

i dont have a proxy setup right now but what is the best method to properly setup my discourse server so i dont lose my domain and can continue testing until im ready to expose it to my audience? do i need to get my butt in gear and get the proxy setup? or is there another method to safely open 443/80?

2

If you’re running in Proxmox, it isn’t a bad idea to have Discourse in its own LXC container for simplicity with managing ports and resources. That’s what I do and what the majority of people do when using cloud compute.

Discourse does not come with any proxy for your host system. If you aren’t able to open port 80/443 on your network (either if you dont want to or if your ISP blocks it), you should look into Cloudflare Tunnels or something else like ngrok