Quick answers to the most common issues. If you can't find what you need, reach out directly.
Server offline or unreachable
Agent stopped, firewall blocking connections, or IP changed.
Deployment not starting
Missing env vars, build errors, or port conflicts.
SSH key authentication failing
Wrong key format, permissions issue, or mismatched user.
High CPU or memory usage
Check which process is consuming resources via the Metrics tab.
This usually means the Symplax agent on your server has stopped. SSH into your server and run the agent restart command. If the agent was never installed, follow the Quick Start guide to install it.
Check that the IP address and port are correct, the SSH user has permission to connect, and your firewall allows inbound connections on port 22 (or your custom SSH port). Make sure you are using the right authentication method — SSH key or password.
This can happen if the build process ran out of memory or the build command exited with an error. Open the app page, go to the Logs tab, and check the build output for the specific error. Common causes are missing environment variables or a failing npm install.
Metrics are sent by the agent installed on your server. If the agent is online but metrics are missing, try restarting the agent. Metrics are stored every 10 seconds and displayed in real time via WebSocket.
Deleting a server removes it from Symplax but does not touch your actual VPS. You can re-add the server at any time by going to Servers → Add Server and following the connection steps again.
Go to Settings → Billing to manage your subscription. Changes take effect immediately and are prorated for the current billing period.
Reach us on X for the fastest response. We typically reply within a few hours.
Message us on XIn-depth guides covering every feature — from connecting servers to CI/CD pipelines.
Browse Documentation