In an attempt to change the login page from http to https, I changed the base url from http to https in the settings of the Confluence GUI however now I cannot reach confluence at all since modifying the base url.
I can't change it back because I can't reach the GUI. I have access to the server via ssh. Please help
Hi Steve,
Please refer to https://confluence.atlassian.com/confkb/how-do-i-manually-change-the-base-url-310378877.html
Changing to https is more than updating the base url. You can view more details about the setup required at https://confluence.atlassian.com/adminjiraserver072/running-jira-applications-over-ssl-or-https-828788168.html
Cheers
Bhushan
Hi Bhushan,
Thank you for helping.
Where do I type those DB commands referenced in your first link? I don't know how to access the bandana table.
Also, is this dangerous? Should I backup the DB? Is there a way to backup the DB manually via ssh? I am not sure which DB I am using.
Steve
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Bhushan,
Also, the reason I modified the base url in the first place was because I saw it at step 4 here:
https://confluence.atlassian.com/doc/running-confluence-over-ssl-or-https-161203.html
If I perform steps 1, 2, and 3 in that document, will I be able to reach Confluence at the base url that I changed to? The only thing I modified in the baseurl was changing http:// to https://
Steve
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey Steve,
Hoping you are trying this on a dev/staging environment as per best practices prior to applying it to production.
If you are following the documentation above, simply reverting the change on database as per my initial suggestion might not be the best option.
Instead, you might want to take a look at the logs that will suggest what is actually causing Confluence from either not starting, or not being accessible at the https url.
I would also suggest raising an L1 support ticket if this is on your production instance.
Regards
Bhushan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.