Azure PBX Express - SSH password for restored instance

[JonnyM]

I've seen previous threads on this that refer to new PBX Express deployments on Azure, and point people towards the documentation (https://www.3cx.com/docs/hosting-pbx-phone-system-microsoft-azure/) that states "SSH Information - during the creation of the instance, the SSH password for the user pbxexpress is set to the same password as the 3CX management console login. After the PBX is created, you can change this SSH password and login with the pbxexpress user."

I have deployed into Azure using PBX Express, and restored from a backup. SSH is not accepting my management portal login password, I can login to the management portal without an issue.

Is there some sort of placeholder credential that would usually get updated in the deployment that hasn't been in this case? The email confirmation that I received following the deployment contained the password that the management console admin user was previously set to, so it's managed to extract all the information correctly.

 

[CentrexJ]

If that password doesn’t work I believe you can reset the ssh password through azure portal.

 

[Mark Phillips]

If that password doesn’t work I believe you can reset the ssh password through azure portal.

Yes, this works. Password reset can be found under "Support and troubleshooting" on the VM configuration.

 

[JonnyM]

Thanks, I was unsure whether the Azure deployed VM contained the required extension - glad to see it does. I reset the password for the pbxexpress user through that feature and I can SSH to the VM now.

It's been a pretty smooth deployment so far, other than having to backup and restore the VM to get it into the correct VNet. I'll open a feature request if there isn't one already.

Edit: I didn't realise the feature request forum had been limited to specific types of account. All I will say is that it would be good if the SSH access ACL wasn't open to the world - maybe create it and restrict access to the IP address that is running the PBX Express deployment. I'm not sure, I guess you could argue that people are meant to know what they are doing and should be checking that sort of stuff once the system has deployed.