Issues found after upgrade
Asked by Josh Pelligrino:

After upgrading my version of Confluence from 5.7 to 6.8, I have noticed the following issues:

1. Unable to access site over port 80 even after going through the KB's on this site. I have edited the server.xml file, restarted the application and still does not work. It will over port 8090, but not over 80

2. Unable to change base URL. Each time I go to localhost, it tells me that the base URL is different and when I go to change it, a pop up continues to state that the base URL isnt the same.

3. When I go to edit the home page, it just sits and spins and never allows me.

As well as a few other issues.


Answers:
author: Josh Pelligrino
body: Also, I cant get an add-on to uninstall. I click the uninstall button and nothing happens. This is for "Universal Plugin Manager Self Update Plugin" version 2.22.5

comments: author: AnnWorley
body: Hi Josh,

During our call we made sure nothing was taking up port 80 and looked for a proxy on the server, which we did not find. After editing the server.xml and restarting the service once more we were able to reach the instance over it's DNS "friendly" name.

I know the universal plugin manager can be impacted by base URL issues so I am curious whether the issue with the plugin is persisting since we are accessing Confluence over the configured base URL.

I understand you are not fond of a lot of SQL queries so please try clearing the plugins cache as described in: [How to clear Confluence plugins cache](https://confluence.atlassian.com/confkb/how-to-clear-confluence-plugins-cache-297664846.html), first.

If there is still an issue, please try these articles: [Unable to Uninstall a Plugin or Install an Old Version of a Plugin](https://confluence.atlassian.com/confkb/unable-to-uninstall-a-plugin-or-install-an-old-version-of-a-plugin-155484380.html) and [How to manually remove malfunctioning add-ons](https://confluence.atlassian.com/confkb/how-to-manually-remove-malfunctioning-add-ons-113705118.html)

Thanks,  
Ann


author: Josh Pelligrino
body: * Let me know what you see in the browser when Confluence won't serve over port 80: I have used IE, Chrome and FireFox.
* Post a screen shot of the base URL message because sometimes it will reveal where Confluence "sees" the request as originating, which could be a clue.

![Base URL.png](https://community.atlassian.com/t5/image/serverpage/image-id/18245iAD09A3B780DEDA30/image-size/large?v=v2&px=999 "Base URL.png")

* So that I can better understand your configuration, please post the contents of your server.xml file from \<Confluence_Install\>/conf directory.

\<Server port="8000" shutdown="SHUTDOWN" debug="0"\>  
\<Service name="Tomcat-Standalone"\>  
\<Connector port="8090" connectionTimeout="20000" redirectPort="8443"  
maxThreads="48" minSpareThreads="10"  
enableLookups="false" acceptCount="10" debug="0" URIEncoding="UTF-8"  
protocol="org.apache.coyote.http11.Http11NioProtocol" /\>

\<Engine name="Standalone" defaultHost="localhost" debug="0"\>

\<Host name="localhost" debug="0" appBase="webapps" unpackWARs="true" autoDeploy="false" startStopThreads="4"\>  
\<Context path="" docBase="../confluence" debug="0" reloadable="false" useHttpOnly="true"\>  
\<!-- Logger is deprecated in Tomcat 5.5. Logging configuration for Confluence is specified in confluence/WEB-INF/classes/log4j.properties --\>  
\<Manager pathname="" /\>  
\<Valve className="org.apache.catalina.valves.StuckThreadDetectionValve" threshold="60" /\>  
\</Context\>

\<Context path="${confluence.context.path}/synchrony-proxy" docBase="../synchrony-proxy" debug="0" reloadable="false" useHttpOnly="true"\>  
\<Valve className="org.apache.catalina.valves.StuckThreadDetectionValve" threshold="60" /\>  
\</Context\>  
\</Host\>

\</Engine\>

\<!--  
To run Confluence via HTTPS:  
\* Uncomment the Connector below  
\* Execute:  
%JAVA_HOME%\\bin\\keytool -genkey -alias tomcat -keyalg RSA (Windows)  
$JAVA_HOME/bin/keytool -genkey -alias tomcat -keyalg RSA (Unix)  
with a password value of "changeit" for both the certificate and the keystore itself.  
\* Restart and visit https://localhost:8443/

For more info, see <https://confluence.atlassian.com/display/DOC/Running+Confluence+Over+SSL+or+HTTPS>  
--\>  
\<!--  
\<Connector port="8443" maxHttpHeaderSize="8192"  
maxThreads="150" minSpareThreads="25"  
protocol="org.apache.coyote.http11.Http11NioProtocol"  
enableLookups="false" disableUploadTimeout="true"  
acceptCount="100" scheme="https" secure="true"  
clientAuth="false" sslProtocols="TLSv1,TLSv1.1,TLSv1.2" sslEnabledProtocols="TLSv1,TLSv1.1,TLSv1.2" SSLEnabled="true"  
URIEncoding="UTF-8" keystorePass="\<MY_CERTIFICATE_PASSWORD\>"/\>  
--\>  
\</Service\>  
\</Server\>


author: AnnWorley
body: Hi Josh,

The issue you are reporting with the editor after upgrading is sometimes related to a base URL mismatch, so let's sort out the port and base URL and then move on to the editor if it is still misbehaving. [Unable to edit any pages in Confluence 6.x due to Collaborative Editing](https://confluence.atlassian.com/confkb/unable-to-edit-any-pages-in-confluence-6-x-due-to-collaborative-editing-867362716.html)
> A mismatch of Base URL and Access URL will result in users unable to edit any pages.

To help me investigate, please:

* Let me know what you see in the browser when Confluence won't serve over port 80.
* Post a screen shot of the base URL message because sometimes it will reveal where Confluence "sees" the request as originating, which could be a clue.
* So that I can better understand your configuration, please post the contents of your server.xml file from \<Confluence_Install\>/conf directory.

Thanks,

Ann