When publishing fails, EverWeb shows an error with a Copy To Clipboard button. Press it and keep the text. If you contact us, paste the whole thing: a screenshot won't show everything we need.
Is the error one of these?
| You see | Go to |
|---|---|
| Error 28, Operation timeout, "may have been blocked" | Error 28 |
| Protocol error, publishing to EverWeb Hosting | Protocol error: EverWeb Hosting |
| Protocol error, publishing to another host | Protocol error: FTP |
| Your plan has expired, or the version isn't within your upgrade period | Which version can I use? |
| Your hosting disk space is full | Contact us and we'll check what's using your space, or upgrade your plan |
| Keeps asking you to sign in | Sign out and back in at EverWeb > Settings on a Mac, or Edit > Options on Windows > Account |
Otherwise, try these in order
Try publishing after each step.
- Clear any block on your connection. Sign in to your client area on this computer.
- Turn off anything that reroutes your connection. That means any VPN (NordVPN, ExpressVPN, Surfshark), and iCloud Private Relay on a Mac (how). Then repeat step 1.
- Try another network, such as your phone's hotspot. Hotels, cafes and offices often block publishing.
- Check Use passive publishing connections. Go to EverWeb > Settings on a Mac, or Edit > Options on Windows > Publishing. Keep it on normally. If it is off, turn it on. If it is on and step 5 doesn't help, try it off.
- Set Maximum Connections to 1 on the same tab, wait 15 to 20 minutes, then publish.
- Turn off Use Secure Publishing under the Account tab. Turn it back on when you're on a network that allows it.
- Check your firewall or security app. Little Snitch, Norton, and on Windows, Windows Defender can block publishing. Allow EverWeb or pause it briefly.
- Keep EverWeb in front while it publishes, on a slow connection.
Publishing to another web host
Also check these under File > Edit Publishing Settings:
- Username and Password are your FTP login. This is often different from the login to your host's website.
- Directory/Path is correct. It is often
public_html, but ask your host. It is not your website address. - Protocol and Port match what your host supports. Usually port 21 for FTP and FTP with SSL/TLS, and 22 for FTP with SSH.
- Press Test Connection.
Try the same login in a free FTP app such as Cyberduck. If that fails too, the host can help.
Run the diagnostics
In EverWeb 4.5 or later, go to Help > Publishing Connection Diagnostics. It tests your connection and writes a report.
Contact us
Send the full error text, the diagnostics report, and a full-screen screenshot of File > Edit Publishing Settings. Tell us which steps you tried.