The proxy server could not handle the request

SYSTEM INFORMATION
OS type and version Debian 11
Webmin version 2.105
Virtualmin version 7.9.0

After trying to get a ssl certificate to a site I got this error:

Proxy Error

The proxy server could not handle the request
Reason: Error during SSL Handshake with remote server

After that I was able to get into Virtualmin with colon 10000. But it didn’t work as it should. On a new login attempt, the code from Authy was not accepted. So now I can’t get in at all with Virtualmin.

The CLI still works, but I’m no expert on it.
However, I saw in the /etc/webmin/miniserv.conf file that there were a number of extra lines at the end that shouldn’t be there. Have had similar problems once before when there were extra lines there. That time it was solved when I removed them, but not this time. Maybe something for the developers to look into.
Now I don’t know what the next step is. Where shall I look?
Thanks for any help I can get.

I don’t know what you’re trying to do or where you get that error.

Normally there would be no proxy involved in requesting certificate, so you’re going to have to be more specific about how you’re getting that error.

It just happened when I requested a Let’s encrypt certificate in the same way as I use to do. Nothing special with that.
I also checked the exact time but that didn’t help with Authy.

I didn’t ask when it happened.

You need to tell us what you’re doing to get this error, because there are no proxies involved in the usual case, so you are doing something I can’t figure out.

What does Authy have to do with anything?

What lines exactly were there that shouldn’t have been?

That was a previous problem. The current problem is not that (whatever that was).

I´m sorry @Joe but,

I still think that there is some connection with the error.
A “normal” miniserv.conf is 54L, 2068B
On the one having problems, it’s 123L, 9813B
It is not normal for a config file to be used as an intermediate storage for temporary data, is it?
By temporary data I mean e.g.:

ipkey_domain.com,.domain.com=/etc/ssl/virtualmin/1705588533711649/ssl.key
ipcert_domain.com,
.domain.com=/etc/ssl/virtualmin/1705588533711649/ssl.cert
ipkey_domain.com,.domain.com=/etc/ssl/virtualmin/1705694848873393/ssl.key
ipcert_domain.com,
.domain.com=/etc/ssl/virtualmin/1705694848873393/ssl.cert
ipextracas_domain.com,.domain.com=/etc/ssl/virtualmin/1705694848873393/ssl.ca
ipcert_domain.com,
.domain.com=/etc/ssl/virtualmin/1705695948887050/ssl.cert
ipkey_domain.com,.domain.com=/etc/ssl/virtualmin/1705695948887050/ssl.key
ipkey_domain.com,
.domain.com,domain.com,*.domain.com=/etc/ssl/virtualmin/1705695948887050/ssl.key

This isn’t a temporary data. These are expected lines for per-domain SSL certificate support in Webmin.

Please understand, if you want us to help you, you really need to provide more details about your configuration, what you’re doing (what you have tried), and what you’re aiming to achieve.

1 Like

You still haven’t told us where and how you get this error.

Again, there are no proxies involved in the usual case of requesting a certificate from Let’s Encrypt. I still have no idea what you’re trying to do, where it’s failing, or why. I can’t solve a problem if I can’t even figure out what the problem is.

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