Unable to authenticate
Surreal CMS reached your server, but the server wouldn't let it log in. You'll see this message when you publish, test the connection, or work with files:
Unable to authenticate with your server. Check the credentials in your site's connection settings, then use Test Connection to verify them.
How to fix it
- Open the site with Edit Site and check the username and password, or the access keys if your site is in a bucket. A space pasted at the end of a password is easy to miss.
- Try the same credentials in another app, such as an FTP client. If they fail there too, they're wrong. Your host or provider can reset them.
- Select Test Connection. Once it says Connection successful!, publish again.
If the credentials work in another app but not in Surreal CMS, check the causes for your protocol.
Common causes by protocol
| FTP |
Some hosts want the full username, such as user@example.com. Your FTP password isn't
always the same as the password for your hosting account.
|
|---|---|
| SFTP | Surreal CMS logs in with a password, not a key. If a key works in another app but a password doesn't, password login is turned off on the server. Ask your host to turn it on for the user you connect with. |
| WebDAV | The server may only accept Digest authentication. Ask your host to allow Basic authentication over HTTPS. |
| Amazon S3, Cloudflare R2, and DigitalOcean Spaces | The access key or secret key is wrong, or the key isn't allowed to read and write this bucket. With Amazon S3, make sure the bucket name in your IAM policy matches in both places. |
If you're still stuck, contact us and tell us which site you're publishing.