Upgrade to 20 - cannot log in to manage 3CX

[SilverServers]

Greetings,
I went through all the steps to assign an owner and set the email etc. I had tried the upgrade but it didn't seem to work automatically so I had to SSH in and manually do the debian update and then run the 3CX apt install. This brought the system back online but now I can't get in and manage anything.

I have tried password reset but no emails come through.

 

[Evolute IT]

you should've waited longer, now take a backup and reinstall as you probably screwed the update process by trying to do it manually.

also, no email will come for password reset if the email wasn't unique to the system owner you created/assigned.

 

[TheodorosG_3CX]

As @ConceptsWeb mentioned manual update can cause several issues on the installation.
Also you need to ensure that the System Owner has a unique email address otherwise the PBX cannot reset password for multiple users.

 

[Rick-Arcus-IT]

As ConceptWeb mentiones, you probably intervened to soon. Give the v20 update at minimum 15 to 20 minutes to complete, depending on the performance of your machine/vm. If you set the system owner mailadress correct, try to login after you received the email that the update has been successful. If you try to login and 3CX gives 'server error', have some more patience, it's still doing it's magic.

 

[SilverServers]

So I tried importing the backup but the VM can't get through the whole process.
Progress: 42.500%, 3567/8393 items processed
The VM has 2 cores and 1.91GB RAM.
Long story short, the host for the VM is on is isolated machine and is a pain to do anything with. My ultimate goal is to get this system updated, get it onto a new IP address so I can add it to the correct network on a new machine.
For whatever reason the phone still work.

So I tried creating a new VM on a new host in a different network. I used the latest Debian ISO installer from 3CX and finalized with the install from backup. This went smooth and the username/password for admin matched what I was expecting so I was able to log into the new VM fine. Only catch is I have to get the new VM attached to the correct IP address. I think I'll just leave the old VM running the phones for today until I can sort out getting the VM attached to the correct IP address.

Thanks everyone for the tips.

 

[TheodorosG_3CX]

@SilverServers You are welcome. Please update us once this is completed.

 

[SilverServers]

Greetings,
It has been quite a ride but finally the system has been migrated to a new VM on a new host and seems to be fully operational.
A couple of small issues.
If I connect using my admin login through the dynamic FQDN I don't get the admin option in the left menu. If I connect via local IP address I do get the admin option but I get a warning saying I'm not connected through https or FQDN. I can't seem to find any setting that would allow me to manage the system from the FQDN login.

I had to use a temporary IP of 192.168.100.222 as the port forwarding to the old server was pointed at 192.168.100.212. Once the system was installed and the backup imported I disconnected the old machine from the network and switched the IP of the new system to 192.168.100.212 (same as the old machine). I then selected the correct IP in the admin area and the phone lines went active. I'm seeing the old IP and another one - no idea where it got the extra one from - in various areas. Is there a way to get everything to use the 212 IP?

 

[Rick-Arcus-IT]

Greetings,
It has been quite a ride but finally the system has been migrated to a new VM on a new host and seems to be fully operational.
A couple of small issues.
If I connect using my admin login through the dynamic FQDN I don't get the admin option in the left menu. If I connect via local IP address I do get the admin option but I get a warning saying I'm not connected through https or FQDN. I can't seem to find any setting that would allow me to manage the system from the FQDN login.

I had to use a temporary IP of 192.168.100.222 as the port forwarding to the old server was pointed at 192.168.100.212. Once the system was installed and the backup imported I disconnected the old machine from the network and switched the IP of the new system to 192.168.100.212 (same as the old machine). I then selected the correct IP in the admin area and the phone lines went active. I'm seeing the old IP and another one - no idea where it got the extra one from - in various areas. Is there a way to get everything to use the 212 IP?

When you go to Admin -> Advanced -> Console restrictions, did you select the top option or the bottom one? If you're on the 2nd option you need to add the IP where you are trying to reach your 3CX from to the list, for example your nginx proxy.

Where do you see the extra and old IP adresses?

 

[SilverServers]

Console - Got it! I've added the appropriate allowed IPs for remote admin.

The IPs exist when editing a user and selecting the "IP Phone". There's a section for "Network Interface" with a drop-down. I've had to manually go through and change all of these to the correct IP. I'm not sure if there are other areas where this will be an issue as well.

 

[TheodorosG_3CX]

If the console restrictions were configured prior the installation are also restored from a backup.
Are there multiple NIC's on the machine?