We’ve supported IPv6 on customer websites for many years, but it didn’t default to “on”: customers had to explicitly enable it in our account management control panel.
Starting today, IPv6 is on by default for all new accounts signed up with us (although you can turn it off if you want).
In addition, we’re beginning a gradual process of slowly enabling IPv6 for existing sites if they haven’t chosen to disable it. If you don’t want IPv6 to be enabled for your site in the future, you should use our control panel to disable it.
Read the rest of this entry »
The PHP developers recently released versions 7.1.27, 7.2.16 and 7.3.3 that fix several bugs. We’ve upgraded the PHP 7.1, 7.2 and 7.3 series on our servers as a result.
These changes should not be noticeable, but as always, don’t hesitate to contact us if you have any trouble.
Our business offices will be closed on Monday, February 18 to observe the US legal holiday. As always, we’ll provide same-day support for time-sensitive issues via our ticket and e-mail systems. However, questions that aren’t time-sensitive (including most billing matters) may not be answered until the next day, and telephone support (via callbacks) will be available only for urgent problems.
The PHP developers recently released versions 7.2.15 and 7.3.2 that fix several bugs. We’ve upgraded the PHP 7.2 and 7.3 series on our servers as a result.
These changes should not be noticeable, but as always, don’t hesitate to contact us if you have any trouble.
We’ve added a feature that allows you to do a complete “one-click” restore of your site from the control panel. The restore includes all website files, databases, and PHP settings at once, giving you a way to quickly “rollback” a site without needing to use extra tools like FTP or phpMyAdmin.
The backups page in our support section has more details.
Update 9:32 PM Pacific time: the maintenance described below has been completed, and all services are running normally.
Between 9:00 PM and 11:59 PM Pacific time on Friday, February 8, 2019, the MySQL database software on each of our servers will be upgraded from MariaDB version 10.0.37 to 10.0.38 (equivalent to MySQL 5.6.43). This will cause an approximately 60 second interruption of service on each MySQL-using customer website at some point during this period.
This upgrade is necessary for security reasons and to fix bugs in MySQL. We apologize for the inconvenience this causes.
Update 9:30 PM Pacific time: the problem described below is resolved, as Amazon is no longer sending data through the problematic route to our servers.
Original post: Our monitoring systems are showing that this evening, there have been short periods of network failures between our data center and some Amazon Web Services (AWS) data centers on the US East Coast. This appears to be due to a problem Amazon is having connecting to an intermediate “Internet backbone” connection in Virginia run by a third party.
This isn’t affecting other connections, so most of our customers are unaffected, and we see no overall drop in traffic.
Read the rest of this entry »
The PHP developers recently released versions 5.6.40, 7.1.26, 7.2.14 and 7.3.1 that fix several bugs. We’ve upgraded the PHP 5.6, 7.1, 7.2 and 7.3 series on our servers as a result.
In addition, ionCube Loader is now available for the PHP 7.3 series, so we’ve made that an option you can enable in our “My Account” control panel.
These changes should not be noticeable, but as always, don’t hesitate to contact us if you have any trouble.
Our business offices will be closed on Tuesday, January 1 to observe the US legal holiday. As always, our support staff will be providing same-day support for time-sensitive issues via our ticket and e-mail systems. However, questions that aren’t time-sensitive (including most billing matters) may not be answered until the next day, and telephone support (via callbacks) will be available only for urgent problems.
We’ve updated the SSL/TLS security settings on our servers to match current “best practices” for security, disabling the long-obsolete, insecure “SSLv3” in all cases.
Our customers shouldn’t notice any changes. We made this change on our own websites a long time ago with no reports of problems, and nearly all of the largest sites on the Internet have done the same. We’re just mentioning this so that people know to contact us in the unlikely event they do have any trouble.
That said, if you do have any trouble, it’s probably because you’re using a long-outdated, insecure web browser that you should update. You can check your browser by visiting www.howsmyssl.com. If you can’t update it, using a different browser on your computer will probably help.
