I'm running Confluence 5.4.2 on CentOS 6.5, and trying to use Apache to serve HTTPS to the client, connecting to the Confluence standalone tomcat via AJP.
Note: I already have this setup running perfectly on the same machine with Jira.
The Apache config contains:
ProxyPass /confluence ajp://localhost:28009/confluence/
And the server.xml contains:
<Context path="/confluence" 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="" /> </Context> … <Connector port="28009" redirectPort="28443" enableLookups="false" protocol="AJP/1.3" URIEncoding="UTF-8" SSLEnabled="false" scheme="http" secure="false" />
The Confluence base URL is set to https://myserver.com/confluence
I can access the base URL (works over https and http), but get a confluence HTML-page containing resources (images, javascripts, css) with links/sources/URLs like
http://myserver.com/confluence/s/en_GB-1988229788/4731/0a2d13ba65b62df25186f4b87e6c642af1792689.1/_/images/logo/confluence-logo.png
(which gives a Confluence 404 error)
instead of
http://myserver.com/confluence/images/logo/confluence-logo.png(which works fine if I try to view the resource directly via the correct URL)
As far as I can see and check, I'm doing nothing else with Confluence than what is already working with Jira. Any idea or pointers what I am missing?
Best,
Thomas
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.