Is there a way to view stats without cpanel?

[jodie]

I'm planning to move about 10 customer sites from my current host. Right now they can see their stats in Urchin, by going to a subdirectory of their domain. There is no cpanel with the current host, and I won't be giving them access to this one after the move. If I can't give them access to their stats, I probably can't move them... Thanks.

[Lianna]

It's not a problem. You can easily create a subdomain called "stats" and setup a redirect to the appropriate stats directory. Then they would access the stats like: http://stats.****

 

 

Lianna

[jodie]

Thanks Lianna. I understand about the redirect, but still don't know where the stats directory is.

[Lianna]

Ah, yeah, that would help wouldn't it!

 

For AWStats the path would be:

http://yourdomain.com:2082/awstats.pl?config=yourdomain.com&lang=en

 

For Webalizer the path would be:

http://yourdomain.com:2082/tmp/yourusername/webalizer/index.html

 

For Analog the path would be:

http://yourdomain.com:2082/frontend/bluelagoon/stats/analog.html

 

How did I get those paths? I went to cpanel and clicked up the stats package. Highlighted the contents of my browser's address bar and copied it. Came here and pasted it.

 

Keep in mind. Each of these is truely still accessed through the cpanel and thus requires login! Also know that shortly, only one stats package will be made available.

 

Lianna

[jodie]

Thanks Lianna. I already new about the paths through port 2082. I am looking for a "no password" solution, or at least a solution that doesn't reveal the password for ftp, cpanel, etc.

[Lianna]

Wow, if anybody else wants to jump in here, please feel free.

 

Since the stats packages are a part of cpanel, I'm not sure that what you ask can be accomplished without a bit of work, if at all.

 

I could theorize that you could make a subdirectory and house within it a 'copy' of the raw logs (maybe using a daily cron job) and then install your own interpretter (stats package) within that site's public_html.

 

A second theory says that you create a script that contains the user/pass to the paths identified above and then encrypt it. Place the script in public_html somewhere and magically you're in the cpanel stats without having the user know the user/pass.

 

Now, I'm not a good resource for making either of those suggestions work, if they would at all, but there may be someone else here that has the programming experience to do it. ...ooh. I just got another 'theory' light bulb. Let me try something else, too and see what happens.

 

Back in a bit.

Lianna

[Lianna]

Ok. Encrypt or scramble this:

 

http://username:pass@******:2082/awstats.pl?config=******&lang=en

 

Then place it as a link in your site.

 

EDIT: After trying several options with this, it just is NOT safe. Here are some pitfalls:

1. You must still protect the username and pass from appearing in the status bar on mouse over.

2. Your username and pass still appear in the title of the browser when you get to the stats page.

3. Once on the stats page, you can edit the address bar to remove "awstats.pl?config=******&lang=en" and they are in your cpanel.

4. You could place the link into a container which could eliminate #2&3.

 

 

Lianna

[TCH-Rick]

I tried opening my AWStats from the Cpanel then I saved the page as stats.html to a local directory on my computer. Then I copied the *.txt files from my tmp/awstats directory to the local directory. I was able to view my stats fine locally using that method. Maybe a cronjob to copy those files each day would work.

[jodie]

I hadn't really thought about a programming solution. For security sake, the password could be stored in MySQL, read by a PHP program and passed to file(). Thanks for getting me on the right track.

[Lianna]

You're welcome.

 

Lianna