Domain pointing to external MX on Plesk
If you are using an external MX record and also using a Linux environment for…
Introduction:
If you encounter the Webalizer errors:
Error: Unable to lock DNS cache file /usr/local/psa/var/webalizer.cache
don’t worry this is a common issue caused by cache file permissions. You can quickly resolve it by recreating the cache file and correcting its ownership and permissions.
1. Remove the existing cache file
rm -f /usr/local/psa/var/webalizer.cache
2. Create a new empty cache file
touch /usr/local/psa/var/webalizer.cache
3. Set the correct ownership
chown root:root /usr/local/psa/var/webalizer.cache
4. Set proper file permissions
chmod 644 /usr/local/psa/var/webalizer.cache
5. Verify file status
stat /usr/local/psa/var/webalizer.cache
Always make sure you’re logged in as root before making changes. Incorrect ownership or permissions can prevent Webalizer from functioning correctly.
Explore more hosting insights, tips and industry updates.
If you are using an external MX record and also using a Linux environment for…
If you have a website, whether for business or leisure. You may have found certain…
In this article, we will explain how to clear the cache in Laravel Applications. Talking…