You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
My problem is that I have a webserver (from my router) that only accepts certificates/privates keys that are generated via RSA. It also contains a self-generated certificate. I was hoping to fully ignore the webservers certificate because I have the proxy manager, but whatever I try to change at the config, the proxy manager forwards the certificate from my router.
Describe the solution you'd like
It would resolve the issue if you could discard the certificate of the underlying host. Also it would be great to have the option to go back to RSA. I tried to change the letsencrypt.ini file without success.
Describe alternatives you've considered
An alternative would be to create the certificate manually and upload it but that isn't practical because they expire every 90 days.
Additional context
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
My problem is that I have a webserver (from my router) that only accepts certificates/privates keys that are generated via RSA. It also contains a self-generated certificate. I was hoping to fully ignore the webservers certificate because I have the proxy manager, but whatever I try to change at the config, the proxy manager forwards the certificate from my router.
Describe the solution you'd like
It would resolve the issue if you could discard the certificate of the underlying host. Also it would be great to have the option to go back to RSA. I tried to change the
letsencrypt.ini
file without success.Describe alternatives you've considered
An alternative would be to create the certificate manually and upload it but that isn't practical because they expire every 90 days.
Additional context
The text was updated successfully, but these errors were encountered: