Menu

All items for November 2007

Installing an SSL certificate for WHM/cPanel https redirection

Previous to version 11.x.x of cPanel‘s WHM interface there was an option in the SSL/TLS section to either generate a self-signed SSL certificate for the server or to install a real SSL certificate.  However, in 11.x.x (not sure exactly when this changed) this option no longer exists.  Even if you install your SSL certificate through the normal process for installing SSL certificates for domains it won’t work as expected. 

If you have changed the Tweak Settings option “When visiting /cpanel or /whm or /webmail with SSL, you can choose to redirect to:” to Hostname or SSL Certificate and you navigate to a hosted domain at https://www.domain.com/cpanel it will redirect to https://servername.com:2083/, however, it will not be using the SSL certificate that you just installed.  “But why?”, you may ask.  The reason is because you installed the SSL certificate for Apache, but you did not install it for the WHM/cPanel interface.  The installation for the cPanel/WHM SSL certificate has been moved to a different section of WHM. This is because cpsrvd handles SSL requests for WHM/cPanel whereas Apache handles SSL requests for normal domain traffic.

Under the Service Configuration section of the standard WHM theme there is an option for “Manage Service SSL Certificates”.  Navigate to this page and you will see it lists certificates (self-signed) for Exim, Courier, FTP, and surprise… WHM/cPanel!  This is where you need to install your newly purchased SSL certificate. If you click on “Install New Certificate” you will be taken to the standard WHM SSL certificate installation form.  If you have already installed the certificate through the standard domain method then all you have to do is click on “Browse” next to Domain this CRT is for and select the servername from the list.  This will install your previously installed SSL certificate in the correct location. 

If you did not already install the SSL certificate you will have to do so by pasting the necessary information into the form and submitting it. If you haven’t already changed the Tweak Settings option to redirect make sure you don’t forget it. At this point you should be good to go!

Team Fortress 2 on Vista crashes on map change, “Can’t load lump x, allocation of x bytes failed! Engine Error”

I’ll get straight to the point.  I’ve been playing Team Fortress 2 with no significant issues since the beta was published via Steam…until recently.  For some reason I was randomly getting crashes when the map changed on a server.  The specific error is as given in the title of this post.  I could not for the life of me figure out what might have changed that would have caused an issue like this (completely forgetting I had recently reinstalled Vista).  Instead of actively searching out a solution I continued restarting the game each time it crashed.  This seems to be a problem of mine, putting a band-aid on the problem rather than researching the cause to find a true solution.  Well it turns out it was actually a problem caused by Windows Vista itself in the way it handles memory allocation. 

This issue actually affects more than just Team Fortress 2, but my exposure to the problem was limited to this game.  The solution is a patch provided by Microsoft which I had installed on my previous instance of Vista, and was the reason I had not experience crashing prior to my reinstall.  Hopefully if you’re reading this you’ve taken the initiative to research your problem rather than trying to do what I did.  I have been running successfully with no crashes since installing the patch.  With that said, install the patch and get back to the game!

Microsoft KB Article 940105 – Virtual address space usage in Windows game development