- Fixed price
- $69 per incident
- Same day
- $109
- People answer
- daily 13:00-21:00 CET
- No fix
- no fee
Server Rescue: a broken server back up, at one fixed price
Server down, hacked, certificate expired or mail not arriving? We find the cause and fix it for a flat $69 per incident. If we cannot fix it, you pay nothing. A same-day start is listed at $109.
Server Rescue is a one-off repair job for a server that has stopped doing what it should: the site returns an error, mail no longer leaves or arrives, a certificate has expired, or someone has got in who should not be there. You need it when the thing is broken today and there is no administrator to call. The price is fixed and published, and if we cannot fix the problem you pay nothing.
You describe the symptoms in a brief and tell us the provider, the operating system and how the machine can be reached. We confirm the scope and the price, and work starts once you accept. Diagnosis comes first: likely causes are ranked, and read-only checks run before anything is changed. Then the fix is applied and verified. The work is drafted by software and checked by a person before the result reaches you.
/ Who it is for
Anybody whose site, mail or certificate has stopped working and who has nobody to ring. You do not need to know what is wrong, only what you see.
/ What you get
- A diagnosis that names the likely causes, ranked with the most probable one first.
- The fix carried out for the cause that turned out to be the real one, not a list of suggestions.
- The diagnostic plan and the fix procedure written down, in the order the steps were taken.
- Verification steps after the fix, so you can see for yourself that the service is back.
- A no fix, no fee rule: if we cannot get it working again, you pay nothing.
- A same-day start if you need one, listed at $109.
/ What is not included
- This covers one incident. If the server breaks again next month, that is a second job.
- It is not ongoing care: watching the server month after month is what the monthly plans are for.
/ What we check before it ships
- Likely causes are ranked, most probable first, before anyone touches the server.
- Read-only diagnostic commands come before any change, in a safe and fixed order.
- No destructive command is run without a backup or another safeguard in front of it.
- Nobody asks you to paste a password or a secret in plain text; access is handed over securely.
- Every fix ends with explicit verification steps that show the service is working again.
/ How it works
- 1.You describe what you see: the error, since when, and what changed last. Add the provider, the operating system and how the server can be reached. No passwords in the form.
- 2.We confirm the scope and the fixed price. Work starts only after you accept.
- 3.Diagnosis first: likely causes are ranked, and read-only checks run before anything is changed.
- 4.The fix is applied, with a backup or another safeguard in front of any risky step.
- 5.You get the steps in the order they were taken and the checks that show the service is back. If we could not fix it, you pay nothing.
/ What we need from you
- BriefTell us what you need.
- Access / environment (optional)Provider, OS, how we can reach it. Never paste passwords here - we'll arrange secure handover.
- Content / source (optional)
/ Questions people ask
What does Server Rescue cost?
$69 per project, where a project is one incident. The same-day option is listed at $109. The price is fixed and published, and it is confirmed together with the scope before any work starts. If we cannot fix the problem, you pay nothing.
What problems does Server Rescue cover?
A server or site that is down or returns an error, mail that no longer leaves or arrives, an expired certificate, and a break-in. One job is one incident.
How fast do you start?
People answer every day from 13:00 to 21:00 CET, which is 7am to 3pm Eastern. A start on the same day is listed at $109.
How do I order it?
You submit a request describing what is broken. We confirm the scope and send the final price for you to approve. Work starts only after you accept. When the fix is in place you review the result and can ask for changes before you approve it.
What access do you need, and how do I give it?
Tell us the provider, the operating system and how the server can be reached. Do not paste passwords into the request form. We arrange a secure handover of credentials separately, and no step in our work asks for a secret in plain text.
What if you cannot fix it?
Then there is no fee. That rule is part of the plan, not a favour granted case by case. The delivery also says plainly what could not be done, because that is how every job here is closed: nothing is left out quietly.
/ Read next
- Server down: what to check firstThe checks to run before you hand it over, and what not to do.
- 502 Bad Gateway on nginxReading the error log line, and the usual fixes for PHP-FPM and app servers.
- Error establishing a database connectionWhen WordPress cannot reach MySQL: why the database stopped and the four lines in wp-config.php.
- Website hacked: the first stepsWhat to do in the first hour, and why a restore alone lets them back.
- SSL certificate expired: the fixHow to confirm it, why renewal stopped and how to renew with Certbot.
- Free server health checkThe certificate, the https redirect, the security headers and the response time of any domain, read from outside.
- Security hardeningSo it does not happen again: firewall, SSH, TLS, updates and backups reviewed and changed, with a written report.
- Managed server plansWhen the server needs looking after month by month, not one incident at a time.
