V18 to V20 - Can't login, can't revert

[rfrary]

I have a complete backup for v18 and now I can't login knowing the extension, system_owner, and password. I keep getting invalid username or password.

I tried a new VM for v18 (old vm had kernel issues) and can't revert due to this license message:

Product cannot be activated because the license key is of a previous version. Upgrade license key or purchase maintenance from


I'm unsure about what the next steps are. I have CLI access.

 

[Shane-Rees-89]

As in you can't login to V20 after the upgrade?

 

[Alphabetic]

And what happens when you press forgot password?

 

[SteveITS]

can't login knowing the extension, system_owner, and password

Just to be clear the logins in v20 are either extension number or email, not a username. You can double check your .xml file in the backup to see which extension is tagged as the system owner.

 

[TheodorosG_3CX]

Check your xml file in the backup and confirm that you are using the correct email to login as system owner.

 

[kent3]

Check your xml file in the backup and confirm that you are using the correct email to login as system owner.

What if the backup is encrypted, do 3CX have a way of un-encrypting it if I have the password to backup file as this has caused me an issue in the past. We encrypt our backups for added security.

 

[Guillaume Bourgeois]

What if the backup is encrypted, do 3CX have a way of un-encrypting it if I have the password to backup file as this has caused me an issue in the past. We encrypt our backups for added security.

No, it’s not possible to decrypt a backup outside of the restoration process.
It’s not the compressed folder that is locked, but its contents that are encrypted.

Only the PBX can decrypt the contents of the zip file, for security reasons.

So, if you encrypt your backups, rest assured they will remain secure, with no risk of leaks, even against brute force attacks. That's the whole point, right?

 

[kent3]

No, it’s not possible to decrypt a backup outside of the restoration process.
It’s not the compressed folder that is locked, but its contents that are encrypted.

Only the PBX can decrypt the contents of the zip file, for security reasons.

So, if you encrypt your backups, rest assured they will remain secure, with no risk of leaks, even against brute force attacks. That's the whole point, right?

Makes sense!

Moral of the story is keep login details on file in case something goes side ways

 

[rfrary]

I purposely didn't encrypt the backup. Either way we have a kernel issue, I'm back in and will need to backup and refresh again at some point. I made all the users admins then logged in with the one we knew and fixed it. Thanks!