After changing in base url, I am not able to access the confluenc wiki with new url. Still old url is working.
Old url : http//<serverName>:8080/pages
Changes url: http//myname.com/pages
After change the BaseUrl, i have restarted the Confluence service and tried to hit changed url,but not working. When I hit old url then confluence is working. I can not see any where the existing url in any config file/database/baseurl....everwhere changed url is visible, But still why my Confluence is pointing old url???
Please let know the steps to change url for Confluence Wiki and also let me know where I am missing?
The base url is a Confluence setting - it tells Confluence where you expect to reach it.
The url is determined by your DNS services
Confluence isnt pointing at your old url, it's your network that's doing it. You need to get the new url set up in your DNS system.
I have checked, everything is fine. DNS is not configured, not able to see under ->Control Panel | Administrative Tools -> . Is there anywhere else, we can check? Working on Windows server 2008. In server.xml: Port:8080
<Context path="/pages" docBase="../confluence" debug="0" reloadable="false">
There is no proxy setting.
We are Using AJP as connector. Where to check DNS entry related to Confluence, because we are access from client not from server in client network?
Is there any other file of confluence which have url related info, except server.xml, bandhana table and base url of admin page?
I am wondering from where the working url is coming. I have modified in BaseUrl, bandhana table but still old url is working.
Sorry, I misread this slightly, I thought you were changing the name, hence the reference to DNS, but all you're doing is trying to drop the 8080
You can do that in two ways.
1. Proxy it, so that traffic arriving on port 80 flows to 8080. You'll need a proxying web-server to do that - IIS can be grudgingly made to do it, or use Apache or Nginx or or or...
2. Run Tomcat on port 80 instead of 8080. Stop Jira, change the port in server.xml and restart it. You don't need to do anything other than that. Although, if you were running it on a Unix box, you'd have to fiddle a bit more because it won't let you run processes on a port under 1024 without special rights - I don't know if Windows has a similar security issue
More and more people are building their careers with Atlassian, and we want you to be at the front of this wave! Important Dates Start the Certification Prep Course by 2 April 2019 Take your e...
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