hotelgasil.blogg.se - Awstats password protect

This happened, by the way, when Plesk was upgraded from 11 to 12, or somewhere in between. So take heed, if you implement this security measure, Plesk may not honor your preferences, meaning that you will inevitably need to go through and change the setting after each Plesk update. You can do this either on a per directory basis in /etc/apache/nf or through the use of a. Update (7): After taking the time to go through all of my domains and change the settings for each (which in Plesk is no quick task), I have re-checked on my Plesk Statistics settings only to find that Plesk 12 has automatically changed every single domain’s Stats settings back to the default setting, enabled. Update: if you use the “require login” technique, the login should be the same as your site’s main/FTP username and password. The settings for Plesk stats are located in the General Hosting settings for your domain. htaccess file: RedirectMatch 403 ^/plesk-stat/? 5tarteo wizard Video TLtcrlals C range Password Find Mail Frequently Accessed Areas Password Protect Directories Perl Modules Awstats phpMyAdmin Cron. htaccess - add this rule to your site’s root.

Require login - if you want to use the stats, require a login (make sure the box is checked).

Disable ’em - if you don’t need Plesk stats, simply disable them (select “None” from the web-stats dropdown).

Any of these techniques will work to secure your stats. Here are three ways to lock down your Plesk stats (either AWStats or Webalizer), depending on whether or not the stats are required.

If, however, these pages exist and are available to the public, you may want to secure your data using any of the following techniques. If you get a password prompt or the pages don’t exist, then nothing to see here, you’re all good. One last option is to password-protect the stats directory. Here is an important security tip for Plesk users.ĭepending on your current Plesk configuration, your server stats may be openly available to anyone who visits either of these URLs: Normally, to see your web hosting statistics (AWStats), you must first log into your cPanel. Any ideas why awstats would not work out of the box? I had installed i-mscp on Ubuntu 12.04 before that and did not run into any issues.An important aspect of website security is protecting sensitive data such as your server statistics. Now edit the stats virtual directory by selecting the option Edit Virtual Directory, and disable. When I try to load the stats for the second domain / user, it won't accept my username/password at all, although I verified that it is the right one (at least I can log into the panel with the same credentials). Awstats virtual directory can be password protected by following the given steps: Login in HC Panel as Reseller or Webadmin select the required website and navigate to the path Hosting Services. So I configured 2 domains (users) and the strange thing is that 'domain1/stats' accepts my username and password, but then produces an apache 404 error page (The requested URL /stats/ was not found on this server). The cronjob seems to be running fine and the corresponding logs are being created and I could not find anything related to stats in the logs. Awstats is installed and I selected 'dynamic' during the setup. While everything seems to be working fine in general, I cannot access the web statistics pages. Hi there, I just set up a testserver (vserver) running on Debian Wheezy and i-mscp 1.1.0-beta1 (Build 20120630), pulled from github.