I am not sure if I could the problem clear but I will try my best. :grin: I set up the Discourse on port 9988 and proxy it to subdomain, http://d.abc.com/ , with nginx. It works. However, I can still access it from http://abc.com:9988/ and http://d.abc.com:9988/ . How can I completely disable the acc…

Your can use a firewall like iptables to block access to this port. Alternatively, you can follow this guide to use a socket instead of a port, eliminating the need to block any port :slight_smile:

@fefrei Thank you! You are the best! :kissing_heart:

Disable direct access with port (nginx)

Product Support Self-hosting

preDawnHunter (Haobin Liang) July 22, 2015, 9:36pm 4

@fefrei Thank you! You are the best!

Topic		Replies	Views
Block Direct Connections Self-hosting	4	1086	November 24, 2014
Nginx + discourse Self-hosting	9	8412	February 8, 2016
Checking domain name fails behind NGINX proxy Self-hosting	1	1134	October 21, 2020
Running on different port than 443: Disable redirect to nonport URL Self-hosting unsupported-install	7	1170	July 18, 2023
Forcing access to Discourse via domain name only Self-hosting	4	989	October 5, 2017

Disable direct access with port (nginx)

Related topics