The subject (problem) is that we all have internal administrative sites (like vsphere, Nutanix, IIS, SQL, etc) that have self-signed certs, protected by ACL/firewall/restricted access. But now with hardening of certs, browsers are increasingly not allowing access unless https has a valid cert.

I was going to start this post with a question about making EDGE bypass/accept self-signed or expired certificates, but I think I know the answer, “It won’t”. (If I am wrong, please tell me I would LOVE to know how).

But then I was reading in this forum, and got a good thought from a fellow user, “Stop teaching bad habits, and teach how to do it correctly.” This is a great idea. So now I have several different questions, especially since the CA’s are going to start forcing us to renew certs every 90 days.

Auto renewal seems like the way to go. Where do I even start? Does IIS support auto renewal for 3rd party CA’s like Comodo/Sectigo?

Does Tomcat support auto renewal for a windows CA or 3rd party?

What about 3rd party applications where the cert is integrated?

What should be looking up (researching keywords)?

Is there a better CA that does support auto-renewal?

Opinion: The complete removal of the ability to by pass the cert requirement is BULLS@#$. The very least Edge, Chrome , and others can do is make some admin level bypass so we can get our job done! so frusterating >:(

[No AI, Human generated]

7 Spice ups

To my recollection, the short answer is that yes, you can setup auto-renewal of certificates. Not sure this one is still relevant in general or to your specific situation, but may at least point you in the right general direction:
Renew Web Server (SSL) Certificates Automatically | Microsoft Community Hub

Another one that might be a little closer to your situation:
Can self-signed SSL certificate be renewed? How? - Super User

2 Spice ups

yes it’s a pain.
I recommend using an internal CA and automating this. powershell/shell script can be used to request new certs and install them.
If you can fully automate then set them to renew every 6 months with a 1 year validity and log errors.

Otherwise use a 5 year cert internally.

2 Spice ups

You can type in

thisisunsafe’ directly on the SSL warning page to bypass it (Chrome and Edge).

47 days by 2028.

Let’s encrypt are 90 days default.

ACME or Win-ACME will work, these support many 3rd parties that allow API requests, but why stop there, use LE (Let’s encrypt) and get free certificates.

For something a bit more GUI based, certifytheweb will do this, but it’s only free for (automating) 10 certs.

With an internal PKI you can also automate certificates, either by GPO and autorenew or using the aforementioned ACME tools.

3 Spice ups

I tries ‘thisisunsafe’ and it failed :frowning:

1 Spice up

I expect you’re not typing it in the right place or the warning is not the usual one.

If you can share a screenshot that might help, but you type that line, without spaces or quotes on the error page, make sure you’ve clicked on the page and just type it.

this is a workaround though, not a fix.

1 Spice up

yeah, i pray i am wrong, here it is

1 Spice up

The thisisunsafe should work on that screen, after clicking to expand the error, click somewhere on the screen between hide advanced, refresh and the writing below, then just type

thisisunsafe, no spaces, no caps etc. It should reload the page and take you in.

The only reason this may not work is if it’s public facing, behind a proxy server or filter of some kind that blocks nontrusted certs, in which case, whitelist the site and try again.

If this is an internal site, uses IPs but you do have a proxy, the proxy is still likely the cause. You have two options. Whitelist it and try again or add a DNS name to your AD for this resource and try again with the DNS name.

FYI, for internal sites, you would want to use an internal CA, not third party certs, while you can, unless the site is public facing, internal would be the recommended.

Proxies treat a period as a way to decide if a site is internal or external, IPs have many periods so proxies still try to filter these.

2 Spice ups

Still no joy. could there be a GPO deliberately blocking this?

1 Spice up

It is possible - you can check this via your browser

edge://policy/

Look for:

  • SSLErrorOverrideAllowed
  • SSLErrorOverrideAllowedForOrigins

If any are set to false, it’s blocked.

You can also test this by logging in as a local account, GPOs don’t apply here.

For Chrome

chrome://policy

2 Spice ups

The certificate management is only going to get more overwhelming when the total certificate lifespans drop to 39 days in 2029. I wish I had a typo in there, link for more info:

47 days, and that’s moved back another year, once more.

It was originally 2027, a few weeks ago it was 2028 and now 2029.

delaying it helps, but if it’s coming, it’s coming, it’s better to adapt now than wait until the last minute then scramble to sort it.

1 Spice up

Agree.

these are not set