mellonbot
MaintenanceMellonbot can fix

Config errors

Programs on your server read their settings from config files. A small typo — a missing semicolon or a wrong path — can stop the web server or database from starting, often right when it’s restarted after an update.

Get startedAll checks
At a glance
Group
Maintenance
Mellonbot
Can fix it
What it does
Pinpoints the line and fixes it, with a backup first.
Approval
Always with your OK

What you’ll notice

  1. 01A service won’t start after a change or an update
  2. 02The site went down right after someone edited a setting
  3. 03Errors like “syntax error” or “unknown directive” in the logs
  4. 04Reloading the web server fails

Why it usually happens

  1. 01A typo when editing a settings file
  2. 02A setting that a newer version no longer supports
  3. 03A file path that doesn’t exist any more
  4. 04Two settings files that conflict with each other

Fix it yourself

How to fix it by hand

Comfortable with a terminal? Here’s what an experienced admin would do. Start with the read-only commands.

  1. 01

    Test the nginx settings

    Prints the exact file and line of any mistake.

    sudo nginx -t
  2. 02

    Test Apache instead, if you use it

    Same idea for Apache.

    sudo apachectl configtest
  3. 03

    Read the service’s error

    The log shows why the service refused to start.

    sudo journalctl -u nginx -n 30 --no-pager
  4. 04

    Fix the line and reload

    After correcting the file, test again and only reload if the test passes.

    sudo nginx -t && sudo systemctl reload nginx

With Mellonbot

How Mellonbot fixes it

  • Tests your service settings and finds the exact file and line that’s wrong.
  • Explains the mistake in plain English.
  • Offers to fix the line — backing up the file first and testing before anything is reloaded.
  • The backup stays on your server if you’d rather go back.
What Mellonbot can and can’t do →

Not sure this is your problem? Ask us →

FAQ

Config errors: common questions

How do I check my nginx config for errors?

Run sudo nginx -t. It checks every settings file and tells you the file and line of any problem, without restarting anything.

Why did my site break after an update?

Updates sometimes restart services, and a settings mistake that went unnoticed before stops them from starting again.

Still have a question?

Every message goes straight to the founder.

Get in touch

Related

Often seen together

  1. 01Crashed servicesA program your site relies on, like the web server, has stopped.Mellonbot fixes
  2. 02DowntimeYour site stops answering visitors, often before you notice.Mellonbot fixes
  3. 03SSL certificatesThe padlock is about to expire, or already has, and visitors see a warning.Mellonbot fixes

Free plan · 100 credits to start

Let Mellonbot look after your website

Create a free account and connect your first site in a few minutes. Upgrade only when you need more.

  • No card needed
  • Leave any time

Prefer to talk first? Get in touch →

mellonbot — startfree
  • ✓ 100 credits to start
  • ✓ No card needed
  • ✓ One command to connect your site
Create free account

Already have an account? Sign in