You'll need to contact your provider. I'm guessing their script isn't compatible with OpenSSL 3.0, but without more information (such as the stdout/stderr of the openssl CLI invocation here) there isn't much we can do on this end.
Whatever the precise issue though, it's almost certainly NOT related to the OP bug :).
You'll need to contact your provider. I'm guessing their script isn't compatible with OpenSSL 3.0, but without more information (such as the stdout/stderr of the openssl CLI invocation here) there isn't much we can do on this end.
Whatever the precise issue though, it's almost certainly NOT related to the OP bug :).