Feature disabled MESSAGE

[moura1990]

Dear Administrator,

I received the following message while trying to use a feature:
“This feature has been disabled. Please, contact your administrator.”

Could you please review my access and enable this feature if possible?
I would appreciate your assistance in resolving this issue.

I need to resolve my SSL certificate issue. I received the message and need to know if it has been resolved.

 

[mrburnsx]

Can you please elaborate on the exact feature (or what exactly you clicked on) that is giving you that message?

 

[moura1990]

The function to view system messages has been suddenly disabled. When clicking on the function, the following message appears: "This feature has been disabled. Please contact your administrator."
As I mentioned, I need to view the messages.
I don't understand why they deactivated it out of nowhere.

 

[mrburnsx]

It is disabled as intended and not supposed to be enabled at this time. Please try SSL again, but uncheck the wildcard box option when doing so.

 

[moura1990]

This information appears if I do this.

"Your request could not be executed.
/usr/local/directadmin/data/users/xxx:database not found, closing..."
P

 

[Eric S]

This should be resolved.

 

[moura1990]

This should be resolved.

Nothing resolved.

I need you to release the messages. And resolve the SSL issue. I received the messages and I can't view them without knowing why.

The information I mentioned above appears.

 

[Eric S]

I apologize this should be resolved and you should not see any errors when trying to get a valid SSL

 

[moura1990]

I apologize this should be resolved and you should not see any errors when trying to get a valid SSL

NOTHING RESOLVED. I need a solution because you disabled messaging without any prior notice. I can't activate SSL; the message I told you about appears. I don't understand why.

 

[mrburnsx]

NOTHING RESOLVED.

To clarify, the message center is disabled and will NOT be enabled at this time.

Please try SSL again, but uncheck the wildcard box option when doing so. Please provide any supplemental error messages when trying again.

 

[moura1990]

To clarify, the message center is disabled and will NOT be enabled at this time.

Please try SSL again, but uncheck the wildcard box option when doing so. Please provide any supplemental error messages when trying again.

NOTHING RESOLVED.
It remains the same.

 

[Eric S]

This should be resolved as mentioned. Please re-attempt to generate and SSL as needed. There may be limits on the domain name but the error you saw previously should no longer be valid.

As for messages as mentioned by our community member this is disabled by default and is not an issue.

 

[moura1990]

This should be resolved as mentioned. Please re-attempt to generate and SSL as needed. There may be limits on the domain name but the error you saw previously should no longer be valid.

As for messages as mentioned by our community member this is disabled by default and is not an issue.

2026/03/06 13:51:29 [INFO] [xxxxxxxx] acme: Obtaining SAN certificate
2026/03/06 13:51:29 Could not obtain certificates:
acme: error: 429 :: POST :: https://acme-v02.api.letsencrypt.org/acme/new-order :: urn:ietfarams:acme:error:rateLimited :: too many certificates (50) already issued for "x10.network" in the last 168h0m0s, retry after 2026-03-06 20:58:12 UTC: see https://letsencrypt.org/docs/rate-limits/#new-certificates-per-registered-domain
Failed to issue new certificate .
See the error.

 

[Anna]

The good news is that the error message tells you exactly why and what can be done, ie there is a rate limit and you can retry at the earlist at 20:58:12 pm UTC, which was a few minutes ago. This limit is imposed by Let's encrypt and has nothing to do with the x10 servers nor is it under x10 hosting's control.
If you wait too long you may run into the limit again, as according to message there's a max of 50 to be issued before a cool down period is imposed on that domain.

 

[moura1990]

This should be resolved as mentioned. Please re-attempt to generate and SSL as needed. There may be limits on the domain name but the error you saw previously should no longer be valid.

As for messages as mentioned by our community member this is disabled by default and is not an issue.

RESOLVED THANKS. I managed to resolve it now.

 

[moura1990]

The good news is that the error message tells you exactly why and what can be done, ie there is a rate limit and you can retry at the earlist at 20:58:12 pm UTC, which was a few minutes ago. This limit is imposed by Let's encrypt and has nothing to do with the x10 servers nor is it under x10 hosting's control.
If you wait too long you may run into the limit again, as according to message there's a max of 50 to be issued before a cool down period is imposed on that domain.

RESOLVED THANKS. I managed to resolve it now.