We are taking down Web564 to replace a failed memory module. Downtime should be 15 minutes or less.
2017-08-20 16:13 UTC: Shutting down the machine.
2017-08-20 16:25 UTC: The memory has been replaced and server is back online.
Effective on 1 September 2017, our SMTP server will reject any outgoing message that uses a sender address in the form of “user@host.webfaction.com” (for example, “bob@web555.webfaction.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 “user@host.webfaction.com”, 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.
2017-07-27 21:16 UTC: Microsoft is currently blocking and/or throttling mail sent via our SMTP to hotmail.com, outlook.com, msn.com, and other email domains hosted by Microsoft. We’re working with Microsoft to resolve this issue and will update this post when more information is available.
2017-08-02 18:02 UTC: We’ve set up some downstream SMTP relays to help with delivery while we continue to work to get the main SMTP IP address unblocked.
2017-08-03 16:54 UTC: Mail sent via our SMTP to hotmail.com, outlook.com, msn.com, and other email domains hosted by Microsoft is no longer being blocked or throttled. We’ll continue to monitor.
2017-07-25 22:21 UTC: a filesystem issue on one of our POP/IMAP proxies is disrupting mail service for some customers. We’re working to restore service and will update this post when more info is available.
2017-07-25 23:09 UTC: The faulty mail proxy is back online. We’ll continue to monitor.
2017-07-27 21:15 UTC: We’ve seen no further issues with the POP/IMAP proxies.
We will be performing power maintenance on Web599 between 23:00 UTC July 16, 2017 and 00:00 UTC July 17, 2017.
Connectivity to the server will be interrupted for up to one hour during the maintenance window. 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-07-17 00:08 UTC: The maintenance has begun.
2017-07-17 00:21 UTC: The maintenance is complete.
We are currently investigating the issue and will update as soon as we have further details.
2017-06-30 18:37 UTC: Web523 is currently in a rescue environment and our data center team are troubleshooting.
2017-06-30 20:53 UTC: Web523 had a corrupted kernel. The problem has been resolved and the server is now back online.
We will be performing power maintenance on the following servers between 21:00 UTC July 2, 2017 and 00:00 UTC July 3, 2017:
wf-207-38-86-39
wf-207-38-86-40
wf-207-38-86-43
wf-207-38-86-47
wf-207-38-86-48
wf-207-38-86-49
wf-207-38-86-73
wf-207-38-86-75
wf-207-38-86-76
wf-207-38-86-78
wf-207-38-86-79
wf-207-38-86-85
wf-207-38-86-88
wf-207-38-86-90
wf-207-38-86-92
wf-207-38-86-93
wf-207-38-86-94
wf-207-38-86-98
wf-207-38-86-102
wf-207-38-86-103
wf-207-38-86-104
wf-207-38-86-105
wf-207-38-86-106
wf-207-38-86-107
wf-207-38-92-110
wf-207-38-86-178
wf-207-38-86-180
wf-207-38-86-191
wf-207-38-86-193
wf-207-38-86-194
wf-207-38-86-195
wf-207-38-86-196
wf-207-38-86-197
wf-207-38-86-198
wf-207-38-86-199
wf-207-38-93-249
wf-207-38-86-77
wf-207-38-86-135
wf-207-38-86-138
wf-207-38-86-140
wf-207-38-86-145
wf-207-38-86-147
wf-207-38-86-149
wf-207-38-86-150
wf-207-38-86-159
wf-207-38-86-160
wf-207-38-86-164
wf-207-38-86-165
wf-207-38-86-166
wf-207-38-86-167
wf-207-38-86-168
wf-207-38-86-170
wf-207-38-86-171
wf-207-38-86-175
web590
web591
web592
web593
web594
web595
web596
web597
web598
web600
web601
web602
web603
Connectivity to the servers will be interrupted for up to one hour during the maintenance window. 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-07-02 23:14 UTC: The maintenance has begun.
2017-07-02 23:56 UTC: web590-web592 are complete and back online.
2017-07-03 00:11 UTC: web593-web596 are complete and back online.
2017-07-03 00:43 UTC: web597, web600-web603 are complete and back online.
2017-07-03 02:51 UTC: All servers are back online.
2017-06-20 20:44 UTC: A networking issue in one of our US data centers is affecting incoming mail service and webmail logins for some customers. We’re working to restore service and will update this post when more information is available.
2017-06-20 20:59 UTC: Service has been restored – we’ll continue to monitor.
2017-06-21 14:36 UTC: There have been no further disruptions, and the data center confirms that the networking issue is resolved.
2017-06-20 01:41 UTC: Web576 is currently offline due to a DDoS attack. We’re working to restore service and will update this post when more information is available.
2017-06-20 02:09 UTC: We’ve mitigated the attack upstream. The server appears to be stable, but the mitigation may affect UDP traffic. Please contact WebFaction support if you’re not able to access the server. We’ll continue to monitor.
2017-06-20 14:33 UTC: At the present time, Web576 is showing very high packet loss. We’re investigating at this time.
2017-06-20 17:48 UTC: Web576 is stable at this time. We’ll continue to monitor.
2017-06-21 14:37 UTC: The attack has resumed, and we’re working to mitigate it.
2017-06-21 18:21 UTC: We’ve possibly identified the intended target of the attack and have isolated them from other customers. The server is stable at this time and we’ll continue to monitor.
2017-06-22 18:23 UTC: The server has been stable for the past 24 hours. We’ll continue to monitor.
2017-06-25 15:23 UTC: The server has been stable for over 72 hours, and there has been no further sign of any attack.
We will be performing power maintenance on the following servers between 16:00 UTC June 25, 2017 and 04:00 UTC June 26, 2017:
wf-207-38-86-39
wf-207-38-86-40
wf-207-38-86-43
wf-207-38-86-47
wf-207-38-86-48
wf-207-38-86-49
wf-207-38-86-73
wf-207-38-86-75
wf-207-38-86-76
wf-207-38-86-78
wf-207-38-86-79
wf-207-38-86-85
wf-207-38-86-88
wf-207-38-86-90
wf-207-38-86-92
wf-207-38-86-93
wf-207-38-86-94
wf-207-38-86-98
wf-207-38-86-102
wf-207-38-86-103
wf-207-38-86-104
wf-207-38-86-105
wf-207-38-86-106
wf-207-38-86-107
wf-207-38-92-110
wf-207-38-86-178
wf-207-38-86-180
wf-207-38-86-191
wf-207-38-86-193
wf-207-38-86-194
wf-207-38-86-195
wf-207-38-86-196
wf-207-38-86-197
wf-207-38-86-198
wf-207-38-86-199
wf-207-38-93-249
wf-207-38-86-77
wf-207-38-86-135
wf-207-38-86-138
wf-207-38-86-140
wf-207-38-86-145
wf-207-38-86-147
wf-207-38-86-149
wf-207-38-86-150
wf-207-38-86-159
wf-207-38-86-160
wf-207-38-86-164
wf-207-38-86-165
wf-207-38-86-166
wf-207-38-86-167
wf-207-38-86-168
wf-207-38-86-170
wf-207-38-86-171
wf-207-38-86-175
web590
web591
web592
web593
web594
web595
web596
web597
web598
web600
web601
web602
web603
Connectivity to the servers will be interrupted for up to one hour during the maintenance window. 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-06-25 22:26 UTC: The maintenance has begun.
2017-06-25 23:48 UTC: The maintenance had to be postponed.