Fix port 2224 and Nydus errors for my VPS Hosting
Your VPS Hosting requires port 2224 and Nydus (nydus-ex and nydus-ex-api) for operation. If either of these are blocked or modified, it can result in service disruption. A variety of factors can affect ports and services. So, while we can't provide an exhaustive list, we've highlighted key areas you can check if you encounter issues related to port 2224 or Nydus.
Check your resource usage
If your VPS Hosting resource usage (CPU, RAM, or disk space) is high, services may respond slowly or stop running.
- Check your resource usage and uptime.
- If you notice consistently high usage:
- Review your CPU and memory.
- Find areas of disk usage on WHM, Plesk, or SSH.
Check your firewall (WHM, Plesk, or Windows)
If you can access your control panel, check if port 2224 is open. Choose from the options below according to your control panel and firewall.
- Access WHM and check out how to edit your firewall from cPanel.net.
- Access Plesk and check out how to edit your firewall from Plesk.com.
- Connect to your Windows server and check out how to edit your firewall from Microsoft.com.
- If you have other firewalls installed, check your provider's support site.
Open port using SSH (Linux)
If you have a firewall installed and can use SSH, check if the port is open.
- SSH で VPS Hosting に接続します。
- rootユーザーに切り替えます。
- コマンドを実行:
sudo firewall-cmd --permanent --zone=public --add-port=2224/tcp
- コマンドを実行:
sudo firewall-cmd --reload
- 次のコマンドを実行して、ポートのブロックが解除されていることを確認します:
sudo firewall-cmd --list-ports
Restore from a backup
If you know a recent date when your server was fully operational, check if you have a backup to restore from.
Rebuild
If you've exhausted all options, you can rebuild the server. We recommend saving a backup on your computer, so you can upload your content after the rebuild.
- Check out how to create a backup from cPanel.net or Plesk.com.
- If you're familiar with command-line, you can create a backup with SSH.