Hi, I upgraded our Confluence 6.2 to 6.13.5 and the log stated:
entireUpgradeFinished Upgrade completed successfully
However, when going to the url I get an NGIX error as per image below, not very helpful in its direction. I checked the upgrade tasks from intermediate release notes here....
https://confluence.atlassian.com/doc/confluence-6-9-upgrade-notes-949755515.html
https://confluence.atlassian.com/doc/confluence-6-10-upgrade-notes-952058231.html
.... but to no avail.
I'm biting bullet and going to restore snapshot and try again on Monday but thought I'd ask in case someone has a lightbulb moment for me.
Thanks
Resolved it!
The upgrade, for whatever reason reset the proxyname port numbers from 8092 to 8090 so it obviously then had trouble connecting using the proxyname we use in our links (and set as the base URL in settings).
I noticed we had to nginx dir on our drive and I typically managed to pick the wrong one when viewing the log file hence no evident reason for my connection error.
Confluence was upgraded successfully and was requiring the servername:<portnumber> or IP:<portnumber> in order to allow access. our host proxyname is "apconfluencetest" as can be seen below.
The nginx error was:
2019/06/10 23:08:55 [error] 1632#11472: *10 upstream timed out (10060: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond) while connecting to upstream, client: 10.128.12.159, server: apconfluencetest, request: "GET /dologin.action HTTP/1.1", upstream: "http://10.242.130.12:8090/dologin.action", host: "apconfluencetest"
Changed port numbers in the nginx.conf file, restarted nginx service and all seems well.
Thank you for responses.
Confluence will always modify the server.xml file when being upgraded. That’s why you get a list of modified files that you should review.
Glad you solved it,
JP
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
we cannot see the image...
Best
JP
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It doesn't point me to specific log and having checked the NGINX directories I don't see anything of note in the log files that exist there
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.