Solved AWS Instance - no access to phone system via web

Status
Not open for further replies.

Bigzan

Free User
Joined
Jul 22, 2020
Messages
6
Reaction score
1
Hi Everybody,

I have recently been introduced to 3CX v16 and was hoping to get to grips with the AWS EC2 version and to do a bit of testing to see how it fairs.

However I am having quite a lot of trouble in trying to get to the instance once I have completed the installation. Everything installs and sets up just fine, but I am just not able to get to the web page to login in and instead I get a

502 Error: Bad Gateway

Is there something I need to be doing in the process? The ports are assigned correctly and i'm just not seeing the login page.

I tried to use the pbxexpress version but that just gets stuck at the VPS machine selection.

I appreciate and thank all who offer their expertise!

Regards
Bigzan
 
are you using https to connect?
 
so if you didn't used pbxexpress to install, how did you do ?
can you give some details on install steps you follow?

3CX debian iso is already prepared for 3cx use, this is why I ask your how to
 
are you using https to connect?

Hi Jacobegan, thank you for replying!

I have tried both the http and the https (80 and 5001 respectively) to connect but still no joy.

Incidently,
http://<my-instance-IP> is showing the 502 Bad Gateway error since the;

https://<my-instance-IP>:5001 just fails to show anything...
 
https://<my-instance-IP> does that load anything?
 
so if you didn't used pbxexpress to install, how did you do ?
can you give some details on install steps you follow?

3CX debian iso is already prepared for 3cx use, this is why I ask your how to

Hey AWS2P, thank you for taking the time to reply!

I initially tried the pbxexpress option but this is as far it allows me to get and I am not able to proceed (see attached image)

I have used the Debian install via the AWS Marketplace which is the Amazon Machine Image and that auto installs everything on a virtual machine. The entire process flows relatively easily however it just doesn't allow me to connect to the system web page once the installation completes.

I just follow the standard process as it is shown in the guide. The system allows inital access via the web to perform the installation using the credentials-

username:3CX password:<my-amazon-instance-id>

Once I get the successful instance page, it displays the IP address along with login credentials and it emails them across to me. But when I try to access them http gives me a bad gateway and https just fails.

I am using firefox and have tried alternate desktops and I am not behind any VPN.

Gratitude and appreciation for your help!

Regards
Bigzan
 

Attachments

  • pbxexpress stuck.png
    pbxexpress stuck.png
    419.4 KB · Views: 7
https://<my-instance-IP> does that load anything?

Hi Jacobegan, thank you for replying!

No unfortunatly nothing appears. Only the bad gateway error if I use the http://<my-instance-IP>

Gratitude and appreciation for your help!

Regards
Bigzan
 
Make sure you have the right ports open on your AWS Instance, Also my guess is you need to go to the first time configuration wizard:
EG:
http://x.x.x.x:5015
To configure the PBX then you can use it on the standard ports of 5001/443 depending on setup.
 
Make sure you have the right ports open on your AWS Instance, Also my guess is you need to go to the first time configuration wizard:
EG:
http://x.x.x.x:5015
To configure the PBX then you can use it on the standard ports of 5001/443 depending on setup.

Hi Terry, thank you for responding!

The process installs fine, I use the usual ports and have followed through the installation to completion.

Regards
Bigzan
 
Hello All,

I would like to thank everyone here for their input and assistance in trying to resolve the issue.

I even got the guys from Amazon to jump on and take a look and they had confirmed what I suspected-

The issue was from our end as there were port restrictions on the network connection we were using.

Having connected to another internet connection with reduced security it allowed access instantly!

My apologies for the tail-chasing...


Regards
Bigzan
 
  • Like
Reactions: AWS2P
Glad to hear it was resolved, thanks for updating the thread
 
your Pbxexpress failure is not normal, before starting pbexpress did you proceed to create an instance on AWS with 3CX docs?

If so, did you used the same region EU-WEST2 as you tried to use in pbxexpress ?

never been stuck in pbxexpress.
 
Status
Not open for further replies.

Forum statistics

Threads
111,954
Messages
589,923
Members
164,852
Latest member
priya