NeuroAgent

3x-ui Panel Not Loading: Complete Troubleshooting Guide

Complete guide to diagnosing and fixing 3x-ui panel loading issues on your server. Step-by-step instructions to restore access.

Question

What should I do if the 3x-ui panel doesn’t load?

I have a server on Aeza where I’ve configured a VPN using an SNI key (from a whitelist) in 3x-ui for Amnezia. After entering the SNI key from the whitelist, the VPN worked for several days. It had also previously worked stably on the Xray built into Amnezia. Now the VPN isn’t working again. I tried to access the 3x-ui panel through WinSCP, went to the IP:8080 link, but the page loads infinitely through my home internet. What should I do in this situation?

NeuroAgent

3x-ui Panel Not Loading Due to Possible Server Issues, Network Settings, or VPN Configuration

To resolve the issue, you need to check the service status, restart the 3x-ui panel, clear browser cache, and verify server network settings including ports and firewall.

Contents

Main Causes of Panel Loading Issues

The 3x-ui panel loading issue can occur due to several main reasons:

Server Issues:

  • 3x-ui service stopped
  • Insufficient system resources (CPU, RAM)
  • Errors in configuration files
  • Corrupted installed packages

Network Problems:

  • Port 8080 blocked on firewall
  • Traffic routing issues
  • IP address conflicts
  • DNS resolution problems

VPN Configuration Issues:

  • Incorrect SNI keys
  • Xray settings errors
  • SSL/TLS certificate issues
  • Conflicts between different VPN protocols

In your case, when the VPN worked for several days and then stopped functioning, the most likely causes are issues with the 3x-ui service or network conflicts that arose after some changes on the server.


Step-by-Step Diagnosis and Solution

1. Check 3x-ui Service Status

First, you need to check if the 3x-ui service is running on your server:

bash
systemctl status x-ui

If the service is inactive, try restarting it:

bash
systemctl restart x-ui
systemctl enable x-ui

Check the service logs for errors:

bash
journalctl -u x-ui -n 50

2. Restart the Control Panel

If the service is running but the panel is not loading, execute the following commands:

bash
# Stop the service
systemctl stop x-ui

# Remove old configuration files (make a backup first)
rm -rf /etc/x-ui/*
rm -rf /usr/local/x-ui/*

# Restart the service
systemctl start x-ui

Important: Before deleting configuration files, be sure to create a backup of important settings.

3. Check Port 8080

Make sure port 8080 is open and listening:

bash
netstat -tulnp | grep 8080
ss -tulnp | grep 8080

If the port is not open, check your firewall configuration:

bash
# For UFW
ufw allow 8080

# For firewalld
firewall-cmd --permanent --add-port=8080/tcp
firewall-cmd --reload

4. Clear Browser Cache and Cookies

Sometimes the issue is related to browser caching:

  • Clear your browser cache and cookies
  • Try opening the panel in incognito mode
  • Use a different browser to access the panel

Checking Server Network Settings

1. Check DNS and Network Connections

Execute the following commands to diagnose network issues:

bash
# Check DNS resolution
nslookup your_server_IP

# Check routing
traceroute your_server_IP

# Check port availability from another device
telnet your_server_IP 8080

2. Check Xray Configuration

Check the Xray configuration file for errors:

bash
cat /etc/x-ui/xray/config.json | jq .

If you don’t have jq installed, install it:

bash
# For Ubuntu/Debian
apt install jq

# For CentOS/RHEL
yum install jq

3. Check SNI Keys

Make sure SNI keys are properly configured and don’t contain errors:

bash
# Check SNI configuration
grep -n "snis" /etc/x-ui/xray/config.json

If errors are found, edit the configuration file:

bash
nano /etc/x-ui/xray/config.json

Tip: When editing JSON files, use validators to check the correctness of the format.


Restoring Access to the Control Panel

1. Reset Access Password

If you’ve lost access to the control panel due to password issues:

bash
# Reinstall password
cd /usr/local/x-ui
./x-ui setting -username your_username
./x-ui setting -password your_password

2. Update 3x-ui to the Latest Version

Sometimes updating solves compatibility issues and errors:

bash
# Update 3x-ui
bash <(curl -Ls https://raw.githubusercontent.com/mhsanaei/3x-ui/master/install.sh)

3. Re-request SSL Certificates

If the issue is related to SSL/TLS:

bash
# Re-request certificates
acme.sh --reinstall-cert -d your_domain --force

Additional Measures and Prevention

1. Monitor Server Resources

Set up monitoring to track resource usage:

bash
# Install htop
apt install htop

# Check resource usage
htop
free -h
df -h

2. Regular Backups

Set up automatic backup of configurations:

bash
# Create backup script
nano /backup-x-ui.sh

Add the following commands to the script:

bash
#!/bin/bash
DATE=$(date +%Y%m%d_%H%M%S)
tar -czf /backup/x-ui_backup_$DATE.tar.gz /etc/x-ui/
echo "Backup created: x-ui_backup_$DATE.tar.gz"

Make the script executable and set up scheduled execution:

bash
chmod +x /backup-x-ui.sh
crontab -e

Add a line for daily backup:

0 2 * * * /backup-x-ui.sh

3. Check VPN Connection Logs

Check VPN logs to identify connection issues:

bash
# Check Xray logs
tail -f /etc/x-ui/xray/access.log
tail -f /etc/x-ui/xray/error.log

When to Contact Support

If none of the above measures helped, contact Aeza support with the following information:

  1. Your server ID on the Aeza platform
  2. Complete error logs of the 3x-ui service:
    bash
    journalctl -u x-ui --no-pager > x-ui-logs.txt
    
  3. Diagnostic results:
    bash
    uname -a
    lsb_release -a
    netstat -tulnp
    ss -tulnp
    
  4. Description of the sequence of events (what you did before the problem occurred)
  5. Screenshots of the problem, if available

Aeza support team can help in cases where the issue is related to their platform’s hardware or specific settings that cannot be directly changed through the terminal.

Conclusion

To resolve the 3x-ui panel loading issue, you need to sequentially perform the following steps:

  1. Check the status of the 3x-ui service and restart it if necessary
  2. Ensure that port 8080 is open on the firewall
  3. Clear the browser cache and try opening the panel in a different browser
  4. Check network settings and Xray configuration
  5. If necessary, update 3x-ui to the latest version
  6. Create a backup of important settings before making changes

Regular configuration backups and server status monitoring will help avoid similar issues in the future. If you cannot resolve the issue yourself, contact Aeza support with complete information about the problem.

Sources

  1. Official 3x-ui Documentation
  2. Xray Configuration Guide
  3. Aeza Usage Instructions
  4. Linux Firewall Guide
  5. systemctl Documentation