nginx emergency error about the size of shared memory zone "SSL" conflict

[leolivier]

Checklist

• Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image?
  • Yes
• Are you sure you're not using someone else's docker image?
  • Yes
• Have you searched for similar issues (both open and closed)?
  • Yes

Describe the bug
As I was blocked by the issue #4439 , I tried a workaround. I created a wildcard certificate using my DNS provider (IONOS) and it worked. But when I tried to assign this new cert to one of my subdomain instead of the one for which I am blocked on #4439, the proxy went offline with no error and no trace. The xx.conf file has disappeared. So I looked at the database content and I see an error, table proxy_host, column meta, on the row related to my proxy (reformated for readability):

{
  "letsencrypt_agree": false,
  "dns_challenge": false,
  "nginx_online": false,
  "nginx_err": "nginx: [emerg] the size 52428800 of shared memory zone \"SSL\" conflicts with already declared size 10485760 in /etc/nginx/conf.d/include/ssl-cache.conf:2\nnginx: configuration file /etc/nginx/nginx.conf test failed\n"
}

Nginx Proxy Manager Version
v2.12.3

To Reproduce
Steps to reproduce the behavior:

1. Create a standard certificate for one subdomain
2. Create a proxy_host for that subdomain and link to the above cert
3. DO the same for several subdomains with the same cert
4. Create a wildcard certificate for the domain
5. Assign the new certificate to one of the subdomains
6. See site go offline and xx.conf file disappear and error in the database

Operating System
RPI5

Additional context
After that I tried to remove the proxy, remove the wildcard cert then recreate the proxy : still the same error. Even worth, I tried to make a small change not related to certs to another of the subdomain and I have the same issue with that subdomain: site down, xx.conf disappeared.
I found a workaround by recreating the two lost xx.conf files by copying another one and just changing the server name, port and log files and reloaded nginx using docker exec and it worked, the sites are reachable but the error remains in the UI and the database
EDIT: nginx -t shows no error:

[root@docker-6effe8a06f6c:/app]# nginx -t
nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
nginx: configuration file /etc/nginx/nginx.conf test is successful

[leolivier]

Sorry, my bad, I found the culprit.
In another very specific proxy (SSL managed by the proxied container) I had added the ssl_session_cache shared:SSL:10m; configuration line. Removing it solved the issue