Admin does not use let's encrypt certificate collection from acme

[dklinger]

Describe the bug
Not sure if it is live yet or not. But the certificate process via ioBroker.acme seems not work yet. I can aquire the certificates via acme adapter and also select it in the Admin adapter. But when opening admin instance, it's showing me a certificate error and, when checking the certificate, it's shown a self-signed one, created by ioBroker.

To Reproduce
Steps to reproduce the behavior:

1. Configure acme adapater to retrieve certificates
2. Select collection in Admin adapter
3. Try to open Admin instance

Expected behavior
Admin page opening with the certificate which was aquired by acme adapter.

Screenshots & Logfiles

Versions:

• Adapter version: 6.4.3
• JS-Controller version: 4.0.24
• Node version: v18.16.0
• Operating system: docker - buanet

[Apollon77]

For Acme and the new certificate logic you need js-controller 5!

[dklinger]

Darn - that's good to know :D
Thanks!

[peterbaumert]

I have js-controller 5.0.6 and have the same issue.

2023-07-03 21:09:27.918 - error: admin.0 (1394527) Cannot configure secure web server, because no certificates found: , ,

strange thing is this error comes before:

2023-07-03 21:09:28.669  - debug: admin.0 (1551271) Loaded custom certificates: {"key":"-----BEGIN RSA PRIVATE KEY-----\

[dklinger]

I am now on below verions and it is still loading the ioBroker GmbH certificate.

Adapter version: 6.10.1
JS-Controller version: 5.0.12
Node version: v18.17.1
Operating system: docker - buanet

[dklinger]

I have setup 2 collections and ACME shows status "OK" for both. I have tried selecting both of them in the Admin adapter, with fallback certificates set to none.

[mcm1957]

@foxriver76
Could you üplease check / comment if this is still a problem?
The issue was created at april - several new release of admin / web and js-controller are out in the meantime.

[dklinger]

@foxriver76
Yes, I checked 1-2 weeks ago after I've updated to the v5 JS controller. It still did not work. Let me gather a few details and update the thread.

[dklinger]

@foxriver76
Admin is still always providing the ioBroker-cert:

As stated above:
Adapter version: 6.10.1
JS-Controller version: 5.0.12
Node version: v18.17.1
Operating system: docker - buanet

ACME-Status:

The ACME-Collection is selected in the Admin-Adapter at the first tab in the picklist "Let's Encrypt".

[mcm1957]

siehe auch:
https://forum.iobroker.net/topic/68286/acme-letsencrypt-zertifikate-auch-f%C3%BCr-web-adapter/4

Wobei es divergierende Aussagen gibt ob das hilft oder nicht

[dklinger]

Nope, hilft leider nicht.
Wobei ich das Problem auch und primär mit dem Admin-Adapter habe.

[aSilentSniper]

Es hilft nichts weder im Admin noch im Web bekomme ich die ACME certs zum laufen auch nach lesen aller tips hier.

[peterbaumert]

Ja geht bei mir auch nicht. Mein issue wurde leider geschlossen.

[TA2k]

Auch bei mir war die einzige Lösung revert

admin auf v6.7.0
web auf v5.5.3

Dann geht alles normal ohne acme und update der certificate

[aSilentSniper]

Naja das kann ja keine lösung sein was sagen die Entwickler dazu? @GermanBluefox

[mcm1957]

Naja das kann ja keine lösung sein was sagen die Entwickler dazu?
@Apollon77 @foxriver76

[aSilentSniper]

Schade das seit einem Monat da nichts zu gesagt wird

[mcm1957]

@Apollon77 @foxriver76 @bluefox

[foxriver76]

Unfortunately I have no touching point with this functionality currently. We had a fix one month ago ioBroker/webserver@2355c34 but this is already included in the current admin stable. So if someone which has a setup with public domain could look into this, would be much appreciated.

[dklinger]

Works with latest version of acme adapter (0.1.2).