I had sangoma talk up and running on pbxact 14. I reloaded 16 and restored from backup and setup SangomaConnect again. I tapped on the email link from an iphone that had been working with Talk previously and get the message note Error downloading external provisioning. I thought it might be because the iphone was on the latest ios update, I think 18.3.1. This was on wifi on the local network.
I tested from my android tablet just now and now the app shows Server error.
What’s the best way to troubleshoot this?
Hi @ozarktech
1.Can you make sure Sangoma connect service is running ..?
2. Make sure Sangoma Talk Mobile App Registration address is set properly .
3. Reset talk app on mobile and Send again email provision invite link then check, but before clicking on the email link, monitor the error logs by running below command.
tail -f /var/log/asterisk/sangomaconnect*
So I had been running https port on 8443 but had to change it due to a port conflict. The log shows
==> /var/log/asterisk/sangomaconnect_out.log-20250402 <==
2025-04-02 03:08 -05:00: ### Connecting to PBX
2025-04-02 03:08 -05:00: ### SangomaConnect Daemon running on port 8443
and
[root@phonesystem ~]# tail -f /var/log/asterisk/sangomaconnect*
==> /var/log/asterisk/sangomaconnect_err.log <==
2025-04-03 11:10 -05:00: Error in API request (/mobile/sip/setup) null Error code404 “\n<html lang="en">\n\n<meta charset="utf-8">\nError\n\n\n
Cannot POST /admin/ajax.php\n\n\n”
2025-04-03 11:10 -05:00: Error in API request to (/user/credentials) “\n<html lang="en">\n\n<meta charset="utf-8">\nError\n\n\n
Cannot POST /admin/ajax.php\n\n\n” null
2025-04-03 11:22 -05:00: Error in API request (/mobile/sip/setup) null Error code404 “\n<html lang="en">\n\n<meta charset="utf-8">\nError\n\n\n
Cannot POST /admin/ajax.php\n\n\n”
2025-04-03 11:22 -05:00: Error in API request to (/user/credentials) “\n<html lang="en">\n\n<meta charset="utf-8">\nError\n\n\n
Cannot POST /admin/ajax.php\n\n\n” null
2025-04-03 11:30 -05:00: Error in API request (/mobile/sip/setup) null Error code404 “\n<html lang="en">\n\n<meta charset="utf-8">\nError\n\n\n
Cannot POST /admin/ajax.php\n\n\n”
2025-04-03 11:30 -05:00: Error in API request to (/user/credentials) “\n<html lang="en">\n\n<meta charset="utf-8">\nError\n\n\n
Cannot POST /admin/ajax.php\n\n\n” null
2025-04-03 11:37 -05:00: Error in API request (/mobile/sip/setup) null Error code404 “\n<html lang="en">\n\n<meta charset="utf-8">\nError\n\n\n
Cannot POST /admin/ajax.php\n\n\n”
2025-04-03 11:37 -05:00: Error in API request to (/user/credentials) “\n<html lang="en">\n\n<meta charset="utf-8">\nError\n\n\n
Cannot POST /admin/ajax.php\n\n\n” null
2025-04-03 11:41 -05:00: Error in API request (/mobile/sip/setup) null Error code404 “\n<html lang="en">\n\n<meta charset="utf-8">\nError\n\n\n
Cannot POST /admin/ajax.php\n\n\n”
2025-04-03 11:41 -05:00: Error in API request to (/user/credentials) “\n<html lang="en">\n\n<meta charset="utf-8">\nError\n\n\n
Cannot POST /admin/ajax.php\n\n\n” null
I suspect the issue now has to do with the port being changed from 8443 to 443 but I’m not seeing how to update that?
I’m in the process of Run Domain action and run cloud Connect Agent action again, I hope that’s all it takes.
I’m still getting a Failed to Get user credentials in the app.
==> /var/log/asterisk/sangomaconnect_err.log <==
2025-04-03 12:00 -05:00: Error in API request to (/user/credentials) {“status”:false,“message”:“Hash is not on the db”} null
Can you please open a case at help.sangoma.com ?
You can ask to assign the case to me, or you can give me the case number here.
I opened Case 01840804
1 Like
Support requested vpn access. The vpn doesn’t connect. They requested their ip be allowed for GUI access. I did that a few days ago and haven’t heard back. Can this get looked at soon @slobera
This is working now Doug, thanks for taking my call 
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.