Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Upgrade from version 7.8.0 to 7.14.1 fails

Payam MASOUMI November 9, 2021

Hello,

we are currently in the process of upgrading Confluence from version 7.8.0 to 7.14.1. The process runs as it is supposed and describes in the documentation. We copy the files required just as stated in the process but the service won't run anymore. Website won't load and the system is not accesible. We are running the system in Windows 2016 with MySQL.

2 answers

0 votes
Daniel Ebers
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
August 20, 2022

Because the question to troubling upgrade processes repeats recently in Community here more of a basic recommendation:
If your own staff gets stucks with migrated trained and skilled partners are available which are experienced in doing upgrades and complex migrations.
You can locate a partner near you from partner directory:
https://partnerdirectory.atlassian.com/

Regards,
Daniel

0 votes
Radek Dostál
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
November 9, 2021

What does "as stated" and "won't run" and "won't load" mean? You're describing about a thousand possible causes.

Payam MASOUMI November 9, 2021
  • As stated in the upgrade documentation from Atlassian in "upgrading Confluence" (AKA the documentation)
  • Won't load is won't load, it keeps looking for the web access until it comes up with a time out.

I don't know what else to tell you that, is literally the behaviour.

Payam MASOUMI November 9, 2021

I'm looking for a known issue when you migrate from/to those specific versions. If there's none then maybe any tips where to look when the web service won't let the website load. So yes, it is pretty general, but at this point without access to the webadmin there isn't much to say about it. Maybe someone has experienced this and have any ideas what could be when you have that behaviour even when following the upgrade steps exactly as Atlassian describes them. 

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
SERVER
TAGS
AUG Leaders

Atlassian Community Events