# Proxying new setup with reverse proxy

**URL:** <https://meta.discourse.org/t/proxying-new-setup-with-reverse-proxy/406487>\
**Category:** Self-hosting\
**Created:** [June 30, 2026, 8:37pm UTC](https://meta.discourse.org/t/proxying-new-setup-with-reverse-proxy/406487 "2026-06-30T20:37:14Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![tayhansolo](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/tayhansolo/32/569173_2.png) [@tayhansolo](https://meta.discourse.org/u/tayhansolo)\
**Post date:** [June 30, 2026, 8:37pm UTC](https://meta.discourse.org/t/proxying-new-setup-with-reverse-proxy/406487/1 "2026-06-30T20:37:14Z")

</div>

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?

---

_[View the full topic](https://meta.discourse.org/t/proxying-new-setup-with-reverse-proxy/406487)._