- Web Server
- Control Panels
- Site Map/RSS Feeds
Comment out the lines
in your httpd.conf and restart your Apache.
If you created a user named testuser for the web www.xyz.tld, you can reach his personal website on
The ISPConfig checks the status of the services on localhost (IP: 127.0.0.1). It may be that some of your services only allow connections to specific IP addresses and not 127.0.0.1 (in Apache this is done with the Listen directive). If you allow connections to localhost the status will be shown correctly in the ISPConfig.
Another possibility is that the affected services do not run on the standard port intended for it.
The ISPConfig log is /home/admispconfig/ispconfig/ispconfig.log. The system logs which command was executed in which line in which script and if the command was successful (Status: INFO) or not (Status: WARNING).
If you encounter problems with ISPConfig please have a look into the logfile and see if there are warnings. Also have a look into the logfiles under /var/log. If you cannot solve the problems on the basis of the logfiles and want to contact our support by email, please do not forget to send suspicious messages from the logs along with your email.
Under "Co-Domains" you can enter subdomains or even total different domains that should point to that web.
If you can reach your web by www.xyz.tld then you could enter the subdomain www2.xyz.tld under "Co-Domains". You could also enter the new domain abc.tld (e.g. with the host www, so that www.abc.tld points to your web www.xyz.tld).
Please check if you have tried to reach the system over the right protocol (https or http). If this is the case please verify that the ISPConfig system started before (with
on the command line, or just restart the ISPConfig system:
/etc/rc.d/init.d/ispconfig_server restart (RedHat/Mandrake)
/etc/init.d/ispconfig_server restart (SuSE)).
If this still does not work, then most probably your firewall (iptables or ipchains) is blocking port 81.
Partial deinstallation means that only the ISPConfig system itself will be uninstalled, not the objects created by it (web sites, users, DNS records, etc.).
On complete deinstallation also the objects created by the systems (web sites, users, DNS records, etc.) will be uninstalled. Thus, the server is reset to its original state.
Attachments with suspicious file extensions (e.g. exe) will be renamed automatically: e.g., USELESS_EYE_CANDY.EXE would be renamed to USELESS_EYE_CANDY.DEFANGED12345-EXE, so that one cannot open the attachment thoughtlessly by double-clicking. The attachment first has to be saved to the hard disk and to be renamed to USELESS_EYE_CANDY.EXE before it can be opened.
Note: The mailscanner feature is not the same as the antivirus.