VPS.NET Cloud Community: Nick - Viewing Profile - VPS.NET Cloud Community

My account is totally messed up, I got tons of invoices now, and keep getting an error when applying a node .

Looks like the stability has returned to AMS, everything is still running very smooth. Google is reporting my page load times at 1s now, 90% faster then other sites. It was a lot higher the past couple of weeks.

Anyone seeing similar results in AMS or other improved clouds?

Being a customer for about 1 year and 9 months, I have had both really good and bad times. A while back I have had around 100 days uptime on my machine in LON-C, which is really good I think . But after that I had to reboot it for updates, and never even came close to great uptime.

The last few months have been really horrible after i made the move to AMS a while back. At first the speed was really good. The I/O was awesome, and load times dramatically improved.

But then problems started . Sometimes HV's just crashed, and my vps was either restarted, or it was stuck because it wouldn't start, and it needed an FSCK. Then really nasty problems occurred, my vps went into read-only mode lots of times. As my websites aren't that critical I just monitor for ping, checking if the machine is alive. But the problem with that is, that in read-only mode the vps still responds to ping's so it sees the machine as being up. It still ran, but just could read from the SAN, because it lost the connection somehow, or the SAN had a problem. So basically in read-only it turned into a zombie, still running, but serving no websites at al.

This happened to me multiple times (10-20 in about 3 months), causing me hours of downtime up to half a day, until I noticed it . Most of the times when I was asleep. On top of that sometimes one of the two redundant SAN's acted up. Then the whole process of synchronizing these SAN's for data redundancy had to start, causing painful poor performance, and almost a locked up vps, again hardly serving any websites.

I was just about to move until I got the news on the storage platform being replaced, and the network being upgraded. Still seeing the good in vps.net, as I don't always blame them for the soft- and hardware failures, I gave them another go. I guess it's a learning experience for everyone, things go never as you planned or hoped.

But maybe It's a little early to say, as updates on AMS just completed. But it looks like the stability has returned once again for me. The load has gone down a lot, close to 0, as I don't run intensive processes, and the I/O is a lot better. I'm seeing the %iowait once again very low at about 0.39%, which is very good I guess. For now we'll see what happens, and hopefully this stays. Hopefully I can report back in a while, still seeing improved result, and being a happy customer.

Any of you guys have had similar experiences in the past, and seeing improved results now ?

P.S. Hopefully I didn't jinx myself now

Oh wait I made a small mistake, my ca-bundle file are not the 3 other crt's, but it's in the following order.

The domain_com.crt from Comodo (same as SSLCertificateKeyFile, your signed certificate), the PositiveSSLCA.crt and UTNAddTrustServerCA.crt. The other one (AddTrustExternalCARoot.crt) wasn't needed for the correct chain.

It didn't work for me either in ISPManager.

I just did it through ssh. If you have already created the csr and key through ISPManager, it should have created the virtualhost in the apache config file.

You have received a couple files from Comodo in an archive. All you need to do is upload it, bundle some of the crt's and modify the apache config file.

Some of the lines are probably already added in the apache config, so just change it to the correct files (the signed domain certificate by Comodo, and your generated private key).

SSLEngine on
SetEnvIf User-Agent ".*MSIE.*" nokeepalive ssl-unclean-shutdown downgrade-1.0 force-response-1.0
SSLCertificateFile /var/www/httpd-cert/domain.com.crt
SSLCertificateKeyFile /var/www/httpd-cert/domain.com.key
SSLCACertificateFile /var/www/httpd-cert/ca-bundle.crt

The last line I have added myself. It is the chain certificate which is important for your certificate to be valid. You can create it by pasting the 3 other Comodo crt's in 1 file.

It's quite simple, and could be done in a couple of minutes.