Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - cobbers83

#1
Following. After this latest update, 2 hot fixes, and a manually kernel patch, my internet is doing the same thing. I'm pulling my hair out. I see no red flags in the logs. Argh!
#2
This still isn't working for me. It's maddening. I've tried everything I can think of.

I am on Acme Plugin 4.1. I am running Synology DSM 7.2.1-69057 Update 5.

I have OTP enabled and got the Device ID (did) from the cookie in an Incognito window. I set the Device Name to 'CertRenewal" (I just made that up. Not sure if/where I am supposed to get that value or if I just set it to whatever I want.)

I even tried setting up a user WITHOUT an OTP and it still won't authenticate to Synology.

The cert is properly generated in Acme, but the only thing not working is deploying it to my Synology.

For the record, I use a custom domain and custom port for my synology, if that matters.

Does anyone have any other things I could try? Here is what the logs say.

Screenshot: https://share.jacobgraf.com/TtTMcBmwLjVT9kqL0Fcl
#3
Good news! Looks like the fix is out in Acme Client 3.20! 🎉

https://github.com/opnsense/plugins/blob/stable/23.7/security/acme-client/pkg-descr

Fixed:
* fix 2FA support in Synology automation (#3627)
#4
Any updates on this? I've tried to manually edit the config and still can't getting it to work. I'm hoping a first-party update is on the way? In the meantime, is there a way to downgrade to the working version or any other methods to get my Synology SSL certs updated in the meantime?