I have made a new confluence server installation (V6.1.2) with all default settings (in Linux).
Everything went well but when I go to http://localhost:8090 to continue the setup, the URL is changed to http://localhost:8090/setup/setupstart.action and then I get an error stating cannnot connect to localhost.
The confluence server is running, the port 8090 is allowed in firewall, the confluence log file says that the server is ready.
Have anyone ran into this issue? If so, how did you resolve it?
I understand you checked the log and it says the server is ready. Is that the "server startup in xx ms" in catalina.out or does the atlassian-confluence.log say "Confluence is ready to serve"?
Is there anything in the atlassian-confluence.log after "Confluence is ready to serve"? It sounds like Confluence is coming up long enough to detect that it's a new install (hence changing the URL) then it is going down somehow. If it was a loopback or other misconfiguration in Linux I would not expect you to see the setup URL in the first place.
I look forward to hearing whether there is anything else in the logs.
A similar issue was solved by raising the Java heap memory:
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.