SSL not working after last update

[aSilentSniper]

Describe the bug
A clear and concise description of what the bug is.
After last update SSL is not working

To Reproduce
Steps to reproduce the behavior:
Enable SSL in Settings of adapter

Expected behavior
SSL should work

Screenshots & Logfiles

Versions:

• Adapter version: v6.1.2
• JS-Controller version: 5.0.12
• Node version: v18.17.1
• Operating system: Debian GNU/Linux 12 (bookworm

[Apollon77]

please tell more details about the added ssl ... own certificate? Letsencrpt? how created? ...... Anything in the adapter log?

[aSilentSniper]

I have tried it with either a self created from my PKI server and added as text in the Settings and with a Letsencrypt cert added as a path to a file in the settings. The same Certs are working in the admin adapter with no issues.
Unfortunately there is nothing in the log

Edit:

It is not a new cert it was working before the last update

[foxriver76]

what is last update? 6.1.1 to 6.1.2?

[aSilentSniper]

i update a soon as the webui tells me so i think so

[foxriver76]

hm there were two stable updates in the last time, I assume it is from the first one 4.3.0 -> 6.1.0 and the probably a problem with the new webserver/acme as also reported in admin.

[aSilentSniper]

Hmm possible but the same cert in admin is working fine

[Th0masKA]

Hey.

I have a similar problem:
I put a letsencryt-certificate (from the objects of the acme-adpater) in the system-settings of the iobroker (named 202302-Public and 202302-Private). If I choose this certificate in the web-adapter, the browser shows always the earlier and exprired letsencrypt-certifice. I deleted the old certificate in the iobroker settings, nevertheless the adapter uses this deleted certificate.

Where can I delete the used certificate manually, so the adapter gets the new one..?

Adapter version: v6.1.10
JS-Controller version: 5.0.16
Node version: v18.18.2
on a RaspberyPi 4

[Th0masKA]

Sorry for my post...

The acme-adapter got an update today to 0.1.2 and now the web-adapter uses the right certificate, because (or perhabs) the new acme-adpater deleted the exprired certificate from the collection in the opjects.

Did you plan to support the acme-certificates directly from the "objects-collection" in the web-adapter?