Fix 3x-UI Panel Not Loading on Aeza Servers (Quick Guide)

If your 3X-UI panel isn’t loading on an Aeza server—showing infinite spins at IP:8080 over home internet—it’s often due to firewall blocks, service crashes, or Aeza’s strict port/SNI restrictions. Start with an SSH tunnel to access the panel securely, then check X-UI/Xray status and reset configs. For the VPN dropping after days with whitelisted SNI in Amnezia, swap to another SNI like www.apple.com and test legit ports like 443.

Contents

• Quick Diagnosis for 3X-UI Panel Not Loading
• Access Panel via SSH Tunnel
• Check and Restart Services
• Firewall and Port Fixes
• Aeza SNI Whitelist for VPN Stability
• Reset Configs and Clear Logs
• VPN-Specific Troubleshooting in Amnezia
• Prevention Tips
• Sources
• Conclusion

Quick Diagnosis for 3X-UI Panel Not Loading

Staring at that endless loading wheel on your 3X-UI panel? Frustrating, right—especially when your Aeza VPN was humming along with a whitelisted SNI key in Amnezia just days ago. This hits hard on Aeza servers because they aggressively block non-standard ports and DNS resolutions from home networks.

First off, confirm it’s not your local setup. Try accessing http://YOUR_SERVER_IP:8080 directly (skip any domain). Still spinning? SSH into the server and run systemctl status x-ui. If it’s inactive or errored, that’s your smoking gun. The official 3X-UI wiki nails it: panel hangs mean stopped services, firewall locks, or Xray config glitches.

Your VPN cutting out after stable days screams Aeza’s evolving blocks. They whitelist specific SNIs and ports (80, 443, 8080), but even those fail over time. More on that soon.

Access Panel via SSH Tunnel

Can’t reach the panel at all? SSH tunnel to the rescue—bypasses home network firewalls and Aeza quirks entirely. Open PowerShell or cmd on Windows, then:

ssh -N -L 8080:localhost:8080 root@YOUR_SERVER_IP

Hit enter, type your server password (cursor blinks, no echo), and boom—visit http://localhost:8080 in your browser. Panel loads instantly.

Users on Habr Q&A swear by this for Aeza: “Panel infinite load fixed via SSH tunnel—works every time under restrictions.” Why home internet fails? DNS interference or outbound port blocks. Tunnel routes traffic through SSH-encrypted path. Pro tip: Add -p PORT if SSH isn’t 22.

Once in, you can diagnose VPN drops too. Disconnect tunnel with Ctrl+C when done.

Check and Restart Services

Panel access secured? Dive into services. SSH in and run:

systemctl status x-ui
systemctl status xray

Inactive? Start 'em:

systemctl start x-ui
systemctl enable x-ui # Auto-start on boot
systemctl restart xray

From a GitHub issue thread, panels go “Not Running” post-install due to autostart fails—restarting fixes 80% of cases. Logs reveal the rest: tail /usr/local/x-ui/access.log and /error.log. Spot 500 errors or DB locks? Clear bloated logs: echo "" > /usr/local/x-ui/access.log.

Xray config errors kill panels too. In-panel, hit “Reset to Default Configuration” under settings. Regenerates /usr/local/x-ui/config.json cleanly.

Firewall and Port Fixes

Aeza loves firewalls. Ensure port 8080 open:

ufw allow 8080/tcp
ufw status

If ufw’s off, check iptables or Aeza’s panel for blocks. The Aeza wiki stresses legit ports only: 80, 443, 8080, 8443. Non-standard? Blocked fast.

Home network firewall? Test from mobile data. Still no? Provider-level interference—tunnel’s your friend.

Aeza SNI Whitelist for VPN Stability

Your VPN worked days on whitelisted SNI, then poof. Aeza scans and rotates blocks. From their VK announcement: Switch SNI to fresh whitelists like www.apple.com, yahoo.com, or microsoft.com. In 3X-UI panel > Inbound > Edit VLESS > Reality tab, update SNI, save, restart Xray.

Ports matter: Stick to 443/80. uTLS fingerprint? Swap Android to Firefox/Chrome in Amnezia client. Test: Connect button turns green if good.

Amnezia-specific: Export new vless:// config from panel, import, replace localhost with server IP if needed. Aeza guide confirms: “VPN stops after days? New SNI from whitelist.”

Reset Configs and Clear Logs

Desperate measures: Panel menu > Reset Settings. Wipes config.json, rebuilds from scratch. Re-add inbounds/users.

Zero traffic showing? Same reset button—flushes bad rules. GitHub wiki: “All users zero traffic: Reset config, re-add rules.”

Stale DB? Rarely, but x-ui setting -reset via CLI. Backup first: cp -r /usr/local/x-ui /backup.

VPN-Specific Troubleshooting in Amnezia

Panel fixed, VPN still dead? Amnezia logs: Check client debug for handshake fails. Common: SNI expired, or Aeza detected pattern.

Regen UUID/key in 3X-UI > Users > Edit. Export fresh sub/link. Client-side: Forget profile, re-add.

Reality protocol? Verify dest/shortIds match panel. Habr users: “Worked on built-in Xray, failed in 3X-UI—SNI swap + port 443 fixed.”

Test ping: curl -v ipinfo.io via VPN. No IP change? Routing fail—panel Routing tab, reset rules.

Prevention Tips

Don’t let this repeat. Cron job for restarts: crontab -e, add 0 */6 * * * systemctl restart x-ui xray. Monitor: Telegram bot from 3X-UI menu.

Fail2ban: Install via panel—blocks brute-force. Multi-SNI rotation script? Community GitHubs have 'em.

Aeza tip: VLESS+Reality only now—others blocked. Update 3X-UI: x-ui update.

Sources

1. Common questions and problems · MHSanaei/3x-ui Wiki · GitHub
2. Setting up VLESS in 3x-ui | AézaWiki
3. Что делать, если не грузит 3x-ui панель? — Хабр Q&A
4. Возвращаемся в строй! | Хостинг Aéza | VK
5. Panel and xray : not runnig · Issue #3213 · MHSanaei/3x-ui

Conclusion

Fixing a non-loading 3X-UI panel on Aeza boils down to SSH tunnel for access, service restarts, firewall tweaks, and SNI refreshes for VPN uptime. You’ll be back online in 15 minutes—test thoroughly, rotate whitelists proactively. Stay ahead of blocks, and your Amnezia setup runs smooth. Questions? Hit the sources or community.