PBX Express Delayed

Status
Not open for further replies.

kite

Silver Partner
Advanced Certified
Joined
Jan 28, 2013
Messages
9
Reaction score
1
I'm trying to use PBX Express to create an AWS instance. The instance creates, I receive the welcome email, but then the status on the 3CX site is "delayed."

If I view my EC2 console, I see the instance get terminated, and a new one starts. This happens half a dozen times or so. Each time, I receive an email saying that there was an error creating the instance, and implies that I don't have something setup correctly. But I can clearly see the instance being launched.

Any ideas?
 
Could you please share exactly what the email wit the error creating the instance says? Leave out any IPs, etc.
 
There was an error while creating your 3CX Cloud PBX. The error message is reported below:

Can not start PBX on url 'https://xxx.xxx.xxx.xxx:443' in specified amount of time: 00:25: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: Amazon

Regards,


The 3CX Team

www.3cx.com
 
It sounds like the access rights and policies you have set are correct, otherwise you wouldn't even see the machine in the first place.
Why now it disappears I can't say for sure. The error in the email is basically saying that "I created the instance but now it is not responding".

I would suggest checking the AWS logs to see if there is a clue as to why the machine is being deleted.
 
Has this issue been addressed? I'm running into the same issue now but with Google Cloud VM creation. It appears the PBX Express process actually deletes the VM, although it's up and running.

Please advise if there are any updates to this.

Thanks!
 
There is not general issue that has been reported, so it must be something specific. Have you checked your Google Console "Activity" tab? You can find this from the GCC Dashboard.
Also, under "Compute Engine" you can look up "Operations", that also provides some details of what may have happened.
 
Yes after checking the Operations log, the PBX Express script creates an instance, then creates a disk, then 20 minutes later deletes the instance. The 20 minutes is special because that is the timeout value of the PBX Express script.

For some reason the script "thinks" something failed and then deletes what it has done, when in fact the server is up, DNS is working, and I'm able to login to the 3CX Web interface.

See attached log excerpt.

Since this behavior as described above happened to an AWS user, it seems the issue is a script issue with the PBX Express platform.

Please help!
 

Attachments

  • CloudConsole_Log1.png
    CloudConsole_Log1.png
    95 KB · Views: 12
Status
Not open for further replies.

Latest Posts

Forum statistics

Threads
111,894
Messages
589,605
Members
164,764
Latest member
billza209