Wild card SSL Let's encyrpt frontend problem

Hello guys,
I have Let's encrypt wild card (*.mydomain.com) cert. Today I'd renew it, put it in SafeLine MANUAL from frontend. Subdomains works ok and shows my cert, but SafeLine WAF stopped respond on https://myserver:9443. Tried to replace in nginx/cert/ files but no luck.
Now SL WAF interface shows me "ERR_SSL_VERSION_OR_CIPHER_MISMATCH"
When challange against localhost:443 I see my cert, but when check against 9443 (SL WAF forntend)

openssl s_client -connect localhost:9443 -showcerts
CONNECTED(00000003)
140240630338880:error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure:../ssl/record/rec_layer_s3.c:1552:SSL alert number 40
---
no peer certificate available
---
No client certificate CA names sent
---
SSL handshake has read 7 bytes and written 283 bytes
Verification: OK
---
New, (NONE), Cipher is (NONE)
Secure Renegotiation IS NOT supported
Compression: NONE
Expansion: NONE
No ALPN negotiated
Early data was not sent
Verify return code: 0 (ok)
---

Respectively

curl -k -f https://localhost:1443/api/open/health
curl: (7) Failed to connect to localhost port 1443: Connection refused`
Can somebody help ?

you can update SafeLine cert here and you should curl -k https://localhost:9443/api/open/health instead of 1443

try this docker exec safeline-pg psql -U safeline-ce -c "delete from mgt_options where key = 'mgt_cert';" && docker restart safeline-mgt

could you try recreate safeline-mgt?
docker rm -f safeline-mgt && docker compose up -d in install dir

Yes, that works !
curl -k https://localhost:9443/api/open/health
{"status":"ok"}
But still SSL warnging exists. That's (the original cert I suppose) is it:

you can update SafeLine cert here

Mine UI is a little bit different older version LTS I suppose but when change here (attached) with mine cert .... same problem appear again. Already know how to resolve that but though is not OK ?

could you provide your cert?

i request a wildcard cert by letsencrypt and access SafeLine 9443 port, all work good

Alternatively, you can proxy the WAF console to avoid this issue.