Our control panel server is currently not responding. This also affects the control panel API and www.webfaction.com. We’re working to restore service and will update this post when more info is available.
2018-01-06 07:04 UTC: The Control panel, API, and website are back online.
Researchers disclosed a security vulnerability affecting side-channel analysis of speculative execution on modern computer processors (CVE-2017-5715, CVE-2017-5753, and CVE-2017-5754). This issue affects home computers, phones, tablets and servers. As such, nearly everyone who uses such a device is affected. Our team is working on mitigating this, but we expect to have to reboot every machine shortly in order to protect your data.
We are looking to reboot every machine in our fleet at non-business hours over the next few days, we will soon contact you to let you know of the emergency maintenance window we have allocated for your machine.
We will keep you updated on this serious issue and give you as much notice for any emergency reboots as we possibly can.
We will keep this thread updated and apologize in advance for the inconvenience. Should you have any questions about this maintenance, feel free to open a support ticket and our team will be happy to help.
2018-01-05 17:28 UTC: All Singapore shared servers have been updated and rebooted.
2018-01-05 22:44 UTC: All EU shared and dedicated servers have been updated and rebooted.
2018-01-06 13:56 UTC: All USA shared and dedicated servers have been updated and rebooted.
2017-11-10 19:12 UTC: For the past few hours, we have been experiencing delays between the time a customer makes a payment and the time that the payment is posted to the customer’s account. The delay is occurring with our billing processor. If you make a payment and do not see it posted to your account immediately, please do not make an additional payment. The original payment should be posted within a few hours. We’ll update this post when the issue is resolved. Please contact WebFaction support if you have any questions or concerns.
2017-11-10 21:19 UTC: The issue has been resolved.
2017-10-06 17:13 UTC: Several of our cloud servers are currently offline due to an unknown issue. We’re investigating at this time and will update this post when more information is available. The affected servers are:
2017-10-06 17:32 UTC: Several cloud servers are back online after a reboot of the host hardware. The servers down at this time are:
2017-10-06 18:32 UTC: All of the affected servers are back online.
2017-10-11 12:59 UTC: We are taking the machine down for emergency maintenance to do a chassis swap.
On Monday, 4 September 2017 between 11:00 and 12:00 UTC, we will perform maintenance on our Control Panel.
During this time, the Control Panel and API will be temporarily unavailable. We apologize in advance for the inconvenience. Should you have any questions about this maintenance, feel free to open a support ticket and our support team will be happy to help.
2017-09-04 12:01 UTC: We are starting the maintenance.
2017-09-04 13:49 UTC: The maintenance is now over. Thank you for your patience, and if there are any issues please feel free to contact support by opening a ticket.
Effective on 1 September 2017, our SMTP server will reject any outgoing message that uses a sender address in the form of “firstname.lastname@example.org” (for example, “email@example.com”).
This change primarily affects customers who are using sendmail (including the PHP mail() function) to send messages without explicitly setting a sender address.
If you’re not sure if you will be affected by this change, then send yourself a message from the potentially-affected website, script, or other application, and then inspect the headers of the received message to ensure that the “From” header is a valid address not in the form of “firstname.lastname@example.org”, and does not use any of the domains listed in our email limitations and restrictions.
If you have any questions or concerns regarring this change, please open a support ticket and our team will be happy to assist.
2017-09-01 17:09 UTC: The new restrictions are now in effect.
2017-09-17 18:24 UTC: This change was disrupting outgoing email for several customers’ WordPress sites, so we’ve rolled it back and will re-deploy when that issue has been resolved.