Hi,
I am posting this for anyone who possibly has this issue on their setup.
A bit of background:
Clients are logging in via the WHMCS client area by using the LoginKeys feature on DirectAdmin for one-click logins.
When you get this issue, you will not be able to use the one-click login, but the login credentials will work.
The domain will appear fine on the DA admin panel and all the permissions such as login keys will be enabled, the owner of the domain will show
as the reseller/admin but if you log into the reseller and try and search for the domain it will not come up.
The issue is the domain is not in the users' list of the reseller/admin and might be an issue during provisioning, only had like 7 cases in 4 months.
To resolve, you need to add the user to the "users.list" of the reseller, location of this file is:
Once the user has been added, you can save the file, do not force the save if nano informs you the file changed, rather exit and try again otherwise
another user will have the issue as you saved the file without that user.
I suspect that is what's happening when DA creates new users on the server when they overlap.
After this has been done, you will need to push the users' list live, use the following command:
The user details and login keys will now work within WHMCS, the domain will be accessible via its login details.
I suspect a suspension run on WHMCS will also be an issue for these domains if they are not rectified as the reseller can not properly alter the user.
I am posting this for anyone who possibly has this issue on their setup.
A bit of background:
Clients are logging in via the WHMCS client area by using the LoginKeys feature on DirectAdmin for one-click logins.
When you get this issue, you will not be able to use the one-click login, but the login credentials will work.
The domain will appear fine on the DA admin panel and all the permissions such as login keys will be enabled, the owner of the domain will show
as the reseller/admin but if you log into the reseller and try and search for the domain it will not come up.
The issue is the domain is not in the users' list of the reseller/admin and might be an issue during provisioning, only had like 7 cases in 4 months.
To resolve, you need to add the user to the "users.list" of the reseller, location of this file is:
Bash:
nano /usr/local/directadmin/data/users/domains/users.listOnce the user has been added, you can save the file, do not force the save if nano informs you the file changed, rather exit and try again otherwise
another user will have the issue as you saved the file without that user.
I suspect that is what's happening when DA creates new users on the server when they overlap.
After this has been done, you will need to push the users' list live, use the following command:
Bash:
echo "action=cache&value=showallusers" >> /usr/local/directadmin/data/task.queueThe user details and login keys will now work within WHMCS, the domain will be accessible via its login details.
I suspect a suspension run on WHMCS will also be an issue for these domains if they are not rectified as the reseller can not properly alter the user.