# Let's Encrypt 6 day certs

**URL:** <https://forum.virtualmin.com/t/lets-encrypt-6-day-certs/133025>\
**Category:** Third Party News\
**Created:** [April 14, 2025, 12:46pm UTC](https://forum.virtualmin.com/t/lets-encrypt-6-day-certs/133025 "2025-04-14T12:46:12Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![ID10T](https://cdn.forum.virtualmin.com/user_avatar/forum.virtualmin.com/id10t/32/7895_2.png) [@ID10T](https://forum.virtualmin.com/u/ID10T)\
**Post date:** [April 14, 2025, 12:46pm UTC](https://forum.virtualmin.com/t/lets-encrypt-6-day-certs/133025/1 "2025-04-14T12:46:12Z")

</div>

Shorter is better I guess?

> **[Certbot 4.0: Long Live Short-Lived Certs!](https://www.eff.org/deeplinks/2025/04/certbot-40-long-live-short-lived-certs)**
>
> When Let’s Encrypt, a free certificate authority, started issuing 90 day TLS certificates for websites, it was considered a bold move that helped push the ecosystem towards shorter certificate life times. Beforehand, certificate authorities normally...

> **[Announcing Six Day and IP Address Certificate Options in 2025](https://letsencrypt.org/2025/01/16/6-day-and-ip-certs/)**
>
> This year we will continue to pursue our commitment to improving the security of the Web PKI by introducing the option to get certificates with six-day lifetimes (“short-lived certificates”). We will also add support for IP addresses in addition to...

EDIT: I guess this is one reason they abandoned the expiration notices emails?

---

<div class="post-metadata">

**Author:** ![Joe](https://cdn.forum.virtualmin.com/user_avatar/forum.virtualmin.com/joe/32/9_2.png) [@Joe](https://forum.virtualmin.com/u/Joe)\
**Post date:** [April 14, 2025, 10:51pm UTC](https://forum.virtualmin.com/t/lets-encrypt-6-day-certs/133025/2 "2025-04-14T22:51:34Z")

</div>

The IP address certificate is far more interesting for Virtualmin.

We do a crazy and confusing dance where we try to auto-create a Virtual Server in order to fetch a cert for the hostname of the system if it resolves just to avoid the browser error right after installation. Being able to get one for the IP would solve that more reliably. IP-based certs are stupid and a bad idea in almost every case, except this specific one. Having it only last a few days is even better, because I don’t want anyone getting in the habit of using the IP (or the hostname) to talk to the system…once you have Virtual Servers with certs, you can use any of those. With an IP-based cert, we don’t even need the user to have working DNS for anything (the system hostname or whatever) for them to be able to log in to Virtualmin the first time without a browser error.

---

<div class="post-metadata">

**Author:** ![Ilia](https://cdn.forum.virtualmin.com/user_avatar/forum.virtualmin.com/ilia/32/10185_2.png) [@Ilia](https://forum.virtualmin.com/u/Ilia)\
**Post date:** [April 15, 2025, 10:19am UTC](https://forum.virtualmin.com/t/lets-encrypt-6-day-certs/133025/3 "2025-04-15T10:19:41Z")

</div>

> [@Joe](#):
>
> Having it only last a few days is even better, because I don’t want anyone getting in the habit of using the IP (or the hostname) to talk to the system.

As for having it last just a couple of days—that confuses a lot of users. And if the idea is generally bad in the first place, we shouldn’t do it at all, even with exceptions. The hostname-based cert works well right now, and currently I don’t see a good reason to invest more time in setting up IP-based SSL, especially if it only lasts a few days.

Yet, it could technically serve as a fallback feature if the hostname SSL cert request fails, but it’d be a _pretty complex_ one to implement!

> Because I don’t want anyone getting in the habit of using the IP (or the hostname) to talk to the system.

The main reason we eventually decided to automate support for hostname SSL is because people were/are actively using them—and **will keep** using them—regardless of what we (or anyone else) advocate for or think is the “right” way. If that weren’t the case, this feature wouldn’t exist at all.

> With an IP-based cert, we don’t even need the user to have working DNS for anything (the system hostname or whatever) for them to be able to log in to Virtualmin the first time without a browser error.

I wouldn’t mind automating this, but it needs to be clear and confusion-free. If we set up an IP-based cert, it could be for shortened or a standard duration, _but_ with scheduled renewals. We’d also need to monitor and update it whenever the IP(s) changes. Keep in mind that a host might have four or more IPs, potentially a mix of IPv4 and IPv6, and **all of this** would need to be automated to make it a practical and smooth feature.

Generally, I’m not eager to spend time implementing this, but I wouldn’t oppose it either. However, removing the existing feature that creates an SSL cert for the hostname wouldn’t be wise—people are using it, and trying to change that would have any practical benefits and only cause confusion and frustration.

Talking of improvements—I just made a small tweak—the post-install message won’t show the IP:10000 link anymore if the SSL certificate for the hostname was set up successfully. We can bring it back if we ever decide to support IP-based certs—or for example, when the hostname SSL request fails.

@Jamie, also, I’m considering updating the Virtualmin installer to have Webmin also listen on port 8443 if the hostname’s nameservers point to Cloudflare. What are your thoughts on this?

---

<div class="post-metadata">

**Author:** ![Jamie](https://cdn.forum.virtualmin.com/user_avatar/forum.virtualmin.com/jamie/32/8589_2.png) [@Jamie](https://forum.virtualmin.com/u/Jamie)\
**Post date:** [April 15, 2025, 6:29pm UTC](https://forum.virtualmin.com/t/lets-encrypt-6-day-certs/133025/4 "2025-04-15T18:29:02Z")

</div>

> [@Ilia](#):
>
> As for having it last just a couple of days—that confuses a lot of users. And if the idea is generally bad in the first place, we shouldn’t do it at all, even with exceptions. The hostname-based cert works well right now, and currently I don’t see a good reason to invest more time in setting up IP-based SSL, especially if it only lasts a few days.

I didn’t actually know that IP based certs existed until now! But I can see how they could be useful for new installs to avoid the complexity of the default hostname. I will take a look to see how complex this would be to implement..

> [@Ilia](#):
>
> @Jamie, also, I’m considering updating the Virtualmin installer to have Webmin also listen on port 8443 if the hostname’s nameservers point to Cloudflare. What are your thoughts on this?

We could just do that for all installs. What’s special about port 8443 though?

---

<div class="post-metadata">

**Author:** ![shoulders](https://cdn.forum.virtualmin.com/user_avatar/forum.virtualmin.com/shoulders/32/10086_2.png) [@shoulders](https://forum.virtualmin.com/u/shoulders)\
**Post date:** [April 15, 2025, 6:47pm UTC](https://forum.virtualmin.com/t/lets-encrypt-6-day-certs/133025/5 "2025-04-15T18:47:26Z")

</div>

There is also the cpanel ports that might be useful. Just an idea. I don’t know if they are passed through with cloudflare

---

<div class="post-metadata">

**Author:** ![Joe](https://cdn.forum.virtualmin.com/user_avatar/forum.virtualmin.com/joe/32/9_2.png) [@Joe](https://forum.virtualmin.com/u/Joe)\
**Post date:** [April 15, 2025, 7:02pm UTC](https://forum.virtualmin.com/t/lets-encrypt-6-day-certs/133025/6 "2025-04-15T19:02:32Z")

</div>

Cloudflare only proxies for a handful of ports, and 8443 is one of them. 10000 doesn’t work for a Cloudflare address.

---

<div class="post-metadata">

**Author:** ![Ilia](https://cdn.forum.virtualmin.com/user_avatar/forum.virtualmin.com/ilia/32/10185_2.png) [@Ilia](https://forum.virtualmin.com/u/Ilia)\
**Post date:** [April 15, 2025, 7:05pm UTC](https://forum.virtualmin.com/t/lets-encrypt-6-day-certs/133025/7 "2025-04-15T19:05:23Z")

</div>

> [@Jamie](#):
>
> I didn’t actually know that IP based certs existed until now!

ZeroSSL has had this feature for years.

> [@Jamie](#):
>
> But I can see how they could be useful for new installs to avoid the complexity of the default hostname.

It’s not only about complexity; it’s about what people would do or expect, regardless of any recommendations. Practice has clearly proven it.

Also, getting it to work smoothly for IP addresses isn’t easy. We’d need to handle all public IPs on the system—which could mean dozens of IPv4s and, eventually, IPv6 too (though they don’t support IPv6 yet). Plus, we’d have to keep track of any new IPs being added or removed.

And, according to Let’s Encrypt, it will always be a short-lived certs—just 6 days. ZeroSSL, on the other hand, gives you 90 days—we’d need to support both and maybe plan for other SSL providers too, each with **their own** profiles and rules.

I don’t see it to be easy if done thoroughly.

> [@Jamie](#):
>
> We could just do that for all installs. What’s special about port 8443 though?

If Cloudflare proxying is turned on, it only allows certain ports—mainly standard web ones. So `my.hostname.tld:10000` won’t work, but `my.hostname.tld:8443` will. That’s just because Cloudflare blocks most other ports when proxying.

---

<div class="post-metadata">

**Author:** ![Ilia](https://cdn.forum.virtualmin.com/user_avatar/forum.virtualmin.com/ilia/32/10185_2.png) [@Ilia](https://forum.virtualmin.com/u/Ilia)\
**Post date:** [April 15, 2025, 7:06pm UTC](https://forum.virtualmin.com/t/lets-encrypt-6-day-certs/133025/8 "2025-04-15T19:06:59Z")

</div>

> [@shoulders](#):
>
> There is also the cpanel ports that might be useful.

We obviously won’t use those!

---

<div class="post-metadata">

**Author:** ![Jamie](https://cdn.forum.virtualmin.com/user_avatar/forum.virtualmin.com/jamie/32/8589_2.png) [@Jamie](https://forum.virtualmin.com/u/Jamie)\
**Post date:** [April 15, 2025, 11:56pm UTC](https://forum.virtualmin.com/t/lets-encrypt-6-day-certs/133025/9 "2025-04-15T23:56:09Z")

</div>

> [@Ilia](#):
>
> If Cloudflare proxying is turned on, it only allows certain ports—mainly standard web ones. So `my.hostname.tld:10000` won’t work, but `my.hostname.tld:8443` will. That’s just because Cloudflare blocks most other ports when proxying.

Seems like there’s no downside to listening on this port then.

---

<div class="post-metadata">

**Author:** ![Jamie](https://cdn.forum.virtualmin.com/user_avatar/forum.virtualmin.com/jamie/32/8589_2.png) [@Jamie](https://forum.virtualmin.com/u/Jamie)\
**Post date:** [April 15, 2025, 11:59pm UTC](https://forum.virtualmin.com/t/lets-encrypt-6-day-certs/133025/10 "2025-04-15T23:59:36Z")

</div>

> [@Ilia](#):
>
> It’s not only about complexity; it’s about what people would do or expect, regardless of any recommendations. Practice has clearly proven it.

I think it’s useful only in the case where the admin is connecting to Virtualmin using an IP address. I would agree that this is pretty low priority though…

---

<div class="post-metadata">

**Author:** ![Linulex](https://cdn.forum.virtualmin.com/letter_avatar_proxy/v4/letter/l/dc4da7/32.png) [@Linulex](https://forum.virtualmin.com/u/Linulex)\
**Post date:** [April 18, 2025, 10:37pm UTC](https://forum.virtualmin.com/t/lets-encrypt-6-day-certs/133025/11 "2025-04-18T22:37:27Z")

</div>

8443 is the Plesk port.

> **[Ports Used by Plesk](https://docs.plesk.com/en-US/obsidian/administrator-guide/plesk-administration/ports-used-by-plesk.64950/)**
>
> For Plesk and its services to work correctly, certain ports must not be blocked.

| Service name | Ports used by service |
| --- | --- |
| Administrative interface of Plesk over HTTPS | TCP 8443, UDP 8443 |

regards  
Jan

---

<div class="post-metadata">

**Author:** ![Pixilpix\_Ltd\_Trading](https://cdn.forum.virtualmin.com/letter_avatar_proxy/v4/letter/p/91b2a8/32.png) [@Pixilpix\_Ltd\_Trading](https://forum.virtualmin.com/u/Pixilpix_Ltd_Trading)\
**Post date:** [April 20, 2025, 7:56am UTC](https://forum.virtualmin.com/t/lets-encrypt-6-day-certs/133025/12 "2025-04-20T07:56:40Z")

</div>

**Just a quick point to consider for Virtualmin setups:**  
Many users start out with **Cloudflare’s free plan** when setting up their servers. Since the free plan **does not support proxying port 8443** , Cloudflare’s Free Plan supports ports—such as **2096** , **2083** , or **2087**.

---

<div class="post-metadata">

**Author:** ![Ilia](https://cdn.forum.virtualmin.com/user_avatar/forum.virtualmin.com/ilia/32/10185_2.png) [@Ilia](https://forum.virtualmin.com/u/Ilia)\
**Post date:** [April 20, 2025, 8:22pm UTC](https://forum.virtualmin.com/t/lets-encrypt-6-day-certs/133025/13 "2025-04-20T20:22:28Z")

</div>

> [@Pixilpix\_Ltd\_Trading](#):
>
> Since the free plan **does not support proxying port 8443**

The free plan of Cloudflare supports port `8080`, just like `8443`.

> [@Linulex](#):
>
> 8443 is the Plesk port.

Ports `8080` and `8443` are alternative (`http-alt` and `https-alt`) ports—not exclusive to Plesk, just ones they wisely chose to use.

> **[Service Name and Transport Protocol Port Number Registry](https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml?search=8080)**

If we choose to listen on an additional port, it will be either `8080` or `8443`.

---

<div class="post-metadata">

**Author:** ![Pixilpix\_Ltd\_Trading](https://cdn.forum.virtualmin.com/letter_avatar_proxy/v4/letter/p/91b2a8/32.png) [@Pixilpix\_Ltd\_Trading](https://forum.virtualmin.com/u/Pixilpix_Ltd_Trading)\
**Post date:** [April 20, 2025, 11:45pm UTC](https://forum.virtualmin.com/t/lets-encrypt-6-day-certs/133025/14 "2025-04-20T23:45:31Z")

</div>

Thanks Ilia, as you have stated - should have checked the source of truth 🙂.

Here are the Cloudflare details :

> **[Network ports · Cloudflare Fundamentals docs](https://developers.cloudflare.com/fundamentals/reference/network-ports/)**
>
> Learn which network ports Cloudflare proxies by default and how to enable Cloudflare's proxy for additional ports.

Network ports compatible with Cloudflare’s proxy

By default, Cloudflare proxies traffic destined for the HTTP/HTTPS ports listed below.

HTTP ports supported by Cloudflare

```
80
8080
8880
2052
2082
2086
2095

```

HTTPS ports supported by Cloudflare

```
443
2053
2083
2087
2096
8443

```

Ports supported by Cloudflare, but with caching disabled

```
2052
2053
2082
2083
2086
2087
2095
2096
8880
8443

```

---

<div class="post-metadata">

**Author:** ![Linulex](https://cdn.forum.virtualmin.com/letter_avatar_proxy/v4/letter/l/dc4da7/32.png) [@Linulex](https://forum.virtualmin.com/u/Linulex)\
**Post date:** [April 21, 2025, 7:42am UTC](https://forum.virtualmin.com/t/lets-encrypt-6-day-certs/133025/15 "2025-04-21T07:42:09Z")

</div>

> [@shoulders](#):
>
> cpanel

cpanel ports are also not official assigned to cpanel  
2083 = radsec

> **[Service Name and Transport Protocol Port Number Registry](https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml?search=2083)**

8443 = pcsync-https, not https-alt

> **[Service Name and Transport Protocol Port Number Registry](https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml?search=8443)**

Plesk has been using ports 8443 from its very beginning in summer 2001

cpanel is more used us the US while plesk is more used in Europe. If you won’t use the cpanel ports then the same reasoning should apply to the plesk ports.

If you plan to use port 8443 only in virtualmin, then go ahead. I doubt that many people will have both plesk and virtualmin on the same server.

But if you also plan to use it in webmin then you will create problems for all the people that use plesk as customer interface and webmin as server configuration tool.

regards  
Jan

---

<div class="post-metadata">

**Author:** ![Ilia](https://cdn.forum.virtualmin.com/user_avatar/forum.virtualmin.com/ilia/32/10185_2.png) [@Ilia](https://forum.virtualmin.com/u/Ilia)\
**Post date:** [April 21, 2025, 11:03am UTC](https://forum.virtualmin.com/t/lets-encrypt-6-day-certs/133025/16 "2025-04-21T11:03:46Z")

</div>

> [@Linulex](#):
>
> If you plan to use port 8443 only in virtualmin, then go ahead. I doubt that many people will have both plesk and virtualmin on the same server.
> 
> But if you also plan to use it in webmin then you will create problems for all the people that use plesk as customer interface and webmin as server configuration tool.

Yeah, we’d only set Webmin to use port 8443 during the Virtualmin post-install setup—and only if the hostname is using Cloudflare nameservers.

---

<div class="post-metadata">

**Author:** ![jimr1](https://cdn.forum.virtualmin.com/user_avatar/forum.virtualmin.com/jimr1/32/14173_2.png) [@jimr1](https://forum.virtualmin.com/u/jimr1)\
**Post date:** [April 21, 2025, 2:16pm UTC](https://forum.virtualmin.com/t/lets-encrypt-6-day-certs/133025/17 "2025-04-21T14:16:10Z")

</div>

> [@Linulex](#):
>
> if you also plan to use it in webmin

Webmin and virtualmin use the same port as virtualmin is a module of webmin, so just change the webmin port and everything will work

---

<div class="post-metadata">

**Author:** ![ID10T](https://cdn.forum.virtualmin.com/user_avatar/forum.virtualmin.com/id10t/32/7895_2.png) [@ID10T](https://forum.virtualmin.com/u/ID10T)\
**Post date:** [April 21, 2025, 2:58pm UTC](https://forum.virtualmin.com/t/lets-encrypt-6-day-certs/133025/18 "2025-04-21T14:58:16Z")

</div>

> [@jimr1](#):
>
> Webmin and virtualmin use the same port

Not sure how this affects the conversation but it is easy to forget. Never really knew the ‘why’ of the range.  
 ![image](https://cdn.forum.virtualmin.com/uploads/default/original/3X/d/e/de561f79c383864a58ea64688f09c78fe6c114b7.png)

---

<div class="post-metadata">

**Author:** ![Ilia](https://cdn.forum.virtualmin.com/user_avatar/forum.virtualmin.com/ilia/32/10185_2.png) [@Ilia](https://forum.virtualmin.com/u/Ilia)\
**Post date:** [April 21, 2025, 6:53pm UTC](https://forum.virtualmin.com/t/lets-encrypt-6-day-certs/133025/19 "2025-04-21T18:53:57Z")

</div>

> [@ID10T](#):
>
> Not sure how this affects the conversation but it is easy to forget. Never really knew the ‘why’ of the range.  
> ![image](https://cdn.forum.virtualmin.com/uploads/default/original/3X/d/e/de561f79c383864a58ea64688f09c78fe6c114b7.png)

The range is meant for possible use in RPC calls, using the current Webmin port (i.e. default 10000) plus up to 100 additional ports.

> **[Webmin Servers Index](https://webmin.com/docs/modules/webmin-servers-index/#how-rpc-works)**
>
> About This module really serves two purposes, one simple and one quite complex. You can use it to create a master index of other systems running Webmin on your network, each of which is shown as an icon that you can click on to link to the server....

---

<div class="post-metadata">

**Author:** ![ID10T](https://cdn.forum.virtualmin.com/user_avatar/forum.virtualmin.com/id10t/32/7895_2.png) [@ID10T](https://forum.virtualmin.com/u/ID10T)\
**Post date:** [April 21, 2025, 9:31pm UTC](https://forum.virtualmin.com/t/lets-encrypt-6-day-certs/133025/20 "2025-04-21T21:31:26Z")

</div>

OK. Partially I didn’t want folks to forget there is a range even if it doesn’t affect this application of it.

[Next page](https://forum.virtualmin.com/t/lets-encrypt-6-day-certs/133025.md?page=2)
