prithwirajsinha99
Verified User
- Joined
- Nov 2, 2020
- Messages
- 6
I can not find these filesVia SSH, change SSL=OFF to SSL=ON in the .conf file.
If disabled for the user, change in file /usr/local/directadmin/data/users/USER/user.conf
If disabled for the domain, change in file /usr/local/directadmin/data/users/USER/domains/DOMAIN.TLD.conf
indicates the User in which you are looking for.../USER/
this would be your domain.../DOMAIN.TLD
Account manager in user level??? As far as I know user level does not have any "account manager", next to that, enabling SSL (or disabling it) is done in Domain Manager when using user level.disabled SSL in user level
Account Manager - SSL Certificate - Disable
Could not execute your request
SSL is not enabled for this domain
Can confirm this bug. Disabled SSL on one of the domains of a user in user level since the domain isn't active anymore. After that got the same error as topic starter and can't access the SSL Certificates page anymore. It just keeps displaying:
Code:Could not execute your request SSL is not enabled for this domain
Via SSH, change SSL=OFF to SSL=ON in the .conf file.
If disabled for the user, change in file /usr/local/directadmin/data/users/USER/user.conf
If disabled for the domain, change in file /usr/local/directadmin/data/users/USER/domains/DOMAIN.TLD.conf
If you you choose disable ssl. Then it converts to disabled. Are you waiting a few minutes for directadmin task to fully run? Then after a few minutes try to re enable it? Then wait a few more minutes to see if it takes again. Just wondering if it is a timing thing.Yup, user has ssl in his package otherwise he couldn‘t have visited the SSL Certificates page to disable ssl in the first place. Also, the other domain of this user still has ssl enabled perfectly fine.
oh yes correct. I think what everone is expecting is the button to disable to become back as a button to enable. Its only there because some one did domain setup.The end user can enable SSL for the domain himself but he has to go through Domain Setup
CorrectSo maybe it's not a bug but a feature after all?
agreed.It would be a lot more user friendly/consistent if the enabling/disabling worked like for example the Spamassassin Setup page where you can enable and disable on that page without having to go to Domain Setup or anything.
Are we ready to retrain the world?SSL be renamed to TLS nowadays?
If we have to vote between those two I'd vote for the latter!Are we ready to retrain the world?. I vote we label it "that lock thingy" or "encryption enable"
Think of all the support requests...such funthe latter!
Yes, like in the screenshot (enhanced skin). I thought you ment that option would not be available anymore after disabling it there.The end user can enable SSL for the domain himself but he has to go through Domain Setup click the domain he wants to enable SSL for again and click "Secure SSL".