koyeb offline

[macosupdate]

I followed the instructions, but when I add the VPS, it shows as offline. I've tried multiple times, including changing the domain and using different Cloudflare accounts

koyeb Log Instance allocated in nomad Instance is unhealthy ./entrypoint.sh: line 15: /etc/resolv.conf: Read-only file system Generating RSA private key, 2048 bit long modulus (2 primes) .........................................................................+++++

• Restarting periodic command scheduler cron
• Stopping periodic command scheduler cron ...................................................+++++ e is 65537 (0x010001) ...done. Signature ok
• Starting periodic command scheduler cron subject=CN = data.xemgia.pp.ua ...done. Getting Private key 2023-09-14 16:20:30,021 CRIT Supervisor is running as root. Privileges were not dropped because no user is specified in the config file. If you intend to run as root, you can set user=root in the config file to avoid this message. 2023-09-14 16:20:30,021 INFO Included extra file "/etc/supervisor/conf.d/damon.conf" during parsing 2023-09-14 16:20:30,024 INFO RPC interface 'supervisor' initialized 2023-09-14 16:20:30,024 CRIT Server 'unix_http_server' running without any HTTP authentication checking 2023-09-14 16:20:30,025 INFO supervisord started with pid 41 2023-09-14 16:20:31,027 INFO spawned: 'agent' with pid 43 2023-09-14 16:20:31,029 INFO spawned: 'argo' with pid 44 2023-09-14 16:20:31,031 INFO spawned: 'nezha' with pid 45 2023-09-14 16:20:31,037 INFO spawned: 'nginx' with pid 46 2023-09-14 16:20:32,170 INFO success: agent entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2023-09-14 16:20:32,170 INFO success: argo entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2023-09-14 16:20:32,170 INFO success: nezha entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2023-09-14 16:20:32,170 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) Instance is healthy

VPS log

nezha-agent.service - Nezha Agent Loaded: loaded (/etc/systemd/system/nezha-agent.service; enabled; vendor preset: disabled) Active: active (running) since Thu 2023-09-14 08:23:02 GMT; 28s ago Main PID: 13597 (nezha-agent) Tasks: 4 Memory: 8.7M CGroup: /system.slice/nezha-agent.service └─13597 /opt/nezha/agent/nezha-agent -s data.xemgia.pp.ua:443 -p hMPHylW7uC4yVuWGrB --tls

Sep 14 08:23:02 instance-20220513-1644 systemd[1]: Stopped Nezha Agent. Sep 14 08:23:02 instance-20220513-1644 systemd[1]: Started Nezha Agent.

[fscarmen2]

Your Nezha dashboard with argo has been install correctly. And i have a test---upload data to your dashboard.
You should sheck your vps firewall / iptable. You can use /opt/nezha/agent/nezha-agent -s data.xemgia.pp.ua:443 -p hMPHylW7uC4yVuWGrB --tls -d to debug.

[macosupdate]

Thank you for your support. I tried a different server, and it's working fine. Your code is working well. There's only one server that's having issues, as mentioned earlier. I ran the command as you suggested, and although it's not due to your code, based on your experience, do you happen to know the cause of the issue? Here is the error message:

root@hk01:~# /opt/nezha/agent/nezha-agent -s data.xemgia.pp.ua:443 -p zoGiJNAOvbFOXAEG01 --tls -d
NEZHA@2023-09-20 09:17:07>> 检查更新： 0.15.6
NEZHA@2023-09-20 09:17:08>> 上报系统信息失败： rpc error: code = Unavailable desc = unexpected HTTP status code received from server: 502 (Bad Gateway); malformed header: missing HTTP content-type
NEZHA@2023-09-20 09:17:08>> Error to close connection ...

[fscarmen2]

I have no idea. Maybe you should try to check the inbound and outbound rules on that machine.