You can fix the Virtualmin repos by running:
sudo virtualmin setup-repos
That’s unrelated to your curl error, though. I still don’t know where you’re seeing that, or what systems are involved.
Let me know what information do you need?
The server you are talking to using curl is telling curl to use SSLv3. That shouldn’t happen.
So, where are you running curl? Is it on your server running Ubuntu 20.04?
And, what is curl making a request to? Is it on the same server running 20.04 or something else?
There is no reason for an Ubuntu 20.04 system to ask for clients to use SSLv3. So, I can’t make any sense out of the problem you’re having, and you keep not answering about where you’re running curl and what curl is making requests of.
But, also, I don’t understand why, if this is a local server that’s not available to the internet, you aren’t just using http instead of https. None of this makes sense.
To be clear about the SSL thing and why I’m confused about where things are running: SSL3 is an old protocol. It’s never been the default on Ubuntu 20.04. Updating is not relevant to your problem.
OK I have Ubuntu 20.04 VM and inside I am running Virtualmin with Wordpress Multisite
When update Wordpress it asking me to update the network when I do I get this error
Warning! Problem updating https://website.local. Your server may not be able to connect to sites running on it. Error message: cURL error 35: error:1408F10B:SSL routines:ssl3_get_record:wrong version number
Yes but it still connect to the outside of my network to get updates of Wordpress and plugins. I know self-signed cert is not much but it still something right!!
Something for what? I still don’t understand what you’re trying to do. A certificate provides two things: Encryption (which a self-signed certificate can do, as long as you are able to convince your client to communicate with it), and identity (which a self-signed certificate cannot do, unless you explicitly add the CA cert to the CAs accepted by your client software).
But, this error is not about a self-signed certificate, as far as I know (I’m not sure why this thread turned into a discussion of self-signed certs, but I went along with it without paying close enough attention to the actual error). This error indicates the server you are trying to connect to with curl (I still have no idea what you’re doing or what server you’re connecting to) is not responding appropriately to the SSL/TLS negotiation.
Based on this: curl: (35) error:1408F10B:SSL routines:ssl3_get_record:wrong version number - Stack Overflow
It seems like it can be caused by proxies, misconfigured servers (trying to connect using https to a server only offering http), etc. I don’t know which one is you, but I don’t see any reason to think it’s a problem with the self-signed certificate (again, using the --insecure option allows curl to accept self-signed certs without error.
This doesn’t make sense. WordPress can not do anything to the network, it doesn’t have that kind of privilege.
curl -v https://website.com
- Trying 127.0.0.1:443…
- Connected to website.com (127.0.0.1) port 443 (#0)
- ALPN, offering h2
- ALPN, offering http/1.1
- CAfile: /etc/ssl/certs/ca-certificates.crt
- CApath: /etc/ssl/certs
- TLSv1.0 (OUT), TLS header, Certificate Status (22):
- TLSv1.3 (OUT), TLS handshake, Client hello (1):
- (5454) (IN), , Unknown (72):
- error:0A00010B:SSL routines::wrong version number
- Closing connection 0
curl: (35) error:0A00010B:SSL routines::wrong version number
What happens if you just use http:// with no ssl link?
- Trying 127.0.0.1:80…
- Connected to website.com (127.0.0.1) port 80 (#0)
GET / HTTP/1.1
Host: website.com
User-Agent: curl/7.81.0
Accept: /
- Mark bundle as not supporting multiuse
< HTTP/1.1 200 OK
< Date: Wed, 03 Jul 2024 02:37:32 GMT
< Server: Apache
< Last-Modified: Thu, 10 Dec 2020 18:24:10 GMT
< ETag: “2aa6-5b620483394b6”
< Accept-Ranges: bytes
< Content-Length: 10918
< Vary: Accept-Encoding
< Content-Type: text/html
May I suggest you read through the curl documentation: https://everything.curl.dev/index.html
Here should explain to you why you are getting the error with https://
Hello
Just installed WP Control Plugin on wordpress
and I got this message
There was a problem spawning a call to the WP-Cron system on your site. This means WP-Cron events on your site may not work. The problem was:
cURL error 35: error:0A00010B:SSL routines::wrong version number
More information
in More information link says:
cURL error 35: sslv3 alert handshake failure
This means there’s a problem with your HTTPS configuration. Your server cannot securely connect to itself.
I don’t know if this has anything to do with, I get his error in wordpress with the hostname = virtualservers name. I’ll try and fix to demonstrate as I write this.
This is the error when the are the same
Hostname is displayed here
If I add say server. to hostname
This check health of wordpress.
That error is gone
I do run have LetsEncrypt ssl installed, so maybe its not your issue.
No is not I tried this solution, but not working for me
Now it had changed, after Ubuntu upgrade from 20.04 to 22.04
Your server may not be able to connect to sites running on it. Error message: cURL error 35: error:0A00010B:SSL routines::wrong version number
OK finally solution to my problems 
I hope for now
I said : This means there’s a problem with your HTTPS configuration. Your server cannot securely connect to itself.
and that’s because my /etc/hosts file pointed to 127.0.0.1 address, but should be pointed to the address of the virtual server
Example:
Was
127.0.0.1 website.com
Solution
10.2.2.2 website.com
If you have a subdomain should be the same
Example:
127.0.0.1 localhost
10.2.2.2 website.com
10.2.2.2 subdomain.website.com
10.5.5.5 ubuntu-ip.website.com
If you have an url rerouted to 127.0.0.1 or any other loopback, this will fail the ssl handshake.
So this solve my problem. That’s how server can connect to itself. I think. I don’t know, but it works and I am happy. Thanks for your help
You should not name your system the same as a domain you’ll be hosting virtually in Virtualmin. This is documented in many places. This is one of a few reasons you shouldn’t do it, and why it’s documented you shouldn’t do it.
To quote the installation docs: “A fully qualified domain name is one of the form host.example.com, or simply example.com (but do not use a name you’ll be hosting in Virtualmin).”
This topic was automatically closed 8 days after the last reply. New replies are no longer allowed.