Jvanderlinde
New member
- Joined
- Aug 4, 2011
- Messages
- 2
Hello.
My Webhoster is recently upgrading all its direct admin licences and versions on their huge serverpark. I'm a large reseller user who owns up to 60 customers for various websites and so on. I provide them a website with all the options they need in order to get a fully operational business on the web.
One of the features that are included would be Awstats, something just as neath in tracking visitors as Analytics would be. Recently Awstats has stopped working on various websites and their reseller accounts. I asked my hoster what the problem was; They told me that Direct admin integrated Awstats could no longer be requested by using the direct url like domain.com/awstats/, instead you have to log into directadmin and view your stats using domain manager. Since i sell my clients a very solid package of software to manage their website, i would like to not give my clients direct access by FTP or Database level because of illegal copying and so on. My clients can live with the idea they have everything and can request support anytime they want,
but here's the deal. Awstats is usable while it lasts, untill the whole serverpark is updated and i'm forced to start putting alot of website into analytics accounts and tell people how to use them, because the top tier Direct admin decided to put their Awstats access into a higher level. What is wrong with just having a user / pass combi by using htaccess as a protection level? Can someone clarify why this choice is being made?
I'm not talking about 60 clients with 60 websites, more likely 150 websites and not my own websites mentioned
My Webhoster is recently upgrading all its direct admin licences and versions on their huge serverpark. I'm a large reseller user who owns up to 60 customers for various websites and so on. I provide them a website with all the options they need in order to get a fully operational business on the web.
One of the features that are included would be Awstats, something just as neath in tracking visitors as Analytics would be. Recently Awstats has stopped working on various websites and their reseller accounts. I asked my hoster what the problem was; They told me that Direct admin integrated Awstats could no longer be requested by using the direct url like domain.com/awstats/, instead you have to log into directadmin and view your stats using domain manager. Since i sell my clients a very solid package of software to manage their website, i would like to not give my clients direct access by FTP or Database level because of illegal copying and so on. My clients can live with the idea they have everything and can request support anytime they want,
but here's the deal. Awstats is usable while it lasts, untill the whole serverpark is updated and i'm forced to start putting alot of website into analytics accounts and tell people how to use them, because the top tier Direct admin decided to put their Awstats access into a higher level. What is wrong with just having a user / pass combi by using htaccess as a protection level? Can someone clarify why this choice is being made?
I'm not talking about 60 clients with 60 websites, more likely 150 websites and not my own websites mentioned
