Documentation

Unable to connect

Surreal CMS couldn't reach your server, or the server didn't answer in time. You'll see this message when you publish, test the connection, or work with files:

Unable to connect to your website. Please double-check your connection details and make sure the server is online.


How to fix it

  1. Make sure the server is online. A website that loads in a browser doesn't prove that its FTP or SFTP server is running, so try connecting with another app too.
  2. Open the site with Edit Site and check the host and port. Don't put ftp:// or sftp:// in the host.
  3. If your host limits access by IP address, allow 162.243.9.115. Every connection from Surreal CMS comes from that address.
  4. Select Test Connection, then publish again.

Common causes by protocol

FTP with TLS/SSL The server has to support explicit TLS, version 1.2 or newer. Implicit FTPS, which usually runs on port 990, isn't supported. If your server only offers that, use SFTP if you can.
SFTP SFTP almost never runs on port 21, which is for FTP. A tool like fail2ban may have blocked 162.243.9.115 after failed logins. The server's SFTP subsystem also has to be turned on.
WebDAV The host has to start with https:// and include the port if your server uses one. The server's certificate has to be valid and not expired.
Amazon S3 and DigitalOcean Spaces Check the bucket name and the region. The region has to be the one the bucket was created in.
Cloudflare R2 Check the bucket name and your account ID.

If you're still stuck, contact us and tell us which site you're publishing.