"The server cannot be reached" after fresh installed

[kishanecosmob]

Hi Team,

We have installed Jambonz Building a self-hosted solution with two servers.

Installation was successful and all pm2 are running smoothly. While logging in to the Jambonz URL with public IP http://103.254.35.50:3001/, we are getting the below error.

I have attached the pm2 logs file from sbc & feature server and screenshot for your reference.

jambonz feature error.docx jambonz api error.docx

[davehorton]

what is in the .env file in the jambonz-webapp folder? If its not correct, fix it then run

npm run build && pm2 restart jambonz-webapp

[kishanecosmob]

Hi @davehorton,

FYI, I have created two servers for SBC and Feature. Both are in a local environment, but I have mapped a public IP to the SBC server and allowed the required ports.

I have attached the .env and ecosystem.config.js files for your reference.

Local server IPs: SBC: 172.16.16.133 Feature: 172.16.16.134

Please check both files and provide a resolution so that we can access Jambonz and start using it. Also attached influxd service screenshot if any issues in this let me know. Thanks in advance.

ecosystem.config.docx jambonz .env file.docx

[kishanecosmob]

@davehorton Also attached log file when i run the reset_admin_password.js file getting the error.

reset_admin_password.js.docx

[kishanecosmob]

Hi @davehorton

Please provide me resolution on the above issues. We need to start using Jambonz. Thanks in advance.

[davehorton]

support for clustered environments requires a paid support subscription. You seem to have created some sort of custom environment and we do not offer a service where we troubleshoot custom setups for free.