Config warnings

error:03000082:digital envelope routines::invalid key length error:03000082:digital envelope routines::invalid key length error:03000082:digital envelope routines::invalid key length error:03000082:digital envelope routines::invalid key length error:03000082:digital envelope routines::invalid key length error:03000082:digital envelope routines::invalid key length error:03000082:digital envelope routines::invalid key length error:03000082:digital envelope routines::invalid key length error:03000082:digital envelope routines::invalid key length error:03000082:digital envelope routines::invalid key length error:03000082:digital envelope routines::invalid key length error:03000082:digital envelope routines::invalid key length error:03000082:digital envelope routines::invalid key length error:03000082:digital envelope routines::invalid key length error:03000082:digital envelope routines::invalid key length

I’m getting this error on my only child site that I have currently.

Tried disabling the require pw setting in child plugin. But no success. The unique security id setting was and is active. Please advise. That id seems to have changed from my initial connection though.

Main site is a subdomain of the child site. Both go through Cloudflare.

Also on both my main and child plugin the following warnings are there:

WP memory limit
cURL Timeout
OpenSSL Working Status

On main site the above digital envelope error is not there.

I guess these 3 can be sorted by contact my hosting provider?

And also the uptime monitoring seems disabled. Is it because of one of the above issues?

Please advise.

Thanks!

Hey @developme

Welcome to the MainWP community!

For future reference, please don’t bundle multiple issues in a single topic.

Those errors are coming from the OpenSSL library.

It doesn’t affect MainWP functionality, and the warning might even be a false flag on our end.

The actual error means the encryption key length doesn’t match what the selected cipher expects, e.g., AES-256 requires exactly 32 bytes. This can happen if the host updated their PHP or OpenSSL and now enforces stricter checks.

It’s not something MainWP controls, so the host support is in the best position to explain or resolve it.

You can find instructions here on how to resolve system requirements issues: Resolving System Requirement Issues - MainWP WordPress Management

It is not related to the OpenSSL library errors, and it also shouldn’t be related to WP Mem Limit or cURL timeout.

Please open a private Help Desk ticket, and we will gladly look into the Uptime Monitoring issue: https://mainwp.com/my-account/get-support/

Hello,

Great, so I don’t have to worry about SSL warning error, correct?

The other 3 warnings: I’ll check with my host.

Regarding uptime monitoring error, how do I create an account to open a ticket? I don’t see a Signup option.

Thanks!

You can always email us directly at [email protected] to open a ticket.

And to create an account on mainwp.com in order to be able to submit a ticket on https://mainwp.com/my-account/get-support/, follow this link https://mainwp.com/checkout/?add-to-cart=1264797&empty-cart, which will add the Free bundle to your cart.

Then, at the checkout page, you will have an option to enter your new Account username/password.

Once you place the order (there will be no charge!), an account will be created.

Thanks!

BTW is there a way to link the self hosted dashboard with the Mainwp account? Or a backup feature to sync or restore things if needed?

You’re welcome.

MainWP is self-hosted and private, so it is up to the MainWP user to handle backups of their Dashboard site.

1 Like

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.