I want to use the address http://confluence.mycompany.com instead default http://localhost:8090.
And after restart if I go to http://localhost:8090, i get :
Your URL doesn't match
Confluence's base URL is set to http://confluence.mycompany.com but you are accessing Confluence from http://localhost:8090.
Update base URL
If i go to http://confluence.mycompany.com, i get:
Explanation: The Web server refused the connection.
Try the following:
If you are still not able to view the requested page, try contacting your administrator or Helpdesk.
Technical Information (for support personnel)
what is the problem?
How can i do this?
Your network is not routing the request http://confluence.mycompany.com to Confluence.
This could be DNS, routing, (I would mention firewalls, but the error is not a block, it's a "not serving", so we know the request is landing somewhere), or that the server you are contacting is not serving pages where you have ended up.
Easiest test is to specify the right port - try http://confluence.mycompany.com:8090 - what does that say?
That's good. It means your network is routing correctly, and the server is running Confluence as expected.
I assume you really want to change the port number of 8090 so you don't have to have it in the url. To do that, you need to make the server listen on port 80. Almost all software (i.e. browsers) assume that if you don't specify a port in a url, then they should use the default one invisibly. That's port 80 for http.
So, you need to relocate it from 8090 to 80. You can do that in the Tomcat running Confluence, or you can run Confluence through a proxy. Most people use proxies because they have other advantages like caching, easier setup and security, and being able to make many services work together to look like one, but you might not need any of that.
Are you going to want to do this with Tomcat, or a proxy?
It's certainly easier on the most part.
Next question is which proxy. Most people I work with use Apache, and that's the one I'm most familiar with (I worked with a couple of the guys who wrote it!), but you can use any one that has a "proxy" function. Apache, IIS, nginx, lighttpd and so-on can all do it. You should choose one that you're most familiar with.
Atlassian has good docs on rigging up Apache, IIS and nginx as a proxy for their services.
Nope, the proxy can be on any server that can see the Confluence server, and the DNS resolves to that proxy.
It will conflict with existing proxies if it is on the same server as the proxies, unless you configure them to listen on different ports.
Most of us don’t need much convincing that stakeholder management is important. It just makes sense that keeping everyone in-the-know on projects and assigning clearly defined roles is key to having ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs