Node information for Xray doesn't work

[maxekspb]

I updated the dashboard and installed X-Ray. Now I'm seeing this, even though the VPN is working.

And are there any ways to change the node protocol from hy2 to xray without reinstalling? The first time I tried just choosing xray instead of hy2 and configuring it automatically, it didn't work. Now, for some reason, hy2 has stopped working for me in all Linux clients, it only works on the phone. I'm thinking about migrating the node that is installed on the server with the panel to xray. What is the best way to do this?

[ClickDevTech]

Hi! From the screenshot I can see the agent shows "installed" but status is OFFLINE — this means the panel cannot reach the CC Agent on the server.

To fix this:

1. Check if the agent is running on the server:

systemctl status cc-agent

2. If not running — start it and check logs:

systemctl start cc-agent
journalctl -u cc-agent -n 50

3. Make sure port 62080 is open:

ss -tlnp | grep 62080
ufw allow 62080/tcp  # if using ufw

If nothing helps — click "Auto Setup" in the panel, it will reinstall the agent (users won't be affected).

---

Migrating from hy2 to xray:

Yes, it's possible, but there's a catch — these are different protocols, clients are not compatible. Best approach:

1. Create a new node with Xray type (don't edit the existing one)
2. Add it to the same groups
3. Click "Auto Setup"
4. Users will get both servers in their subscription
5. After testing — deactivate the hy2 node

If you want to replace the existing node:

1. Change node type to Xray in settings
2. Configure parameters (security: reality/tls, transport: tcp/ws/grpc, etc.)
3. Save and click "Auto Setup"
4. All users will need to update their configs

---

About "hy2 not working on Linux":

This is a separate issue, not related to the panel. Possible causes:

• Client updated and config format changed
• ISP blocking
• Certificate issues

Which client are you using? Share the client logs and we can take a look.

[maxekspb]

Hi.

root@reverent-hugle:/usr/local/bin# ls
cc-agent xray
root@reverent-hugle:/usr/local/bin# cat cc-agent
404 - Not Found
root@reverent-hugle:/usr/local/bin#
look like it can't download agent.

error when I tried to auto setup.
I deleted node, reinstalled os on my vps and launched auto-setup again. Nothing's changed.

root@reverent-hugle:/usr/local/bin# cat cc-agent
404 - Not Found
root@reverent-hugle:/usr/local/bin#

I tried to change hy2 to xray.
Xray conflicted with the panel due-to same port.
Mar 16 08:13:38 hungry-northcutt.1cent.network systemd[1]: Started xray.service - Xray Service.
Mar 16 08:13:38 hungry-northcutt.1cent.network xray[104325]: Xray 26.2.6 (Xray, Penetrates Everything.) 12ee51e (go1.25.7 linux/amd64)
Mar 16 08:13:38 hungry-northcutt.1cent.network xray[104325]: A unified platform for anti-censorship.
Mar 16 08:13:38 hungry-northcutt.1cent.network xray[104325]: 2026/03/16 08:13:38.684923 [Info] infra/conf/serial: Reading config: &{Name:/usr/local/etc/xray/config.json Format:json}
Mar 16 08:13:38 hungry-northcutt.1cent.network xray[104325]: Failed to start: app/proxyman/inbound: failed to listen TCP on 443 > transport/internet: failed to listen on address: 0.0.0.0:443 > transport/internet/tcp: failed to listen TCP on 0.0.0.0:443 > listen tcp 0.0.0.0:443: bind: address already in use
Mar 16 08:13:38 hungry-northcutt.1cent.network systemd[1]: xray.service: Main process exited, code=exited, status=255/EXCEPTION
Mar 16 08:13:38 hungry-northcutt.1cent.network systemd[1]: xray.service: Failed with result 'exit-code'.

After restart the server xray took place and port for panel. Now I have working xray and not working panel.
Now is it possible to run xray and panel on one server?

[maxekspb]

I decided to reinstall panel and OS on my vps.
I install panel, hy2 node on panel server, add xray node on different server.
And in my subscription in vpn apps didn't show up xray node, I decided to reboot vps with panel and now docker container with backend doesn't start automatically. I manually started the container, it rebooted endlessly and returned this log.

09:29:42 [INFO]: [SSHPool] Initialized
09:29:47 [ERROR]: [Server] Startup failed: getaddrinfo EAI_AGAIN mongo
09:29:48 [INFO]: [SSHPool] Initialized
09:29:53 [ERROR]: [Server] Startup failed: getaddrinfo EAI_AGAIN mongo
09:29:54 [INFO]: [SSHPool] Initialized
09:29:59 [ERROR]: [Server] Startup failed: getaddrinfo EAI_AGAIN mongo
09:30:01 [INFO]: [SSHPool] Initialized
09:30:06 [ERROR]: [Server] Startup failed: Server selection timed out after 5000 ms
09:30:08 [INFO]: [SSHPool] Initialized
09:30:13 [ERROR]: [Server] Startup failed: getaddrinfo EAI_AGAIN mongo
09:30:15 [INFO]: [SSHPool] Initialized
09:30:21 [ERROR]: [Server] Startup failed: getaddrinfo EAI_AGAIN mongo
09:30:25 [INFO]: [SSHPool] Initialized
09:30:30 [ERROR]: [Server] Startup failed: Server selection timed out after 5000 ms
Then I tried to reboot all containers and backend didn't start bc of this. But it's fresh install. there are nothing but panel and hy2 node.

[maxekspb]

About hy2 on linux. I did't find any errors. I'm using Happ client. I noticed that the sites don't open, but for example I can ping google, I can send a message in telegram (can't send media).

[maxekspb]

I tried Koala Clash client and in its logs I found it

[ClickDevTech]

Hi @maxekspb! Thanks for the detailed report! it helped us track down several real bugs. All fixes are now in the latest release.

What was fixed

1. cc-agent showing "404 - Not Found"

This was a bug in the download script. curl was called without the -f (fail) flag, so when the download URL returned HTTP 404, curl saved the error page body ("404 - Not Found") as the binary file. The file was non-empty, passed the size check, got chmod +x, and the service tried to run a text file as a binary.

Fix: Added -f flag to curl (exits with error on HTTP failures), added ELF binary validation after download, and cleaned up the fallback logic.

2. Backend crash loop after reboot (getaddrinfo EAI_AGAIN mongo)

Docker's depends_on only waits for containers to start, not for services to be ready. After a VPS reboot, MongoDB takes 5-15 seconds to initialize, but the backend was already trying to connect and crashing.

Fix: Added health checks for MongoDB and Redis in Docker Compose (condition: service_healthy), so the backend now waits until databases are actually accepting connections. Also added retry logic with exponential backoff in the app itself as a safety net.

3. Xray + Panel port conflict on same server

When setting up an Xray node on the same VPS as the panel with port 443, Xray would conflict with Caddy (which uses 443 for the panel). After reboot, whichever service starts first takes the port.

Fix: Auto Setup now detects same-VPS setups and blocks port 443/80 for Xray with a clear error message suggesting port 8443 instead. The node form also shows a visual warning when this conflict is detected.

Regarding your other questions
Xray node not showing in subscription - this was a cascade from bug #1. The agent was broken → node stayed "offline" → subscription skipped it. With the agent fix, this should work correctly now.

Running Xray and Panel on one server - yes, it's possible! Just use a different port for Xray (e.g. 8443 instead of 443). The panel will warn you if there's a conflict.

hy2 not working on Linux (Happ client) - since you can ping and use Telegram but websites don't open, this sounds like a DNS or MTU issue on the client side, not a panel bug. Try switching to a different client (Hiddify, NekoBox) to isolate the problem.

Please update your panel (git pull && docker compose up -d --build) and let us know if the issues persist!

[maxekspb]

Thank you for your quick reply! I updated according to the instructions safe-update.md , changed the node from hy2 to xray with a port change. Now I only use xray, and the problem with finding a client can also be said to be solved.