Common Panel Connection Issues

Common Panel Connection Issues

Panel connection problems are the most frequently reported issues by IPTVbp vendors. This guide walks through every common scenario with specific diagnostic steps and solutions.

Issue 1: Connection Timeout

Symptom: "Connection timed out" or "Could not reach panel" when testing the connection.

Diagnostic Steps:

1. Verify the URL format: Must include the protocol and port.

   • Correct: http://203.0.113.10:25500
   • Wrong: 203.0.113.10:25500 (missing protocol)
   • Wrong: http://203.0.113.10 (missing port for Xtream UI)

2. Test from your browser: Open the panel URL in a web browser. If you see the panel login page, the panel is reachable. If you get a timeout, the issue is between IPTVbp's server and your panel.

3. Test from the IPTVbp server: If you have SSH access to the IPTVbp server, test connectivity:

   curl -v http://203.0.113.10:25500
   

   This tells you whether the server can reach the panel.

4. Check firewall rules on the panel server:

   # On the panel server
   sudo ufw status
   # or
   sudo iptables -L -n
   

   Ensure the panel port (25500 for Xtream UI, 443 for NXT) allows incoming connections from the IPTVbp server IPs (45.137.20.16 and 45.137.20.139).

5. Check if the panel service is running:

   # Xtream UI
   sudo systemctl status xtreamcodes
   
   # NXT Dashboard
   sudo pm2 status
   # or
   sudo systemctl status nxt
   

Solutions:

• Add a firewall rule to allow IPTVbp server IPs.
• Restart the panel service if it is stopped.
• Use an IP address instead of a hostname (DNS resolution issues are common).
• If the panel is behind Cloudflare or another proxy, ensure the proxy does not block API requests.

Issue 2: Authentication Failed

Symptom: "Authentication failed" or "Invalid credentials" or "401 Unauthorized".

Diagnostic Steps:

1. Verify credentials: Log into the panel's web interface directly using the same username and password. If you cannot log in there either, the credentials are wrong.

2. Check for special characters: Some panel APIs have trouble with passwords containing certain characters (, , , , <, >). Try changing to an alphanumeric password.

3. For NXT Dashboard: Verify the API token has not expired and has the required permissions (Create Users, Manage Subscriptions, View Packages).

4. Check API access is enabled: Some Xtream UI installations have API access disabled by default. Check Settings > General in the panel admin.

Solutions:

• Reset the panel admin password and update it in IPTVbp.
• For NXT, regenerate the API token and update it in IPTVbp.
• Enable API access in the panel settings.
• Use alphanumeric-only passwords if special characters cause issues.

Issue 3: SSL/TLS Certificate Error

Symptom: "SSL certificate problem" or "Unable to verify certificate" or "CERT_HAS_EXPIRED".

This occurs when connecting to a panel using HTTPS with an invalid, expired, or self-signed certificate.

Solutions:

• Renew the certificate: If using Let's Encrypt, run certbot renew on the panel server.
• Fix the certificate chain: Ensure the full chain (including intermediate certificates) is configured in the web server.
• Use HTTP instead of HTTPS: If the panel is on a private network, HTTP may be acceptable (less secure but avoids certificate issues).
• Use a valid certificate: Replace self-signed certificates with Let's Encrypt (free) or a commercial certificate.

Issue 4: Packages Not Loading

Symptom: Connection succeeds but no packages are found, or "No packages available".

Diagnostic Steps:

1. Log into the panel admin and verify at least one package/bouquet exists.
2. Check the package is active (not disabled or deleted).
3. For Xtream UI, ensure the bouquet has at least one stream assigned to it.

Solutions:

• Create a package in the panel if none exist.
• Activate disabled packages.
• Click Refresh Packages in IPTVbp to force a re-sync.

Issue 5: Intermittent Failures

Symptom: Connection works sometimes but fails randomly.

Possible Causes:

1. Panel server overloaded: High CPU or memory usage causes slow or dropped connections.

   • Check with top or htop on the panel server.
   • Consider upgrading server resources.

2. Network instability: Packet loss between IPTVbp and the panel server.

   • Run mtr -r PANEL_IP from the IPTVbp server to check for packet loss.

3. Rate limiting: Some panels or hosting providers rate-limit API requests.

   • Reduce health check frequency in IPTVbp settings.
   • Contact the hosting provider to increase limits.

4. Database deadlocks: Xtream UI is known for MySQL deadlocks under heavy load.

   • Optimise the Xtream database: mysqlcheck --optimize xtream.
   • Consider moving the database to a dedicated server.

Issue 6: Provisioning Succeeds But Credentials Do Not Work

Symptom: IPTVbp shows the subscription as active, but the customer cannot connect to the IPTV service.

Diagnostic Steps:

1. Look up the username in the panel admin. Verify the line exists and is active.
2. Check the expiry date on the panel line -- it should be in the future.
3. Try the credentials yourself using a VLC player or IPTV app.
4. Check if the customer is using the correct server URL and port (not the admin URL).

Solutions:

• If the line does not exist in the panel, there may be a sync issue. Check IPTVbp logs for API errors.
• If the line is expired, the provisioning may have set the wrong expiry. Check product configuration.
• Ensure the customer is using the streaming URL (e.g. http://panel:8080) not the admin URL (e.g. http://panel:25500).
• Reset the password in IPTVbp and resend credentials.

Quick Reference Table

Symptom	Most Likely Cause	First Action
Connection timeout	Firewall blocking port	Check panel firewall rules
Authentication failed	Wrong credentials	Try logging into panel directly
SSL error	Expired certificate	Renew Let's Encrypt cert
No packages	No bouquets created	Create package in panel
Intermittent failures	Server overload	Check panel server resources
Credentials do not work	Wrong streaming URL	Verify customer is using correct URL