PBX Express - Google Cloud - Delayed

[aws997]

Hi team, starting a new thread as all other threads relating to this error are closed for further comments..?

As reported by others the PBX Express process fails and the VM instance gets deleted after 20 mins.

Please advice if there is a workaround.

There was an Error While Creating Your Cloud PBX email:

There was an error while creating your 3CX Cloud PBX. The error message is reported below:

Can not start PBX on url 'https://35.244.96.106:443' in specified amount of time: 00:20:00.

It is likely that you have not configured your account correctly to allow instances to be created via API. Alternatively, your cloud provider might not be able to create the instance at this point.

Please go to this link and review the configuration guide for your cloud provider:

https://www.3cx.com/docs/cloud-pbx-providers/

Hosting type: Custom
Hosting: Google

Regards,
The 3CX Team

 

[YiannisH_3CX]

Hello @aws997

Which region are you trying to select the PBX on? Have you tried a different one?

 

[aws997]

I'm selecting the "australia-southeast1" as the region. Does your script only work with a particular region?

 

[cobaltit]

No in theory it should work in all of them but there may be resource or API issues with certain regions, such as yours. Long story short if you can point to another region and it works it's likely a Google problem

 

[YiannisH_3CX]

I'm selecting the "australia-southeast1" as the region. Does your script only work with a particular region?

It should work with all regions available just wanted to see if you can replicate the issue with a different region so we can narrow down the cause. Have you tried a different region ?

 

[StefanW]

we reviewed the logs as you shared the IP if the install attempt.
The instance was fully created and started however we failed to connect to the instance web management console on port 443.When we do not see this connecting we assume there is something wrong with the deployment (user deleted it in the meantime or so what) and not to leave garbage around we kill the instance so you dont get billed for nothing... Why we cannot connect I cannot see or debug as we remove the access tokens after the deploy

 

[aws997]

@StefanW the script opens tcp/443 i assume as part of the install process? i can assure you there was no manual interaction with the virtual machine instance during the pbxexpress process. i only started looking around in google console when the process failed to finish successfully.

would 3cx team review the deployment script and fix the issue or update install instructions? i've heard great things about this pbx however so far my experience hasn't been a great one.

 

[StefanW]

hi,

as part of the API calls we create a port group called 'pbxports' within the project and map it to the instance to be used. We added some error logs in this section to see if it is true (but we cannot test is as it seams to be working for others). Give it please another shot and lets take it from there.