Hosting 3cx on Microsoft Azure

[sumaana]

On Microsoft Azure, I created a 3CX PBX VM. I have followed all the steps according to the guide
https://www.3cx.com/docs/pbx-azure-marketplace/
but I still cannot access the configuration wizard. I tried to open it from Chrome, Firefox, and Internet Explorer too. I couldn't figure out why it was happening. I have created a new VM, but still it does not work. Can someone help me on this. Am I missing something. This is my first time working on azure 3cx vm
VM is Debian 10.13 V1

 

[Charles_3CX]

Did you follow the step to create a swap file?

Our advice is to use 3CX hosted instead where we we take care of all this for you.

https://www.3cx.com/ordering/pricing/

 

[Alphabetic]

Sounds like you havent configured the firewall correctly.

 

[sumaana]

Did you follow the step to create a swap file?

Our advice is to use 3CX hosted instead where we we take care of all this for you.

https://www.3cx.com/ordering/pricing/

Yes I did create swap file.

 

[SteveITS]

There's a problem today. Not sure if this would be related. This was posted on another forum:

"[Microsoft] Tracking ID BS81-390

Impact Statement: Starting at 07:01 UTC on 31 Jan 2023, you have been identified as a customer using Virtual Machines in East US 2 who may receive error notifications when performing service management operations - such as create, delete, update, scaling, start, stop - for resources hosted in this region.

Current Status: Automatic monitoring alerted us of two partitions of a backend service hosted in East US 2 region becoming unhealthy due to a data process issue. Due to dependencies between services, this manifests in failures when performing service management operations for a subset of Virtual Machines customers with resources in Availability Zone 02. We continue our recovery efforts to bring the affected partitions back to a healthy state to alleviate impact.

Workaround: Customers impacted by this issue could alternatively failover to Availability Zone 01 or Availability Zone 03. Please refer to this documentation for further guidance."