I've got everything running smoothly, and my migration has gone well. However, when clients try to login to their backend to administrate email, sql, and whatnot (www.theirdomain.com:81) no one can login. Yes, the users are created, and one is set to 'Administrator'. But still nothing. www.theirdomain.com:81/mailuser works fine and so does webmail.
There is a difference between a login for a client at URL http://www.yourdomain.tld:81 and a login for a user of a certain domain at URL http://www.yourdomain.tld:81/mailuser. You have set the (mail)usernames/passwords already to login at http://www.yourdomain.tld:81/mailuser. So that works. Now you have to create an account for the client to login at URL http://www.yourdomain.tld:81 You can do this in ISPConfig under ISP-manager > select a client > Select the tab Login Data. A client have full control over his domain. Not all the users have full access over the domain. Which is recomended and is as it should be.
I got the same problem. I created an new client and an new website. I setted the login data for the client with an username and password. Now I try o login to ispconfig with this data. And it tells me the username or password is incorrect. Any ideas???
I guess it is not the same problem as the first poster of this thread has not created a client login. Please make a new thread if you have a problem and dont append your post to another thread. You are sure that you created the username and password in the client and not in the website and that you use https://www.yourdomain.com:81 for login and not the mailuser login?
You created a client as shown here: http://ispconfig.org/downloads/manual_en/manual_reseller_en_src.htm#3_2 and now this client cannot log in with his username and password? Are you sure you didn't mix up email/ftp users and ISPConfig users?
It works now with new clients. The first one didnt worked. I dont know why, but it just didnt. My new clients do work. So I just created an new one for him. Maybe it was because the client domain was the same as my server domain. Which shouldnt be any problem.
This can become a problem when you set up catch-all email addresses. Have a look here: http://www.howtoforge.com/faq/9_33_en.html You should use a technical domain for your server, i.e. a domain that you don't use for web hosting, email, etc. I do it like this on my servers.
Eitherregister a new domain or create a subdomain of your existing domain like server1.yourdomain.com and use this as technical domain.
