Recently, it seems aaPanel triggered a bug and failed to renew the certificate for the panel domain. I had to renew it manually, but after that aaPanel started sending a daily email with the following: #### SSL Certificate expiration >Server:aaPanel Linux panel >IPAddress: 8x.1xx.5x.xxx(Internet) 8x.1xx.5x.xxx(Internal) >SendingTime: 2026-04-14 15:58:27 > Domain SSL ['p.mydomain.com'] certificate expired if(window.hljsLoader && !document.currentScript.parentNode.hasAttribute('data-s9e-livepreview-onupdate')) { window.hljsLoader.highlightBlocks(document.currentScript.parentNode); } And now, instead of two, there is a third certificate here: My two domains—the main website and the panel—seem fine, but a third certificate near expiration is also being shown. I don’t know where it came from. I’ve deleted it twice, but something in the panel keeps putting it back. The CRON log is also showing three certificates, with one of them returning an error: My concern is that the certificate nearing expiration might be the one actually used by aaPanel. If that’s the case, I could soon lose access to the panel—even though under “Website” everything appears fine.

Issue with SSL certificates

Nanno

Recently, it seems aaPanel triggered a bug and failed to renew the certificate for the panel domain. I had to renew it manually, but after that aaPanel started sending a daily email with the following:

#### SSL Certificate expiration
>Server:aaPanel Linux panel
>IPAddress: 8x.1xx.5x.xxx(Internet) 8x.1xx.5x.xxx(Internal)
>SendingTime: 2026-04-14 15:58:27
> Domain SSL ['p.mydomain.com'] certificate expired

And now, instead of two, there is a third certificate here:

My two domains—the main website and the panel—seem fine, but a third certificate near expiration is also being shown. I don’t know where it came from. I’ve deleted it twice, but something in the panel keeps putting it back.

The CRON log is also showing three certificates, with one of them returning an error:

My concern is that the certificate nearing expiration might be the one actually used by aaPanel. If that’s the case, I could soon lose access to the panel—even though under “Website” everything appears fine.

aaPanel_Kern

Hi, can you give us your aaPanel information? The server makes a snapshot backup first, if possible, please send it to kern@aapanel.com.
It is recommended to fill in the following
Post link:
SSH IP address, account password and port:
aaPanel login link address and account password:
Detailed problem description:

No post link will not be able to know which user's information is, and the problem will not be processed

Nanno

aaPanel_Kern

I cannot provide the login details for SSH because login with a password is disabled because the continuous attempts of hacking, but I can collect the information you may need and send by email.

aaPanel_Kern

Nanno
Hi, can you give us your aaPanel information? The server makes a snapshot backup first, if possible, please send it to kern@aapanel.com.
It is recommended to fill in the following
Post link:
aaPanel login link address and account password:
Detailed problem description:

No post link will not be able to know which user's information is, and the problem will not be processed

Nanno

aaPanel_Kern

I spent a time investigating the issue and I confirmed the aaPanel very likely was binded to the certificate near expiration.

There is a bug somewhere at aaPanel 8.0.1. Seems the SSL certificate applied through "Website -> panel domain -> SSL" is not the same as the one applied through "Settings -> Panel SSL -> Modify".
That seems a classical bug: two paths to do the same task, but each one have a different behavior, and they are not compatible with each other. It is better to have only one way to do each task.

I applied to a new Let's Encrypt SSL certificate under "Settings -> Panel SSL -> Modify". Looks like it worked.
I will monitor to see if it repeats in 60 days, when the expiration approaches.