-
-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deploy synology_dsm.sh - Error 109 (was succeed 2 months ago) #5191
Comments
Please upgrade to the latest code and try again first. Maybe it's already fixed. |
Well... trying to get the level 3 debug logs, I ran this command: And the deployment.... Has succeeded.... without changing anything.....
Any clue why I had this 119 error message? |
According to the official doc of Login Web API, 119 means "Invalid session", don't know how it can happen, and since either you can't reproduce this issue, we won't be able to identify the reason to help. |
You need 2FA for the Synology-ACME-Admin-User? I think it's a 2FA problem. |
Well 2FA is needed when you activate it on your Synology, I dont think it relates to the admin account. |
Don't just give up. Required for the import acme.sh a user account with administrator rights, not without the admin or adminuser. It is best to test the import without 2FA. There should be no $ sign in password. If this works, you can test the 2FA again. The 2FA has often caused problems in the near past. Giving up and not using acme is not an option ;) |
Yes the acme is on docker so no rights problem. So I do not give up using acme, I just give up investigating this issue 😅 |
Do you use acme as a deamon? With this, the update works automatically, without an extra task or command. I have already set up acme on the DS for many users, and they have been running for over 2 years without any problems. There were only problems with 2FA. How did you install acme ssh/task or compose? How was the order? Install via Docker/Container Manager (task not needet by deamon - its wrong) |
Hello all!
I just realized that my certificate has not been newed few weeks ago. After checking the logs, I saw a deployment issue:
I checked the synology_dsm.sh file, and the issue seems to be here:
I saw there has been a modification on this file 2 month ago... What's surprising is that I normally configured the acme not to be updated automatically.... So I do not understand why I received the updates.
Thanks in advance for your help (I am a real beginner in Docker... So if some can tell me how to download the certificates so I'll update them manually with the DSM interface).
FYI: the Acme is running on a docker (neilpang one) on a Synology. Previous logs in mid april were:
The text was updated successfully, but these errors were encountered: