Microsoft FrontPage was once a popular Web design program. Microsoft stopped selling FrontPage in 2006, though, and we’ve been warning about the end of FrontPage support for a while now (on both our support pages and our blog).
That time has now arrived. Our FrontPage support for new sites will end on September 1, 2011, and support for existing sites will end a year after that.
World IPv6 Day is now in progress (it started at midnight UTC, which was 5:00 PM Pacific time). For the next 24 hours, many sites on the Internet, including our own www.tigertech.net, are fully IPv6-enabled.
If you have trouble connecting to www.tigertech.net, check other sites like Google, Yahoo and Bing. If you have problems with any of those, you should test your IPv6 connection and notify your ISP or network administrator about any problems.
For more information about IPv6 (and how sites hosted with us can participate), see our previous post: Now We Are Six: IPv6 support.
Today we detected that one of our customers had installed a WordPress plugin on his blog that did something malicious: when the plugin was activated, it sent a stranger an e-mail message allowing full administrator access to the blog.
How did this happen? Well, our customer simply searched the WordPress plugin directory for “Contact Form”, saw the popular “Contact Form 7” plugin listed, then clicked “Install Now”. That all sounds reasonable.
We’re pleased to announce optional IPv6 support for Web sites hosted with our company (just in time for World IPv6 day next week!).
Most customers shouldn’t use IPv6 yet, and if you don’t know what it is, you can safely ignore this post. But if you’re familiar with IPv6 and interested in adding it to your site, this post explains what you need to know.
We’re pleased to announce our WordPress “one-click” installer. Using this new feature in our “My Account” control panel, you can easily install WordPress on your Web site.
Our business offices will be closed on Monday, May 30 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.
Some Comcast users in California had trouble connecting to some of our servers beginning at around 7 AM Pacific May 21, 2011. Non-Comcast users were not affected at all, and even people who were affected were able to reach some of our servers with no trouble.
This was caused by a technical problem at Comcast, and not related to us specifically. It appears Comcast was incorrectly filtering some combinations of IP addresses and ports in one of their California network routers, preventing their customers from reaching some sites.
The issue was apparently resolved by Comcast at 10:07 AM Pacific time, and we are not aware of any ongoing problems. As always, don’t hesitate to contact us if you have any trouble.
All Web sites on the “farnsworth” Web server have been moved to a new server named “zapp”.
This change was made for reliability; our monitoring systems detected potential hardware problems with the “farnsworth” server earlier today, and the sites were moved so it can be replaced before it causes any problems.
This doesn’t cause any downtime, and customers shouldn’t notice any change — but as always, don’t hesitate to contact us if you have any questions.
At approximately 11:00 PM Pacific time tonight, May 14, the “pazuzu” Web server will be restarted.
As a result, for customers on the “pazuzu” server (only), Web site service and the ability to read incoming e-mail will be unavailable for approximately five minutes. Customers on other servers will not be affected.
A router failure at an upstream Internet “peer” that we connect to caused high packet loss for some Internet connections between 5:18 PM and 5:28 PM Pacific time.
The packet loss grew worse through that period until it exceeded 25%, which is enough to cause pages to fail to load within a browser’s timeout period if your connection was one of the affected ones. (Connections that go through different routers were not affected.)
Network engineers have routed all connections around the failed hardware until it’s replaced, so the problem is resolved. If your part of the Internet was one of the affected ones, please accept our apologies for the problem.
