Investigating phpMyAdmin Issues

5:20PM UTC : Our Systems team has been able to identify the issue and completely resolve it. You should have no further issues with loading the Database via phpMyAdmin.

4:45 PM UTC  :  Our Systems team is currently investigating issues with phpMyAdmin. Currently, you will not be able to access your Database to make any kinds of manual changes. Once this issue has been resolved, we will update you here.

Notice of SFTP Changes

On Friday, August 9 at approximately 14:00 UTC, Pressable will change how account owners and site collaborators access and use SFTP.

The first change affects only account owners. Rather than having a single username and password to access all of the sites in an account, we will introduce separate usernames and passwords for account owners on each site. Site collaborators will not be affected by this change.

The second change affects all SFTP users. Currently when logging into an SFTP account, one must click the folder corresponding to your site to access it. After Friday, the folder structure will change to direct all users to the site root. In other words, if, for example, your site is called “mysite”, the site root is currently /mysite. On Friday, the site root will become: /

If you have any questions or concerns about these changes, please reach out to the Help Desk:

Site Creation/Clone Issue – “Domain not found”

16:14 UTC – We have been made aware of an issue when creating or cloning sites which is resulting in the message “Domain not found” being displayed instead of the site’s content. Our Systems Team are actively working on resolving the issue.

17:35 UTC – Our Systems Team have corrected this issue and it should no longer occur. If you find any of your sites were affected by this please submit a support ticket and we will be able to apply a fix to the site for you.

Connection Timeout on limited number of sites

8:45pm UTC – Internal monitoring alerted our systems team to an issue resulting in connection timeouts on a limited number of Pressable hosted websites. They have identified the issue and taken action to correct it.
8:52pm UTC – The systems team confirms that all affected sites are back online.

If you have any questions or concerns, you may contact us at

502 Bad Gateway Errors (Resolved)

15:05 UTC : Our systems team has been able to identify and completely resolve the issue that was causing a very limited number of 502 bad gateway errors.

14:48 UTC – Our systems team is investigating 502 Bad Gateway errors on a limited number of sites on our platform. We will update with more information as soon as it becomes available.

502 Bad Gateway Errors

14:13 UTC – We have received reports of sites on our platform receiving 502 Bad Gateway errors. Of these sites, all have their DNS managed by Cloudflare, which has informed its users that they are experiencing network issues:

Investigating – Cloudflare is observing network performance issues. Customers may be experiencing 502 errors while accessing sites on Cloudflare.

We are working to mitigate impact to Internet users in this region.
Jul 2, 13:52 UTC

For further information, please see their status page.

If you have any questions or concerns, you may contact us at