Sometimes you may see horde webmain in Plesk windows showing page not found errors or not working properly during sending email via Webmail. Here is the general fix for all the problems.
"%plesk_bin%\websrvmng.exe" --reconfigure-webmail
"%plesk_bin%\defpackagemng.exe" --fix --type=webmail.horde
Ever locked yourself out of your Server while making some iptables changes? What about when you change your SSH port and then forget what you set it to?
These are common support tickets we receive at RSHosting. In many cases this is something our customer’s can fix on their own if they are using cPanel on thier VPS/Server.
cPanel comes with a number of “hidden” autofix commands that allow for administrators to fix common problems simply be logging into WHM and going to a special URL. Two of the most useful ones I’ve seen are flushing iptables and restarting SSH in “safe mode” (basically the default settings and port).
Flushing iptables rules
https://yourdomain.com:2087/scripts2/doautofixer?autofix=iptablesflush
Restart SSH in safe mode
https://yourdomain.com:2087/scripts2/doautofixer?autofix=safesshrestart
Once you hit the URL you will be prompted to log in. Simply enter your root password and cPanel will do the rest. These have definitely saved me on more than one occasion when my attempt to ’secure’ my server worked a little too well. Remember that if you happen to also lock yourself out of WHM through iptables, you will not be able to hit the URL’s I mentioned. In that case, contact support.
Other useful commands as well:
Reset the Firewall Settings
https://yourdomain.com:2087/scripts2/doautofixer?autofix=iptablesflush
Reset the SSH Settings
https://yourdomain.com:2087/scripts2/doautofixer?autofix=safesshrestart
bsdbindfix
https://yourdomain.com:2087/scripts2/doautofixer?autofix=bsdbindfix
Autorepair
https://yourdomain.com:2087/scripts2/doautofixer?autofix=autorepair
Compress Zlib
https://yourdomain.com:2087/scripts2/doautofixer?autofix=Compress-Zlib-1.42.tar.gz
Compresszlibfix
https://yourdomain.com:2087/scripts2/doautofixer?autofix=compresszlibfix
dbdmysql
https://yourdomain.com:2087/scripts2/doautofixer?autofix=dbdmysql
Cooldiagnose_apache_conf
https://yourdomain.com:2087/scripts2/doautofixer?autofix=diagnose_apache_conf
fpindexfile
https://yourdomain.com:2087/scripts2/doautofixer?autofix=fpindexfile
libxml2-2.6.28.tar.gz
https://yourdomain.com:2087/scripts2/doautofixer?autofix=libxml2-2.6.28.tar.gz
libxml64fix
https://yourdomain.com:2087/scripts2/doautofixer?autofix=libxml64fix
pro*
https://yourdomain.com:2087/scripts2/doautofixer?autofix=pro*
spamd_dbm_fix
https://yourdomain.com:2087/scripts2/doautofixer?autofix=spamd_dbm_fix
test
https://yourdomain.com:2087/scripts2/doautofixer?autofix=test
vfilterfix
https://yourdomain.com:2087/scripts2/doautofixer?autofix=vfilterfix
yumduprpmfix
https://yourdomain.com:2087/scripts2/doautofixer?autofix=yumduprpmfix
resellerresourceacctounts
https://yourdomain.com:2087/scripts2/doautofixer?autofix=resellerresourceacctounts
horde_sqmail_current_fix
https://yourdomain.com:2087/scripts2/doautofixer?autofix=horde_sqmail_current_fix
Safe to say that a majority of problems in any virtual hosting system will be related to DNS, because DNS requires cooperation of numerous systems, rather than single one, and DNS problems can cause trouble to nearly every service on a hosting system.
For DNS to work, must have correct glue records at your registrar, as well as correct records on your Virtualmin system (or whatever system you choose to use for DNS, if not the Virtualmin server). Also, any slaves must also have correct records, or you will experience intermittent resolution failures.
Checking your glue records can be done using the whois command.
whois example.com
Look for the “domain servers” or “name servers” section of the output. The resulting names must resolve to your DNS servers.
Glue records must be configured at your name service registrar. Virtualmin and Webmin have no control over records at your registrar, so problems must be corrected using whatever interface your registrar provides.
The NS records on your Virtualmin server should match those found in the glue records discussed previously, or intermittent problems may result.
You can find the NS records for a given zone using the host command on your server:
host -t NS example.com
A Records Address records, or A records, are the basic building block of DNS zones. They map names to IP addresses. To check an A record, use the host command:
host example.com
You can also specify the name server used to resolve queries by adding the name or IP of the server you wish to query to the end of the command:
host example.com ns1.example.com
Or, if you aren’t sure about the nameserver IP address resolving correctly, you can use an IP:
host example.com 192.168.10.10
Mail exchanger records, or MX records, provide mail servers the information they need to know how to deliver mail for a particular domain.
You can check an MX record with the host command:
host -t MX example.com
