The app can’t connect to the server
Check the server domain and your connection to the company network. Your administrator can check the services, port and certificate.
Symptoms
- When signing in, you see No Gadka server responds at this address. or Can't reach the server. Check the address and your network connection.
- After signing in, you see Connecting…, Reconnecting…, or a No connection window.
The app keeps trying to reconnect. Select Try again to try immediately.
Check the connection on your computer
- Open a website in your browser to check your network connection.
- Check the server domain. Enter only the domain, such as
gadka.example.com, withouthttps://. - If the server is available only on your company network, connect to the VPN.
- Ask a colleague whether Gadka works for them. If they can’t connect either, ask your administrator to check the server.
Server diagnostics
1. Check whether the services are running
systemctl status gadka gadka-proxy
gadka healthcheck && echo OKIf a service is down, look for the cause with journalctl -u gadka -n 50 or journalctl -u gadka-proxy -n 50.
2. Check whether the port is reachable from outside
Run this on the user’s computer:
curl -I https://gadka.example.com:6543/| Result | Meaning |
|---|---|
| Any HTTP response | The network, TCP port, and certificate are working. |
| Connection timed out or refused | Check the firewall, port forwarding, and DNS. |
| Certificate error | Continue to step 3. |
3. Check the certificate
- Check the expiration date.
- Verify that the certificate covers the server domain.
- Make sure the file contains the full certificate chain.
- If your organization issued the certificate, make sure the user’s computer trusts its certificate authority.
See Domain and HTTPS.
4. Check QUIC and UDP
The app first tries QUIC over UDP. If UDP is blocked, it automatically switches to WebSocket over TCP and keeps working. If the app connects but frequently disconnects, open UDP port 6543 on the firewall. See Firewall and ports.
5. Check any proxy between users and Gadka
An additional proxy or web application firewall must allow WebSocket connections on /gwp/ws, including the Upgrade and Connection headers. Otherwise, the app keeps showing Connecting….
The server was updated or restarted
During a restart, apps lose their connection for about 10 to 20 seconds, then reconnect automatically. You stay signed in.