Password Protecting GoDaddy Webalizer Stats in /usage
At work I recently moved our hosting to a GoDaddy Linux Virtual Server utilizing Simple Control Panel/TurboPanel. Everything worked fantastic with the exception of .htaccess/password protection for the Webalizer statistics located at /usage for each respective site. GoDaddy support was clueless and couldn’t help.
I would place an .htaccess file in each site’s respective directory in /var/www/stats/sitename.com and it would still be accessible to the public. The reason for this was that TurboPanel/Simple Control Panel was not placing the “AllowOverride All” option for the “usage” path in the /etc/httpd/conf.d/turbopanel.conf file. If you edit this file manually, TurboPanel will overwrite it next time you make a change to your configuration so that’s not a good solution.
After some Googling, I found an answer here which was slightly flawed, but saved me a ton of time figuring it out myself. Utilizing the fix below you can permanently fix the TurboPanel configuration template to automatically add the “AllowOverride All” option when it generates the /etc/httpd/conf.d/turbopanel.conf file. This will enable the .htaccess file to work for /usage.
Using Nano/VI/Pico or any text editor (nano is used in my example):
nano /usr/share/turbopanel/webapp/WEB-INF/classes/ (continued on next line)
com/godaddy/turbopanel/framework/systems/apache/apache-config.xsl
Find the following lines under "<!-- Webalizer -->":
<xsl:text>Allow from all</xsl:text>
<xsl:value-of select="$newline"/>
<xsl:value-of select="$tab"/>
<xsl:value-of select="$lbracket"/>
<xsl:text>/Directory</xsl:text>
<xsl:value-of select="$rbracket"/>
<xsl:value-of select="$newline"/>
<xsl:value-of select="$newline"/>
</xsl:when>
Change the above to:
<xsl:text>Allow from all</xsl:text>
<xsl:value-of select="$newline"/>
<xsl:value-of select="$tab"/>
<xsl:value-of select="$tab"/>
<xsl:text>AllowOverride All</xsl:text>
<xsl:value-of select="$newline"/>
<xsl:value-of select="$tab"/>
<xsl:value-of select="$lbracket"/>
<xsl:text>/Directory</xsl:text>
<xsl:value-of select="$rbracket"/>
<xsl:value-of select="$newline"/>
<xsl:value-of select="$newline"/>
</xsl:when>
After editing, restart TurboPanel and Apache:
/etc/init.d/turbopanel restart
/sbin/service httpd restart
For good measure, after you’ve completed the above, go into “Simple Control Panel” and edit one of your sites. Make sure Webalizer/statistics are enabled and click save.
Now when you place an .htaccess file in one of your statistic folders it will actually work! Hooray!
Leave a comment if this helped you or if you have anything to add.
Fuck you Symantec! I used to love you, but now I hate you!
A Shitty Poem for a Shitty Company:
Damn you to hell Symantec.
I used to love you, but now I’m jilted.
Your SAV had me going for years,
Reliable, a workhorse you were.
Now you are a beheamoth,
and your products suck ass.
Endpoint Security is a joke,
and so is your virus protection.
If I continue to be yours,
I will have a full head of gray.
About a year ago I migrated our firm to Symantec Endpoint Security (the first release, RTM) from SAV 10. It has been nothing but a complete fiasco. I’m pretty good at this stuff and had deployed many, many SAV systems previously. When I initially installed SEP (initial release) I had high hopes. These hopes were immediately dashed with countless problems that took weeks to get fully straightened out. Although I “know” the product much better now and have less problems with it, I still hate it with a passion for the following reasons:
-
beta-level software billed as “production” - buggy as hell
-
bloated administration interface (good concept, terrible execution)
-
anti-virus that DOESN’T WORK half the time (ask me about infections that WHIZZED right by SEP - like the CNN spam sourced Windows XP Antivirus virus/malware)
-
constant maintenance releases/bug fixes. 99% of the time these upgrades cause major issues.. and there’s one every couple of months. RTM-MR1-MR2-MR3–blah
-
50-80 minutes on hold to get to tech support
-
recurring issues with LiveUpdate, random definition distrubition
-
huge footprint, slows endpoints down considerably compared to SAV
-
firewall is completely problematic - I don’t even use it
-
15 GB server disk footprint. I have 50 workstations and a 10 GB SEP embedded management database - that’s 200 mb per workstation! WTF?!
-
i could go on…
With that said, all our SEP products (including Symantec Mail Security which I have less of a problem with) will be expiring in March of 2009. I’m probably moving to AVG. Can’t say I’d recommend any of Symantec’s products, maybe with the exception of Backup Exec.
Random Freeway Encounter of the Day
It’s 2:45, September 26th and I’m traveling North on the 405 near the Sunset Blvd. exit in my Porsche, doing my guaranteed-to-suck Friday commute home at a brisk 0-20 MPH in heavy traffic. I’m in the #3 lane and there’s a newish Audi S8 in front of me, I’m a good car or two car distances from him. All of a sudden I see this Audi shutter, but don’t think anything of it - god knows the 405 is littered with potholes. Then I saw a lady in the passenger seat look behind the car at me and again I thought nothing of it. This Audi then proceeded to start going very very slow, so I go to the #2 lane to pass him thinking “WTF is wrong with this guy?!”. I’m blaring Metro Station in a total “commuting zone”. I see that he’s pacing me on the right, so I look over and the dude in the Audi is making a hand gesture for me to pull over (again I’m like, “WTF?!”). I turn down the music and hear him say, “you hit me, pull over.” I replied, “I didn’t hit you!” He then insists I hit him and tells me I need to pull over. I proceed to exit at the Moraga exit following Sunset and pull into the gas station.
My head was immediately clouded with negative thoughts like “how did I hit this guy and not even realize it?”, “how the fuck am I going to pay for this!” or the “I need to cut down on my drinking!” We pull into the Chevron off the exit. I grab my wallet and insurance info and proceed to exit my car and he is parked right behind me. I immediately go examine my front bumper for “damage”. What do I find: nada, jack shit - I look at his bumper with him and find no damage, just a McCain 08 sticker.
I should have told this old douchebag with his trophy Pinay mail-order bride that he was a complete ass. Instead he thanked me for pulling over and I went about my commute in utter fucking astonishment. God I hate the 405!
Wolfgang’s Restaurant CUT unveils it’s “douche” dining room
Site of the Day: Hot Chicks with Douchebags
Came across this awesome site today. The title says it all. Here are a few choice samples of the horror you will find on the site.
Nice eyebrows homo!
You gotta be a serious Lord of the Rings fan to tattoo middle earth on your chest.
Project: Convert an Electromechanical IA2 Phone System to an Avaya Partner ACS
“Hello operator? Get me Chelsea 602 please.”
- Project:
Convert 1A2 system to Avaya Partner ACS, preserving existing cable/wire. - Scope:
3 CO Lines (2 Voice, 1 Fax), 1 Gate Line, 10 Extensions, Fax Machine, Answering Machine - Parts Used:
Avaya Partner ACS R6 Module, 308EC Module, 2-Slot Carrier, (2) 66-Blocks with preinstalled jacks, (1) Standard 66 Block, Amphenol to RJ11 Converters, APC Back UPS 650, RCA 5-Disc CD Player
This project was for my Grandmother’s house. She’s had her 1A2 system for 40+ years and up until recently it has given great service. Line 3 on the 1A2 was giving serious audible static to the point of not being usable. Instead of troubleshooting and fixing the old system, I figured it was more cost-effective to put in a used, but more modern system. I chose the Avaya Partner ACS as the replacement system as it’s cheap, full-featured and I have experience with it (I’ve owned a few).
If you don’t know what an Electromechanical 1A2 system is, think of it as sort-of the OG of phone systems. It was the first prevalent multi-line phone system. You can read more about the 1A2 at Wikipedia. Here’s a picture of a 1A2 phone:
See that crazy connector hanging off the right of it? That’s the amphenol connector which you may remember from a Parallel printer’s connection to a computer before USB became popular. Each 1A2 phone required a 25-pair cable to operate and terminated with an amphenol connector at the phone end. For our project we simply disconnected the old phones and snapped on an amphenol to RJ11 adapter. In some circumstances we had to chop the amphenol off and use a biscuit, but the majority used adapters. The good news is when you are replacing a 1A2 is you’ll have LOTS of existing cable to deal with.
In this particular project there were two blocks that cross-connect to the KSU, both requiring retermination. One of the blocks was in a central spot near the system in the basement (Block A) which was connected to the KSU via another 25 pair cable. This is where the majority of extensions terminated and where Block B cross connected as well. There was another block (Block B) in the attic powering the upstairs 3 extensions (this was a surprise we found late in the job). My task was to reterminate the cross-connect blocks so that every phone would have it’s own dedicated 2 pairs. In a 1A2 system each phone “shares” a series of pairs with the other phones… it’s complex to explain and Wikipedia does a better job of it.
My friend Walter (thanks Walt!) and I completed the job in about 11 hours on a Saturday. It worked out great and my Grandmother loves her new phone system. Check out the pics below of the before and after. You can also read more at this thread at Sundance Communication’s phone system tech support forum where I asked pre-install questions to the experts, having never done something quite like this before.
Before & After Shots:
All project photos:
