Mini-Howtos

Want to support HowtoForge? Become a subscriber!
 

I created a user in ISPConfig but I cannot see him on the system.

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.

I have deleted a user. Now ISPConfig does not let me create a new user with the same user name.

Most probably you have forgotten to delete the user from the recycle bin. Only after you have deleted the user from the recycle bin are you able to create a new user with that user name.

I can see a user's website under www.xyz.tld/users/testuser, but not under www.xyz.tld/~testuser.

Comment out the lines

AddModule mod_userdir

and

LoadModule mod_userdir

in your httpd.conf and restart your Apache.

I created a new user. How can I reach his website?

If you created a user named testuser for the web www.xyz.tld, you can reach his personal website on

www.xyz.tld/~testuser

or

www.xyz.tld/users/testuser

Some services are shown as "Offline" in the ISPConfig though they are running on the server.

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.

Is there a logfile in ISPConfig?

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.

What are Co-Domains?

Under "Co-Domains" you can enter subdomains or even total different domains that should point to that web.

Example:

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).

I cannot reach the ISPConfig system on port 81.

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

ps aux

on the command line, or just restart the ISPConfig system:

/etc/rc.d/init.d/ispconfig_server restart (RedHat/Mandrake)

respectively

/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.

What is the difference between complete and partial deinstallation of the ISPConfig system?

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.

How do I start or restart the ISPConfig 2 System manually?

RedHat/Mandrake:

/etc/rc.d/init.d/ispconfig_server start|stop|restart

SuSE/Debian:

/etc/init.d/ispconfig_server start|stop|restart

first page
previous page
...
12
next page
last page