For example IP:8080
I want to install it on the corporate intranet, but I cannot use domain 。Can I use IP+port ？
AI-generated summary
Installing Discourse on Corporate Intranet without Domain
Aaron_Pang wants to install Discourse on the corporate intranet, but cannot use a domain name. He considers using IP + port (e.g., IP:8080) instead.
Lilly suggests searching for existing solutions, and merefield advises against using IP + port in production, recommending a subdomain instead.
Aaron_Pang explains that the company prohibits putting the knowledge base on the internet, but merefield clarifies that a subdomain can be used internally without exposing it to the internet.
merefield provides a link to a resource on setting up intranet DNS and suggests seeking help from the company’s IT team or posting an ad in Marketplace.
supermathie and Falco agree that leveraging the IT team to create an internal hostname is the best solution. Falco shares his experience with a similar setup, using an internal DNS hostname and certificates from the company’s internal PKI.
merefield also provides a screenshot of the “login required” setting, which can help restrict access to registered users only.
Hi @Aaron_Pang, 
I would start here:
https://meta.discourse.org/search?q=install%20discourse%20intranet
HI, my corporate intranet can access the Internet. But I can’t use the domain name
Do you have access to company engineering resources?
You could probably put Discourse on a subdomain and only expose that internally?
I don’t think Discourse will run on IP/port nicely in Production.
Internet access will make setup much easier.
I know, but as the company’s knowledge base, the company is prohibited from putting it on the Internet.
I can access the company’s server
Server, can connect to the Internet
You are not putting it on the internet.
You can use a subdomain without that being accessible on the internet I believe.
Here:
If you need someone skilled in this area, you could put an ad in Marketplace
Because the intranet DNS setting is difficult.
I started a new topic, how to set up the forum so that only registered users can see the posts.
As the company’s knowledge base, we hope that the account will be visible to the forum only after it has been reviewed.
You should leverage your IT team to create an internal hostname for this.
This is one of the items asked by the setup wizard: “login required”
This is the way @Aaron_Pang. I have installed and ran a large instance for the whole company using only an internal DNS hostname and certificates from our internal PKI, and it works very well. In my case the server didn’t even had access to the internet.