VitalConnect app timeout (cURL error 28) when using custom port (3500) – HTTPS requirement?

VitalPBX Mobile
1

Hi,

I’m having an issue setting up VitalConnect with a custom API port.
Setup:

  • VitalPBX running on Debian 12
  • VitalConnect API available on:
    • HTTP: http://vitalconnect.domain.com:3500
    • HTTPS: https://vitalconnect.domain.com:3501
  • Main web GUI is running on:
    • https://vitalconnect.domain.com (port 443)

Problem:
When scanning the QR code in the VitalConnect mobile app, I get:

cURL error 28: Operation timed out after 10001 milliseconds

However:

  • Accessing http://vitalconnect.domain.com:3500 works (API responds)
  • Port 3500 is open and reachable
  • DNS is correct

Observation:
It seems the mobile app is always trying to connect via:

https://vitalconnect.domain.com

(on port 443)
and ignores:

  • custom ports
  • HTTP endpoints

Temporary workaround:
I solved it by configuring nginx to proxy:

https://vitalconnect.domain.com/api → https://127.0.0.1:3501

After that, the app connects successfully.

Questions:

  1. Does VitalConnect app require HTTPS on port 443?
  2. Is there any way to configure the app to use:
    • custom port (e.g. 3500)
    • or HTTP instead of HTTPS?
  3. Is this expected behavior or a limitation?

Thanks in advance!

2

That means your server is blocking the Provisioning server. Keep in mind that the provisioning server is hosted in the USA.

So, being able to access the server from your country doesn’t imply our provisioning server can reach your server.

Important
Make sure our provisioning server IP(145.223.123.175) can query your server.