We're working on resolving it.
This could take awhile. We're waiting on a customer to change DNS for his domain, so the attack will cease.
Plone 3.0.6 is out. This is a bug-fix release. If you are affected by one of the bugs that it fixes, it would be a good idea to upgrade, otherwise there appears to be no rush. If you wish to upgrade, please file a support ticket.
If you're running a WordPress site, please file a support ticket right away so we can update it to version 2.3.3 for you. WordPress version 2.3.3 fixes a serioues xml-rpc vulnerability.
We had an outage overnight due to an edge switch port failure. This is now resolved. I apologize for the inconvenience.
If you're still using Plone 2.5.4 or 3.0.2 then you needed Plone Hotfix 20071106 back in November. But now there is a hotfix out for this hotfix, Plone Hotfix 20071106-2, to fix a vulnerability in the original hotfix. If you're not confused, and you're running Plone 2.5.4 or earlier, or Plone 3.0.2 or earlier, then please file a support ticket so we can install the new hotfix-hotfix for you. ;)
One of our mail servers, a brand new machine, powered off for some reason. We swapped the disk out into an identical on-site spare and service is restored. I apologize for the delay in restoring service. Thanks for your patience.
If you run a Mailboxer mailing list please update the mtahosts variable to the new IP address: 72.249.122.111. It's critical you update this right away so your list continues to work. I apologize for the delay in this notification.
The wild idea has been floated of turning High Speed Rails into a customer-owned cooperative. Each customer who chooses to become an owner of the coop would be on equal standing with all other owners, including the current ownership, and the cooperative would be run democratically. Members would likely be able to vote an owner discount and/or rebate. I think it's worth considering. If enough people participate, the cost may not be very high. If you're interested, let me know what you think.
In order to gauge the interest level, please participate in this very short and simple poll:
If you have a WordPress site that is using a version earlier than 2.3.2, you need to upgrade right away to fix known vulnerabilities. Please file a support ticket so we can take care of this for you.
If you're not yet using Plone 2.5.5 or 3.0.4, it's recommended that you upgrade right away to fix security issues. Contact support for assistance.
"This hotfix corrects a vulnerability in the statusmessages and linkintegrity modules, where unsafe network data was interpreted as python pickles. This allows an attacker to run arbitrary python code within the Zope/Plone process." More information on Plone Hotfix 20071106.
The hotfix is only for Plone 2.5 and 3.0 but of course if you are running anything earlier than 2.5 you need to upgrade anyway.
To install this hotfix, login via ssh, become root and cd ~zope/instanceX/Products, X usually being 1. If you are not using our standard instance setup then you will already know where your instance is.
wget http://plone.org/products/plone-hotfix/releases/20071106/PloneHotfix20071106.tar.gz
tar xzf PloneHotfix20071106.tar.gz
chown -R zope:zope PloneHotfix20071106
rm PloneHotfix20071106.tar.gz
It's installed so now you need to restart Zope. You can do so either via the Control Panel in Zope (shutdown button) or with the below command:
zopectl restart
Be sure to login to Zope and go to Control Panel > Products where you can verify that PloneHotfix20071106 was successfully installed. If you need assistance, feel free to contact support.
If you're using any Wordpress version previous to 2.3.1, please upgrade right away to fix serious security issues. See here for more information. Please feel free to file a support ticket and we can take care of the upgrade for you.
Server phoenix is currently offline. We're working on the problem and expect to have more information soon.
Update: The server is back up after a lengthy filesystem check. Thanks for your patience. I apologize for the inconvenience.
Plone 2.5.3 is out and it fixes several bugs and a security issue. To upgrade, please file a support ticket and we'll take care of it for you.
Our New York network is offline at the moment. The datacenter staff is currently working on resolving the problem.Thanks for your patience.
Update: Service has resumed. Downtime was 30 minutes. Thanks again for your patience.
We'll be swapping the RAM in server atlanta around 7PM EST this evening to fix some random lock-ups we have seen. Thanks for your patience.
The entire High Speed Rails network in Seattle was offline for approximately 3 hours this morning due to human error by our upstream transit provider during planned maintenance. I apologize for this inconvenience, it should not have happened. We're following up diligently with the provider to ensure that more care is taken in the future. We'll also be deploying additional monitoring systems so that a problem like this is caught earlier. Emails that could not be delivered to our mail servers in seattle were queued up at our backup MX in San Diego and are now being delivered. Thanks for your patience.
Update: All but 500 of the roughly 5000 emails that were queued up during the outage have been delivered. The rest will be delivered shortly. Thanks for your patience.
Server nassau has gone down 3 times since late last night. The reboots are taking awhile since we're running a filesystem check each time to ensure the data is not damaged. We're working on diagnosing the cause of the problem. Thanks for your patience.
Update 26 April: We've put back the old RAM. Hopefully this will resolve the problem. Rest assured that I am monitoring nassau very closely and that staff is alerted almost immediately if nassau stops responding. Thanks for your patience.
Update 4 May: We're taking nassau down briefly to put in some known good RAM of the same kind (Kingston) that was causing the original problem of this post. Thanks for your patience.
Update 5 May: Nassau is coming back up after the RAM swap. Thanks for your patience.
Update 10 May: We're still having problems with Nassau so we are going to swap everything but its RAID card, disks and RAM (which is new) with an identical server that hasn't been used in production (brand-new).
Update 10 May 13:48: Nassau is coming up and we're running a filesystem check, which should take about 20 minutes or less.
Update 10 May 14:05: All the accounts are starting up now. Service is being restored. Thanks for your patience.
Update 10 May 13:15: Yes, we know its down again. We're going to replace the RAID card.
Update 10 May 15:15: The RAID card didn't help. We're going to try a few more things but in the meantime I have lowered TTLs on all domains we host on nassau. If you use outside DNS you will want to lower your TTLs to 600 right away as well. If nothing works out we will migrate nassau accounts to a brand-new machine in Dallas ASAP.
Update 10 May 19:15: We're bringing up the jails one by one but I am not optimistic. The backup plan is well under way.
Update 10 May 21:30: Several accounts are up on the new machine (hanoi) and the nassau hostnames resolve to the IPs of this new machine now, though DNS may not fully propagate for another 20 hours. If you need your new IP, your login and hostname stay the same, except replace nassau with hanoi. You can run dnsip `hostname` on the commandline (via ssh) to get the IP. We're working on redirecting all traffic, or at least port 80 traffic, from nassau to hanoi to compensate for the DNS propagation lag. We'll be emailing each affected customer individually.
Update 10 May 23:50: Accounts 1-8 and 10 are up and their port 80 traffic is being forwarded on to the new server. Accounts 9, 11-12 are in progress. No emails have been sent out yet.
Update 11 May 08:20: Just 3 accounts remain.
Update 11 May: All accounts have been migrated and all affected customers have been emailed.
Update: The redirects for all the nassau IPs will stay up for a few more days but I urge affected customers who don't use our DNS to update right away.
We had to replace the RAM on servers bogota and nassau this evening. I apologize for the inconvenience.
Update: The maintenance is complete. All three servers (plus kingston, which is not yet in use) have brand new Kingston RAM. I ran filesystem checks as well. The final accounts are starting up now. Thanks for your patience.
If you're using Zope 2.8, 2.9 or 2.10, Zope Corp released recommended bug-fix updates 2.8.9, 2.9.7 and 2.10.3. These, plus Zope 2.7.9, are the only Zope 2 versions we currently recommended for us. Please contact support to upgrade.
We'll be performing maintenance on one of the mail servers Monday, March 26 starting at 6PM EST. The window may last up to an hour during which time email services will be suspended. Incoming email will be received and queued on the our backup MX so no mail will be lost. Thanks for your patience.
Update 7:20PM EST. We started a bit late and ran into one serious problem that is delaying the delivery of incoming email. We're working on it.
Update 7:30PM EST. Email is flowing but Spam Assassin filtering is temporarily suspended.
Update 7:50PM EST. We found the problem. Normal service has been completely restored. Thanks for your patience.
We're replacing a bad disk in server santiago's RAID array. Thanks for your patience.
Update: Service is restored and the array is rebuilding. It will take a few more minutes for all accounts on santiago to start up.
One of our mailservers, boise, is experiencing problems again after 18 days of normal performance. We're finishing up filesystem checks at the moment and expect to restore service soon. Thanks for your patience. We have a warm backup server ready to replace boise with very soon.
Update: 9:10AM PST. Service is restored. I don't expect any further outages but its possible. We're working on finalizing the replacement of boise with the new server ASAP.
We're working on upgrading all of our servers to the latest stable version of FreeBSD (6.2), which offers significant gains in performance, stability and security. We'll be emailing affected customers as we schedule the upgrades. Downtime for managed server customers should be less than 5 minutes. For VPS customers we may need up to 30 minutes to complete the upgrades.
On Friday, March 30th we will upgrade accounts hosted on server seattle to a new server running the latest stable version of FreeBSD (6.2). Due to the difference in operating system versions (seattle is 4.11), we unfortunately can not just copy your entire account over to the new server. This upgrade will put your account on a faster, more powerful and newer server. We have emailed all affected customers.
Update: May 5. This was delayed but we will be working on this in May. The migration will be to a new server at our new Dallas location.Thanks for your patience.
A vulnerability has been discovered in Zope, where by certain types of misuse of HTTP GET, an attacker could gain elevated privileges. All Zope versions up to and including 2.10.2 are affected. This hotfix is recommended for immediate install. Please email support to have us install it for you. More information: Hotfix for cross-site scripting vulnerability.
We'll be performing maintenance on one of the mail servers Thursday, March 22 starting at 6PM EST. The window may last up to an hour during which time email services will be suspended. Incoming email will be received and queued on the our backup MX so no mail will be lost. Thanks for your patience.
Update: This had to be postponed.
We're replacing a bad disk in server santiago's RAID array. Thanks for your patience.
Update 19 Mar 1PM: The server is back and the array is rebuilding. Thanks for your patience.
We'll be performing maintenance on server caracas, today Friday March 16th at 1PM EST. The maintenance window should be one hour or most likely less. We'll be swapping RAM, manually checking filesystems and performing general maintenance in attempt to resolve the random lockups that have occurred lately. Thanks for your patience.
Update: We found some more hardware problems and are working on diagnosing and fixing them.
Update: We replaced everything but the RAID array. Service has been restored. Thanks for your patience.
Update: We're still experiencing some issues. We'll have to take the server down to see if we can find the problem.
Update 19 Mar 12PM: We replaced the RAID card with the latest model. Thanks for your patience.
We'll be performing maintenance on server luxor, tomorrow Friday March 16th at 3PM PST. The maintenance window should be one hour or most likely less. We'll be swapping RAM and performing general maintenance in attempt to resolve the random lockups that have occurred lately. Thanks for your patience.
Update: The maintenance is complete. We only had to change the RAM. Thanks for your patience.
As you may know, Daylight Savings Time is starting 3 weeks earlier this year in several countries. We have already updated our servers and networking equipment, however we have not updated customer VPS accounts since many do not use the local timezone (EST for New York accounts, PST for Seattle accounts). If you wish to update to the new DST, you can login via ssh, become root, run this command: pkg_add -r zoneinfo and run the command tzsetup. In tzsetup you'll need to select your desired timezone. Or you can file a support ticket and we will take care of this for you. Also, if you run your own MySQL server and want to update its timezones, please file a ticket.
We're having trouble with server boise again and are working on it.
Update:The filesystem check is taking an extraordinarily long time, but just finished /usr, where all the important data is. Only /var remains, which is quite small. We had to shut down all services on boise in order to ensure that the filesystem check would finish, and quickly. Thanks for your patience. I apologize for the inconvenience.
Update: Service has been restored but we're still working on this. Thanks for your patience.
The datacenter surprised us with some facilities maintenance tonight, from midnight to 3AM. Servers may be offline any time between those hours and hopefully not for the full three hours. Thanks for your patience.
We're working on it. Thanks for your patience.
Update: Caracas is online again.
One of the mailservers, boise is down. This is interrupting mail service. We are working on it.
Update: Service is restored. We may need to perform some additional work for a more permanent solution. Thanks for your patience.
Update: A few problems came up this morning but they appear to be resolved now. Some emails may have gotten through without being spam-checked, or may have gotten rejected by SPF rules because we accidentally set the wrong ip as the primary on boise.
Complete RAID array failures like the one we had last week don't happen often. In reality, given all the precautions we take and the quality hardware we use, they shouldn't happen at all.
But it is essential to be prepared and so we are implementing some improvements that will, we hope, both cause these incidents to happen less often in the future and enable us to restore service more quickly when disaster strikes:
The more agile backups system will require some changes that you should be aware of:
You can read more about the specifics of the new backups system in the Backups FAQ.
We have to take server phoenix offline briefly to replace a bad disk in the RAID array. This will happen shortly. I apologize for the inconvenience.
Update: After rebooting the machine with the new disk, it failed and now shows that another disk has gone bad. If this is correct it means that all data on this machine has been lost. We're going to try swapping out the RAID card but if all else fails we have backups and an idle identical machine on hand. I'll be posting updates as they become available.
Update: We were unable to rescue the RAID array. We're working on swapping in a the spare server and using the same IPs so customers don't have to change DNS. After that I'll be restoring from backups and emailing each customer as their account comes up.
Update: The spare server is up, is in good shape and we're restoring to it from backups.The first 2 accounts are up and the account owners have been emailed. We'll continue working on this until all the accounts have restored. Thanks for your patience.
Update: Accounts 01-20 are up or will be shortly. The other 8 accounts should be within hours or less.
Update: All accounts are up, MySQL is up. Postgres will be up shortly.
Update: Server phoenix went unresponsive Feb 15 around 5PM EST. We're working on it.
Update: Phoenix is working again. We're looking into the cause.
We had to take server dallas offline briefly to replace a bad disk in the RAID array. It should be back up shortly. I apologize for the inconvenience.
Update: Dallas is online again and the array is rebuilding. Thanks for your patience.
SPF is an anti-forgery technology that everyone needs to use. SPF is a useful tool in the fight against spam. If you want to take advantage of SPF, and your domain(s) use the highspeedrails.com nameservers, please file a support ticket and include the following:
If your answer to number 2 is not "only the HSR network", then you need to include a list of all the servers (hostnames or ip addresses) from which you send email using the domain(s) from number 1 above in order for us to establish the SPF record.
More information: SPF Overview from Linux Journal
Please note that this will result in downtime for email services for all customers.
If we host DNS for your domains (i.e., if you're using our nameservers) you have nothing to worry about and we will take care of ensuring a smooth changeover.
If your account is hosted in Seattle and you are not using our nameservers for your domains, please lower TTLs to 600 seconds on all A records pointing to your HSR account. Please do this today and absolutely no later than tomorrow morning before noon PST. The current IP addresses will stop working as soon as each server is moved.
If you're not using our nameservers but are using our MX's (mail services), please ensure that you are using a.mx.highspeedrails.com (pri: 0) and b.mx.highspeedrails.com (pri: 10) as your MX records in order to ensure a smooth changeover.
Affected VPS servers include:
Affected customers with managed servers have been emailed individually.
This only affects servers in Seattle. This does not affect servers on the east coast.
Once the servers have been moved and are online again you can get your account's new IP address, if you need it, by logging in via ssh (to the account hostname, which will not change [see your welcome email]) and running this command (copy and paste):
dnsip `hostname`
Up to 2 hours of downtime per server is expected as a result of the physical move of the servers from one datacenter to another. We will attempt to minimize downtime for the primary mailserver.
I'll be posting updates to this thread so please subscribe to our RSS feed using your feedreader (Bloglines, Google Reader, etc.). If you're using Firefox 2, this is as easy as clicking on the RSS button in the address bar of your browser.
I realize how inconvenient this will be. Thanks for your patience.
NB: For those affected by this migration, please take note of any cases in which you hard-coded your account's IP address somewhere, for example in a config file, client application, ftp client, svn, client, etc. We hard-code IPs in a few places, which we will take care of updating. If you have hard-coded your IP addresses anywhere, be sure to update it after the migration.
Mailboxer users who have defined their forwards on the mailserver: We will update the 'script' for you but you will need to update the mtahosts variable of all your mailboxer instances to: 216.10.79.225.
I found 64 mailboxers on the mailserver, only 5 of which need updating. These have been updated to use the account hostname instead of the IP address.
I believe we have found all the hard-coded ips but if you notice one that needs updating, please let us know.
The Seattle server move is complete.
The unexpected additional downtime was due to human error on the part of the contractor we hired to configure our Cisco switches, and the resulting time needed to fix it.
I apologize for the inconvenience.
Please check any affected services you use and let us know via email to support@highspeedrails.com if you encounter any problems.
Thanks again for your patience.
Although HSR takes nightly backups of your data, please be sure to take your own regular backups (at least weekly) of your important data to an offsite location. Disaster can strike at anytime and its best to be prepared. We can help you set up rsync or other types of backup regimes to offsite systems. Get started today!
If you're using Trac, please file a support ticket to have us upgrade it for you right away as all versions below 0.96 have a reStructuredText breach of privacy and denial of service vulnerability.
The datacenter staff accidentally cut the power from server quito and its not coming back on its own. We're working on the problem and apologize for the inconvenience.
Update: Quito is up. Downtime was 5 hours. I apologize for the inconvenience.
Plone releases that include PlonePAS (Plone 2.5.*) include a vulnerability that allows a user to masquerade as a group. HSR recommends this Hotfix for all Plone 2.5.x installs that allow anonymous user registration. Please file a ticket to have us install it for you. More information: PlonePAS user/group fix (CVE-2006-4249).
We received emails from a couple customers stating their spam counts seem to be increasing, so we have deployed some additional spam fighting measures, including: (1) more RBL lists, for example to block emails from dynamic IP addresses, which are a leading source of spam. (2) new rulesets, which raise the Spam Assassin score for emails that contain common characteristics of spam emails. (3) lowered deletion thresholds, which result in more obvious spam being deleted and not passed through to your email client.
Of course we continue to leverage a lot of other measures, including rejecting virus-laden emails before they even enter the mail servers, the Spamhaus SBL and XBL RBLs, Bayesian spam filtering, the DCC, Razor and Pyzor checks, the SURBL and a lot more.
We encourage customers to use filters/rules in your email clients to filter SA-marked spam emails into a spam folder and to use a Bayesian filter locally, such as the ones built into the Thunderbird or Mail.app email clients. You may also want us to setup SPF records for your domains. Try not to use catchall email accounts if you can avoid it. Catchalls inevitably increase the amount of spam you get.
Plone 2.5.1 is out. Plone 2.5.1 fixes several important security issues and is recommended for immediate use by those customers currently using Plone 2.5.0. Zope 2.9.5 is recommended for use with this Plone release. Please file a ticket to have HSR staff perform this upgrade for you. More information: Plone 2.5.1.
Zope 2.9.5, a bug-fix release, is out. This upgrade is not urgent or recommended unless you wish to also upgrade to Plone 2.5.1. More information: Zope 2.9.5 released.
Plone 2.1.4, a bug-fix release, is out. We recommend that anyone using Plone 1, 2.0 or 2.1 immediately upgrade to Plone 2.1.4 for security reasons. Feel free to file a ticket to have us assist you with this. More information: Plone 2.1.4.
Plone 2.5 and 2.5.1RC are both vulnerable to a security problem with versions 0.4 and earlier of PasswordResetTool. If you have separately installed a vulnerable version of PasswordResetTool this also affects you. Please update to the latest version immediately. If you need help, please file a ticket. More information: Plone Security Advisory: Password Reset Tool.
Nora is catching up on billing for us, so you will see paid invoices/receipts going out starting today. If you have setup a recurring bill (99% of customers have) then you don't need to worry about these invoices/receipts, please just save them for your records. You'll also be able to get the invoices/receipts by logging into My High Speed Rails.
We're pleased to announce the opening of our second hosting location, in New York City, to better serve our East Coast and European customers. The datacenter at 325 Hudson is a modern facility that has everything you would expect. We're hosting both Managed Servers and VPS accounts there. Bandwidth is from Level3, UUNet, NAC and nLayer along with excellent local peering (NYIIX, NYCx & more). A big thanks to our customers, without whom we would not have been able to open this second location. Thank you!
HSR is offering free migrations for current Zettai customers indefinitely. Please note that there is a wait time of up to one week due to high demand.
Update: This offer expires December 15th. Please note that the wait time is now 2 weeks due to high demand.
Update: Due to high demand and the large queue of migrations we have pending, its unlikely that we will re-open orders before December 15. Free migrations thus are almost certainly over. Its unlikely that we will offer for-pay migrations either. I encourage all Zettai customers to seek alternate hosting immediately.
If you're using Mailman, you should be aware of several moderately critical vulnerabilities that have been discovered: mailman - Multiple Vulnerabilities. Please note that the only newer version of Mailman available is a release candidate so I don't recommend upgrading yet. Once Mailman 2.1.9 is out, please feel free to file a ticket and we'll upgrade any existing Mailman instances for you.
Update: Mailman 2.1.9 is now out. If you're using a previous version, please file a ticket to have us upgrade your Mailman install.
Server caracas is currently offline due to a network event at the datacenter, upstream from us. We're working on it and hope to restore service ASAP.
Update: Downtime was 15 minutes, the server is up again.
If you're using Zope 2.7 or 2.8, there is a new hotfix out for more reST security issues. Please email support to have us install this for you. Zope 2.9 is not affected. More information: Hotfix for Further reST Integration Issue.
If you're using Ruby on Rails we urgently recommend you upgrade to version 1.1.6. 'gem update rails' as root or just 'gem update' should do the job or feel free to file a support ticket and we will be glad to help. More information: rubygem-rails - evaluation of ruby code
Just 4 months have passed since High Speed Rails started accepting orders and already we have more than 100 accounts in use. A big thanks to all our customers. :) As a result of this growth we have just 5 VPS accounts left at this time and may run out before the next batch of server parts arrives from Taiwan later this week. Rest assured that we're working hard to get those parts and continue taking orders.
Aug-8: We have just one account left at this time and expect the next batch of servers in no later than August 15th. Thanks for your patience.
Aug-8: Correction, that account has been taken. We'll continue taking orders but please note that the delay is expected to be approximately one week. Thanks for your patience.
Aug-15: The new servers are arriving today and it may take another day or two to lock down the first of them and get started on migrating accounts.
Aug-17: The next batch of servers is ready and we're chipping away at the backlog. Thanks for your patience.
Zope Corp has released Hotfix-2006-07-05 to fix a serious security issue with restructured text. If you allow untrusted users to edit restructured text content through-the-web, then its recommended that you install this Hotfix right away. Please file a support ticket to have us take care of this for you.
Plone 2.5 has been out for awhile now. We've upgraded several customers and no serious problems have been encountered so please feel free to contact support if you'd like us to setup Plone 2.5 for you.
If you're using CacheFu we recommend upgrading to CacheFu 1.0.1 at your earliest convenience as it fixes some issues that can cause instability, deadlocks and high CPU usage. Please contact support to have us perform the upgrade for you.
Server nassau went offline a few minutes ago. We're currently looking into the situation and are attempting to resolve this as quickly as possible. Thank you for your patience.
Update: Server nassau is up now. Downtime was about 28 minutes. I apologize for the inconvenience.
Jun-15: The problem recurred this morning and we're working on figuring out the problem. I apologize for the inconvenience.
Jun-15: The server is up again and all looks normal again, but we're still working on finding the problem. Meanwhile I have ordered a duplicate server in case it turns out to be a hardware problem that is not quickly fixed.
Jun-15: The server failed again. We're looking into it. If we don't find the problem soon I will find an alternate, if temporary, solution for the 10 accounts currently hosted on server nassau. I apologize for this inconvenience.
Jun-15: The RAID array is fine, the RAM has been fully tested without error and the CPUs look good, so we're working on some ideas for what else might be causing this. The server is up again.
Jun-16: Server nassau stayed up and working normally all night so the problem appears to be resolved. What probably fixed it was reseating memory and CPU.
Jun-17: Server nassau has been up for nearly 2 days straight so things look good.
There will be a brief interruption to MySQL service today as we upgrade the MySQL servers for reasons for security. Thanks for your patience.
16:40PM: Servers Seattle and Bogota have been upgraded. For those clients that don't run their own MySQL server we also upgraded your MySQL client version. Its a minor upgrade so the impact should be minimal. For those clients running their own MySQL servers we will be contacting you separately soon.
In the interests of security we'll be rolling out firewall updates this week for all servers. These rules will close a lot of ports (incoming) in order to protect potentially vulnerable apps from the open internet. Ideally, only httpd, sshd, tinydns (if you run your own nameserver) and qmail (if you need to receive email directly to your account) will remain directly exposed to the internet. We can of course open or close other ports as needed, all you need to do is file a support ticket.
02-Jun-06: The update has been rolled out to server bogota. If you need a port opened, please file a support ticket.
13-Jun-06: The update has been rolled out to server seattle. The firewall we're using on seattle is not as advanced as on the other servers (because the OS version is older) so you will experience the occasional ssh timeout. We're working on a way around this. I apologize for the inconvenience. If you need a port opened, please file a support ticket.
15-Jun-06: We've disabled the update on server seattle until this issue is worked out. Thanks for your patience.
Do you need your email filtered into different directories on the mail server based on your specific needs? Then you're in luck because now you can get your filters put into place just by filing a support ticket. Don't worry about syntax, just send us your pseudo-code (if, then, etc) and we will translate it into the filter rules you need using maildrop, a server-side mail filtering and delivery agent (similar to procmail) from the Courier MTA project.
Django for Non-Programmers: An excellent post on how easy it is to get started with Django, even for people who are not programmers - and don't want to be!
The Plone project has released Plone Hotfix 2006-04-10 which fixes some security issues in all versions of Plone 2.x.x. We recommend installing this right away if you use Plone 2. You can file a support ticket to support@highspeedrails.com to have High Speed Rails install this patch for you.
High Speed Rails is a new hosting service founded by the architect of Zettai.net, a python hosting service with more than 1,000 satisfied customers. At High Speed Rails you’ll find performance-oriented, managed open-source hosting.
High Speed Rails is a managed service, a service where Service to our customers is our priority. Support is unlimited: we will install, configure, trouble-shoot, upgrade, downgrade most any software that you need to accomplish your goals. Get the support you need via phone, IM, online chat, forums or email. High Speed Rails saves you time so you can focus on your goals.
The High Speed Rails service gives you the absolute best performance for your web application. You and your customers get speedy and reliable access because we use robust, undercrowded servers on fast networks. You can make an impression by serving your static content through our snappy accelerator service, which is included with all of our plans.
At High Speed Rails we leverage the vast amount of free and open-source software available today to meet the needs of our customers and provide the featureful hosting service you want. From Apache to Zope, from Plone to Ruby on Rails, Django, PHP, MySQL, PostgreSQL and much, much more, you have the diverse spectrum of open-source software at your fingertips with High Speed Rails.
Thanks for visiting!