Failed to create SSL context : Invalid argument at /usr/libexec/webmin/ line 4383

The certificate is ok and ssl was working. De server also have plesk 17.8.11 (plesk onyx).

After upgrading to plesk 18.0.21 (plesk obsidian), webmin won't start anymore with ssl enabled, ssl disabled works fine. The log gives the error:

Failed to create SSL context : Invalid argument at /usr/libexec/webmin/ line 4383

As far as i know: plesk doesn't install, change nore delete anything from perl.

Access to the server can be provided if needed.

Kind regards Jan

Closed (fixed)


Howdy -- when trying to run two control panels on the same server, you can indeed run into some problems.

That particular message occurs if Virtualmin isn't able to use the "Net::SSLeay" module.

You'd want to ensure that module is installed, and that it's in the path for Perl.

That doesn't sound like a Virtualmin or Webmin bug that you're seeing there though. As it looks like you're using Virtualmn GPL there, you'd want to use the Forums for any additional questions. We monitor the forums, along with lots of wonderful folks in the community. Thanks!


I am not using virtualmin, only webmin, and this is a webmin issue because it worked fine before and now it doesn't anymore. net::ssleay is installed, the certificate is ok, selinux is disabled. Plesk doens't do anything with perl so it would surprise me if the plesk update would have changed the perl path, it seems something was changed

The perl path is ok (as far is i can tell). What should it be and how can i test that? how do i test if webmin can use ssleay?

I see on that someone had the same error on ubuntu (my server is on centos7)

I would be willing to pay for the support intervention, as long as it gets fixed. I can't imagine i am the only plesk user that also uses webmin for server maintenance.

regards Jan

That's not a common error we see, and we don't attempt to do any testing alongside other control panels. That's not a setup we regularly see or try to support.

That said, it may be able to work, and I currently don't know what's causing the error you're seeing there... there could be a very simple solution. Or there may be no solution.

However, with the holidays now, we're stretched pretty thin -- we don't have the staff to be able to dig into that right now... a few days ago we disabled all the Professional services options on our website because of that.

That said, even if that weren't the case, we can't guarantee that setup would work, and hiring us wouldn't guarantee a solution. And we certainly don't want to take your money only to find we couldn't fix it.

For now, my suggestion would be to open a new Forum post, and to ask there, as perhaps some folks in the community may have some ideas for you there.

In the meantime -- I'll run it by Jamie to see if he has any ideas.

Thank you for your suggestions. I will try the forum and if nothing works i'll ask for payed support after the holidays. It wont be "just taking my money", you are the experts and if you can't fix it, then at least i know 100% for sure that there is no solution. If i didn't do it, there would always be in the back of my mind: "isn't there anything else i could have done?"

Kind regards Jan

Ilia's picture
Submitted by Ilia on Tue, 01/07/2020 - 07:32

Status: Active ยป Closed (fixed)