torecoupon.blogg.se - Awstats 6.4

#AWSTATS 6.4 INSTALL#
#AWSTATS 6.4 UPDATE#
#AWSTATS 6.4 WINDOWS#

He is still searching for a fix, the reason is found, i will try to translate it from german to english: Notice: if you want to add another domain just repeat these steps from 3-5 Now use this url to see if everything is ok It would be nice if you add these commands to cron tab

#AWSTATS 6.4 UPDATE#

# /usr/local/awstats/or if you want to update all at the same time us this LogFile="/home/httpd/vhosts//statistics/logs/access_log"ĥ) All you need to do now is to update awstats data base using one of these two commands # vi /etc/awstats/awstats.change log path to: You will be asked about your domain and path to nf file so enterĤ) you need to provide correct path to access_log file, so open conf file for your domain using vi text editor usin this command: If you want to use other version of rpm find url first and replace this one.ģ) then you will need to setup awstats_ run:

#AWSTATS 6.4 INSTALL#

Same for top countries with Russia, for instance, having way too inflated numbers on AWStats compared to the reality.Here is a full guide for linux in a few very simple steps :įirst you will need a shell access, the most popular program is putty (ssh emulator) download one if you dont have it, login as a root user and folow the instructions:ġ) you need to install awstats, the best way to install it is using awstats rpm, so run this command first. If I exclude the “unknown” category in AWStats, the remaining table becomes a bit more usable. Similar is the case with top operating systems and top browsers. If I exclude back-end pages such as wp-cron.php, /feed/ and wp-login.php that the bots are trying to access, I may get something closer to the actual numbers. There could be a way to make it more accurate by manually excluding other bots. They automatically exclude the “not viewed traffic” which includes “traffic generated by robots, worms, or replies with special HTTP status codes”.ĭespite these efforts, it seems to miss out on a lot of bot traffic. AWStats tries to isolate and exclude robots. It seems very clear that the majority of data included in AWStats is made by robots. Chrome is second with 18.5% of all page views. AWStats: “Unknown” 64.7% (doesn’t show the number of unique visitors but a number of page views).

#AWSTATS 6.4 WINDOWS#

Windows is second with 15.6% of all page views.

AWStats: “Unknown” 67.5% (doesn’t show the number of unique visitors but a number of page views).

Interestingly enough, Russia is listed second on AWStats while it doesn’t even make it into the top 10 on Plausible Analytics.

AWStats: USA 207k (doesn’t show the number of unique visitors but a number of page views).

My actual top post, /blog-or-vlog/, is 6th in the list on AWStats with 3.2k views. Most of the page views and pages that AWStats counts are made by bots to the backend pages that are not customer facing.

AWStats: /wp-cron.php 93k, /feed/ 78k, home page 67k.

Plausible Analytics: /blog-or-vlog/ 2.5k.

Between Google USA, Google UK, Google India and others, there were more than 10,000 visitors from Google combined according to AWStats. AWStats splits traffic from Google according to the locality. Plausible Analytics displays all traffic from Google under one referral.

More than 100% higher number of visitors according to AWStats.ġ8 times higher number of page views according to AWStats. There is a great data disparity between the two. You can see my complete data for the month of June in this open dashboard.Īnd here are my top line stats from AWStats:

Here are my top line stats for June in Plausible Analytics. To understand the difference in the data between JavaScript-based analytics and server logs, I’ve compared the stats between Plausible Analytics as client-side analytics and AWStats as server-side analytics on my own website in June 2020.