SupportConsole
llms.txtSign in

Troubleshooting

Servers that will not connect, failed deploys, 502s and certificate problems.

Guides

Fix a server that will not connectWork out why SrvYard shows a server as Disconnected or cannot finish installing it: the reason SrvYard recorded, the checklist, the commands to run in your provider's console and how to check again.Find out why a deployment failed and fix itOpen the failed deployment, read the first error in its output, use the Why it failed explanation, match the message to the usual causes and redeploy or roll back safely.Fix a 502 Bad Gateway on your siteWork out why Nginx cannot reach your application: check the services, match the PHP version, read the Nginx error log and restart the right process, with the usual causes after a deployment.Find out why a certificate failed and issue it againRead the failure on the SSL tab, check DNS, port 80, rate limits and DNS validation in that order, then request the certificate again and make sure the site is not stuck redirecting to a missing certificate.Fix the wrong site, an empty page or a placeholder after a DNS changeFind out why a domain shows another site, a blank connection error or the "site created" placeholder after you changed DNS, and check each link in the chain: DNS, the server, the domain on the site, and the deployment.Fix queued jobs that are not being processedCheck that a queue worker exists and is running, restart it after a deployment, match its connection and queue names to your application, and tell stuck jobs from jobs that fail.Fix a full disk, low memory or a slow serverRead the Monitoring page to tell a full disk from a memory or CPU problem, find what uses the space, free it safely, reduce kept releases, and set monitors so the next warning comes by email.

Frequently asked

What should I do when a server shows Disconnected?

Read the reason SrvYard recorded, then work through the checklist on the server page, running the repair commands in your provider's console if needed. SrvYard rechecks about every five minutes and returns the server to Ready by itself. See Fix a server that will not connect.

A deployment failed. Where do I start?

Open the deployment and read the first error line in its output, not the last. The Why it failed card, where your plan includes it, gives a plain-language hint. Then match the message to the usual causes. See Find out why a deployment failed and fix it.

What does a 502 Bad Gateway mean?

Nginx is running but the program behind it, PHP-FPM or a Node.js process, did not answer. Check the services, that the site's PHP version exists, and the Nginx error log. It often follows a deployment or a PHP change. See Fix a 502 Bad Gateway on your site.

My certificate failed. What do I check first?

DNS, then port 80, then rate limits, then DNS validation, in that order. A failed request never replaces a working certificate, but a site set to Force HTTPS with none gives visitors an error. See Find out why a certificate failed and issue it again.

My domain shows the wrong site or a placeholder. Why?

Three different problems look alike: DNS still points at another machine, Nginx did not recognise the name, or the site was never deployed. The SrvYard placeholder means the request arrived but nothing was deployed. See Fix the wrong site, an empty page or a placeholder after a DNS change.

Why are my queued jobs not running?

The worker is missing or stopped, listens to a different connection or queue than your app uses, runs old code, or QUEUE_CONNECTION is sync. Check the worker on Processes, then restart it. See Fix queued jobs that are not being processed.

My server disk is full. What can I safely remove?

First find what uses it on the Monitoring tab and with du, then clear old logs and caches, and lower Deployments to keep so fewer releases stay. Take a backup before deleting anything you did not create. See Fix a full disk, low memory or a slow server.