- Web Server
- Control Panels
- Site Map/RSS Feeds
Co-Domains please enter xyz.tld (without host!). The website will then also reachable via xyz.tld.Under
Activate the option SSL on the tab Basic of the web and go to the tab SSL. Provide your information there (State/county and Organizational unit are optional").
Please leave empty the fields SSL Request and SSL Certificate. Choose Create Certificate under Action and then click on Save.
Afterwards, if you go to the tab SSL again, you will find the Certificate Signing Request (CSR) under SSL Request. Copy the CSR. With this CSR you can apply for an SSL certificate at companies like Verisign (www.verisign.com), Baltimore (www.baltimore.com), Entrust (www.entrust.com), Geotrust (www.geotrust.com), IPSCA (www.ipsca.com) or InstantSSL (www.instantssl.com).
Apache Directives field in the ISPConfig Interface.Never edit the vhost file manually. On the next update of the system your changes will be overwritten! Instead put your additional vhost configuration in the
If you want to add something manually to other files, e.g Postfix' local-host-names, you can put your configuration at the end of the file in a section that is not overwritten by ISPConfig.
Go to Management -> System Config -> Settings. On the tab ISP-Manager you will see the field User Prefix where you can specify a prefix for users. You can use one of the following placeholders:
If you don't want a prefix, just leave it blank.
Please check that you did not mix up customers and users. A customer can login to the ISPConfig and manage his sites (and create system users on the tab User & Email) but he cannot login to the system (e.g. by using FTP, email) because he is not a system user. A customer is an object that exists only in the ISPConfig, but not on the system.
A system user cannot login to the ISPConfig, but he can use services such as email, etc.
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.