We share the code for free. Try to improve the system mainly for our self how ever instead keeping it for our self we share the result and spread some love (and some code). Try to fix a solution by your self. And then create or a tutorial for it or maybe even create a pull request. This way the software can be improved.
If you want a Hosting Control panel out of the box please buy Cpanel…
Well, it’s not my fault that you didn’t know that this option is not working.
Yes, I know that is not best tool and that are better alternatives.
And after 3rd paragraph: well…What can I say. 20 years using linux, and “What do you want from me? It’s free!” is always there.
I fix it, but if I ask for an official or nearest way, is because I don’t want to fuck all install.
If you say: “we don’t have idea”, I can take as valid answer too.
Even a “wow, you found a bug, please, fill a report at github and will be try our best, but maybe take years (or never)” …
I have to admit I did not look deeper into it, before posting the link. if you tried that geoip plugin before and found it not working, that piece of information would have been helpful in your starting post already
however, awstats is a third party service that gets installed along with others. Hestia relies on the version in the repos to be somehow ready to use and it won’t really fix outdated or missing stuff within for you. so I am afraid indeed this is something you need to figure yourself or take over to the AWStats git/forums…
as others pointed out already, of course we can look into integrating a patch or plugin, but I think even then there can’t be real support here, as it’s always gonna be a plugin for third party software anyway
sorry if we sometimes sound rude here, just trying to set expecatations very straight all the time. I also guess different tone of voice often does translate badly and therefore answer might not sound like they are intended to
I could’nt fixed by myself. Seems that something not working. Also, I don’t take in mind to edit Hestia templates before. It could be related.
I did a rollback of all my changes.
I’m trying with proposed solution upgrading Hestia to master branch
This have an error:
root@srv:~# bash /usr/local/hestia/install/upgrade/manual/install_awstats_geoip.sh
grep: /usr/local/hestia/data/templates/web/awstats/awstats.conf: No such file or directory
Reading '/root/.cpan/Metadata'
Database was generated on Sat, 16 May 2020 13:41:04 GMT
Geo::IP::PurePerl is up to date (1.26).
Reading '/root/.cpan/Metadata'
Database was generated on Sat, 16 May 2020 13:41:04 GMT
Geo::IP is up to date (1.51).
sed: can't read /etc/awstats.conf: No such file or directory
Right path is /etc/awstats/awstats.conf
After run manually sed -i '/LoadPlugin=\"geoip GEOIP_STANDARD \/usr\/share\/GeoIP\/GeoIP.dat\"/s/^#//g' /etc/awstats/awstats.conf and exec again /usr/local/hestia/bin/v-update-sys-queue webstats (with new webstats.pipe added) seems to be working, but I will waint until tomorrow and let that awstats run tonight (my version hang at night)
Upgrade does a rebuild of the hestia users, this may include also dns configuration. Also you should have been warned while running v-update-sys-hestia-git that this command isnt for production server at all :
Can you write more what exactly you’ve edited and got a reset during the upgrade? Just to know if that is something we would need to fix before we release the new version.
DNS should not be resettet, there is no reason for it at all. As @eris wrote, please open a issue report with all informations you can get, so we can track down and try to reproduce your issue.