Confluence available on localhost, but not on url

[bsc]

Hi all,

I just updated to the latest version 6.14.2x64 (Windows Server / MSSQL)

Installation went fine, but for some reason, I cannot access Confluence on the base URL.

Confluence Service is running. When browsing http://localhost:8090 on the local server, I can access and all seems to be updated fine.

I also updated my server.xml to paste my settings:

proxyName="confluence.asdf.jkl" proxyPort="443" scheme="https" address="127.0.0.1"

Apache2.4 service is installed but wont start up. Even if i try to start it manually. I am quite sure it should be running. Logs there didn't write anything in the corresponding timeframe.

Any idea, where to look next?

[bsc · Accepted solution]

Finally, we could solve the problem.
The issue was in Apache configs but was caused a few weeks ago when I replaced our expiring SSL certificates.
After replacing, I cleaned up the old certificate files. I also removed the apache default-certificates from \Apache24\conf\ssl, assuming, they are not needed.
Actually, these certificates were referenced in \Apache24\conf\extra\httpd-ahssl.conf - even though not being used, these missing files prevented the service from starting up.
Lesson learned: restart services not only after successful changes but also after doing all the housekeeping!

[Brant Schroeder]

I would check all of your settings here: https://confluence.atlassian.com/doc/proxy-and-https-setup-for-confluence-950286281.html and make sure that they are correct.  If everything looks fine then I would check IIS and ensure that the proxy settings there are correct. https://confluence.atlassian.com/kb/proxying-atlassian-server-applications-with-microsoft-internet-information-services-iis-833931378.html  

It sounds like a proxy configuration issue and traffic is not being routed properly.  

[bsc]

Thanks Brant. Seems like you're right. But I couldn't find anything bogus about the configuration. I rolled back to version 6.8.1 - and even if the VM is restored from a snapshot and the database is rolled back to corresponding time, the problem remains the same.

Actually, i still cannot start Apache2.4 service on the restored environment. Starting service manually from windows services will result in "service-specific error code 1"

But all configs weren't touched and contain all the information, that worked right before. I'm a bit perplexed.

[Brant Schroeder]

You should submit a support ticket to Atlassian - https://support.atlassian.com/contact/#/

In the meantime you might look at reinstalling Apache2.4 and seeing if  you can get it to start.  Are there any windows logs about apache?