22:19 UTC – In preparation for our server migration, the Pressable systems team implemented network modifications that have caused some sites with WordPress security plugins to throw 403 Forbidden errors. If you are unable to access your site due to a 403 Forbidden error, please contact the Help Desk for further assistance: firstname.lastname@example.org
21:34 UTC – We are investigating reports of sites experiencing 403 Forbidden Errors. As soon as more information becomes available, we will update this post.
03-Sept – 21:25 UTC – We’ve added a list of FAQs regarding our server migration. If you have any additional questions, please reach out to email@example.com.
28-Aug – 13:30 UTC – All new Pressable sites (excluding clones of existing sites) are being hosted in our new infrastructure. Some functionality is temporarily unavailable, while other functionality has been removed. Please read below for more information, and contact us at firstname.lastname@example.org if you have any questions.
23-Aug – 18:34 UTC – In anticipation for service upgrades in the coming days and weeks ahead, some features will become temporarily unavailable on newly created and existing sites. Other features will be sunsetted.
Which features will become temporarily unavailable on existing sites?
Once we begin the migration of sites into our new infrastructure, the features that are temporarily unavailable on newly created sites will also become temporarily unavailable on existing sites.
Which features will become temporarily unavailable on newly created sites, including clones?
phpMyAdmin Access – You can use the WP phpMyAdmin plugin as an alternative. (9/3: Now available.)
- Git – You can use DeployHQ.com instead.
Collaborators (8/27: Now available.)
Cloning – You may be able to use our Pressable Automated Migration plugin to copy an existing site. (8/27: Now available.)
How long will these features be temporarily unavailable?
We anticipate that this feature unavailability will be brief. Our team is working hard to restore each feature as quickly as possible, and we will update this post when each feature is restored.
Which features will be sunsetted?
The following will become unavailable on new sites and will be removed from existing sites once they are migrated to our new infrastructure.
- Offsite Backups
- Pressable will no longer provide offsite backups via S3 or Rackspace. We recommend plugins like Jetpack or BlogVault for backups.
- Custom SSL Certificates
- Sites with EV and OV certificates will continue to be able to use them until expiry. Sites with other types of certificates have been transitioned to our Let’s Encrypt certificates.
- Disabling SSL
- All sites will be required to use SSL.
If you have any questions or experience issues creating new sites, please contact us at email@example.com. Additionally, please also take a moment to update your email address in MyPressable Control Panel to ensure you receive all future communications regarding the server migration.
17:50 – At approximately 17:27 UTC, we detected sites experiencing connection timeouts on our platform. This was due to a web server that became unresponsive. When this occurred, our load balancers automatically failed traffic over to another web server. Some sites may have experienced brief connection issues. The issue is now resolved. If you continue to experience any issues, please reach out to firstname.lastname@example.org.
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: email@example.com
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.
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 firstname.lastname@example.org.
16:00 UTC – The issue is now resolved. If you continue to experience problems, please contact email@example.com for further assistance.
14:37 UTC – The systems team is investigating 502 Bad Gateway errors affecting a limited number of sites on our platform.