I’m not very well-versed in using load balancers, but this time I really need to use it. Let’s say my website is called badthreadcomments.com. Every time a user enters my site, their request is sent to my load balancer configured on a VPS, this load balancer should send the request to Discourse hosting in the same VPS, and then Discourse responds to my load balancer, but oh wait, the documentation for using Discourse in production says the following: “Discourse will not work from an IP address; you must own a domain name such as example.com to proceed.” The idea is that the load balancer and Discourse are hosted on the same VPS, so communication between my load balancer and Discourse is 100% local, so, if production requires a domain, what am I supposed to do? what’s the plan here? buy a second domain? if a second domain is necessary, wouldn’t that add more latency to the client?

[image] Willy: Every time a user enters my site, their request is sent to my load balancer configured on a VPS, this load balancer should send the request to Discourse hosting in the same VPS, and then Discourse responds to my load balancer, but oh wait, the documentation for using Discourse in production says the following: “Discourse will not work from an IP address; you must own a domain name such as example.com to proceed.” That means that the clients must access Discourse via a domain name. Internally, behind the last customer facing reverse proxy / load balancer you are can do whatever.

So the order must be like this? badthreadcomments.com > Discourse Docker > Load Balancer > Response Can’t be like this? badthreadcomments.com > Load Balancer > Discourse Docker > Response I don’t understand what you mean by “Internally, behind the last customer facing reverse proxy / load balancer you are can do whatever.”

In production, do I have to have two domains if I want to use a load balancer with Discourse?

Product Support

Jelle_van_der_Pal (Jelle van der Pal) April 28, 2025, 10:51pm 6

I’d recommend checking out Nginx Proxy Manager, the working of that, for your broader understanding.

Topic		Replies	Views
Discourse load balancer encounters problems, hoping to help Self-hosting unsupported-install	7	1262	June 20, 2022
WARNING: Port 443 of computer does not appear to be accessible using hostname: <mydomain>.com Self-hosting	11	1842	September 3, 2024
Setup discourse.domain.com with main site at domain.com Self-hosting	5	1583	December 26, 2020
High Availability 3 Server setup Self-hosting hosting	10	2103	February 19, 2021
Run discourse in front of load balancer like AWS/Oracle OCI Self-hosting	1	453	July 26, 2023

In production, do I have to have two domains if I want to use a load balancer with Discourse?

Related topics