-
-
Notifications
You must be signed in to change notification settings - Fork 5.1k
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 error synology_dsm Failed to authenticate with error: 102. #5184
Comments
Please upgrade to the latest code and try again first. Maybe it's already fixed. |
This is already the latest version and the log is already provided. |
i am experiencing exact same issue with same log |
pls provide the log with |
./acme.sh --deploy --home . -d <hidden_site> --deploy-hook synology_dsm --ecc --debug 3 |
What is the version of your DSM system? According to the official doc of Login Web API, |
Thanks for your reply. I'm using DSM 6.2.4-25556 Update 7. How can I check if the API is installed? If it's not installed, where can I find and install it? |
@webcusp Use your browser to check if the following URL can be used to authorize (replace user/passwd): |
Response: {"error":{"code":400},"success":false} |
@webcusp Replace your synology_dsm.sh file to: |
Load file /usr/local/share/acme.sh/deploy/synology_dsm.sh error. Please check your api file and try again. |
Are you referring to updating a local repo with changes from GitHub repo? |
Execute:
|
Ah. I did it this way, |
You fetched the whole github html page, rather than the source file... |
My bad. I'm hitting "Unable to update certificate, got error response: {"error":{"code":5598},"success":false}." Is this an error on my side? Wondering. |
It's not a related issue, you should search related issues or google it or file a new issue if you still can't resolve it. |
This error was caused by incompatible certificates. acme.sh got the ECC certificate by default, but DSM won't recognize this (RSA type only). I had to add --keylength 2048 at the end of the --issue command line. After obtained the new certificate, I successfully --deploy it. |
Thanks
Thanks so much, this fixed it for me! |
Steps to reproduce
export CERT_DOMAIN="nas.bbb.com"
export SYNO_Certificate="nas.bbb.com"
./acme.sh --deploy --home . -d "$CERT_DOMAIN" --deploy-hook synology_dsm --insecure
Debug log
./acme.sh --deploy --home . -d "$CERT_DOMAIN" --deploy-hook synology_dsm --insecure --debug 2
[Sat Jun 22 23:57:18 CEST 2024] Lets find script dir.
[Sat Jun 22 23:57:18 CEST 2024] SCRIPT='./acme.sh'
[Sat Jun 22 23:57:18 CEST 2024] _script='/usr/local/share/acme.sh/acme.sh'
[Sat Jun 22 23:57:18 CEST 2024] _script_home='/usr/local/share/acme.sh'
[Sat Jun 22 23:57:18 CEST 2024] Using config home:.
[Sat Jun 22 23:57:18 CEST 2024] LE_WORKING_DIR='.'
https://github.com/acmesh-official/acme.sh
v3.0.8
[Sat Jun 22 23:57:18 CEST 2024] Running cmd: deploy
[Sat Jun 22 23:57:18 CEST 2024] Using config home:.
[Sat Jun 22 23:57:18 CEST 2024] default_acme_server='https://acme-v02.api.letsencrypt.org/directory'
[Sat Jun 22 23:57:18 CEST 2024] ACME_DIRECTORY='https://acme-v02.api.letsencrypt.org/directory'
[Sat Jun 22 23:57:18 CEST 2024] _ACME_SERVER_HOST='acme-v02.api.letsencrypt.org'
[Sat Jun 22 23:57:18 CEST 2024] _ACME_SERVER_PATH='directory'
[Sat Jun 22 23:57:18 CEST 2024] DOMAIN_PATH='./nas.bbb.com'
[Sat Jun 22 23:57:18 CEST 2024] DOMAIN_CONF='./nas.bbb.com/nas.bbb.com.conf'
[Sat Jun 22 23:57:18 CEST 2024] _deployApi='/usr/local/share/acme.sh/deploy/synology_dsm.sh'
[Sat Jun 22 23:57:18 CEST 2024] _cdomain='nas.bbb.com'
[Sat Jun 22 23:57:19 CEST 2024] SYNO_USE_TEMP_ADMIN
[Sat Jun 22 23:57:19 CEST 2024] SYNO_USE_TEMP_ADMIN='1'
[Sat Jun 22 23:57:19 CEST 2024] Setting temp admin user credential...
[Sat Jun 22 23:57:19 CEST 2024] SYNO_SCHEME='https'
[Sat Jun 22 23:57:19 CEST 2024] SYNO_HOSTNAME='nas.bbb.com'
[Sat Jun 22 23:57:19 CEST 2024] SYNO_PORT='5501'
[Sat Jun 22 23:57:19 CEST 2024] Domain config new key exists, old key SYNO_Certificate='nas.bbb.com' has been removed.
[Sat Jun 22 23:57:19 CEST 2024] SYNO_CERTIFICATE='nas.bbb.com'
[Sat Jun 22 23:57:19 CEST 2024] Getting API version...
[Sat Jun 22 23:57:19 CEST 2024] _base_url='https://nas.bbb.com:5501'
[Sat Jun 22 23:57:19 CEST 2024] GET
[Sat Jun 22 23:57:19 CEST 2024] url='https://nas.bbb.com:5501/webapi/query.cgi?api=SYNO.API.Info&version=1&method=query&query=SYNO.API.Auth'
[Sat Jun 22 23:57:19 CEST 2024] timeout=
[Sat Jun 22 23:57:20 CEST 2024] _CURL='curl --silent --dump-header ./http.header -L --trace-ascii /tmp/tmp.z0jiea5S9n -g --insecure '
[Sat Jun 22 23:57:21 CEST 2024] ret='0'
[Sat Jun 22 23:57:21 CEST 2024] Logging into nas.bbb.com:5501...
[Sat Jun 22 23:57:21 CEST 2024] SYNO_LOCAL_HOSTNAME
[Sat Jun 22 23:57:21 CEST 2024] Creating temp admin user in Synology DSM...
grep: warning: stray \ before -
grep: warning: stray \ before -
[Sat Jun 22 23:57:27 CEST 2024] GET
[Sat Jun 22 23:57:27 CEST 2024] url='https://nas.bbb.com:5501/webapi/entry.cgi?api=SYNO.API.Auth&version=6&method=login&format=sid&account=sc-acmesh-tmp&passwd=JIwBeSN2H2FKP20D&enable_syno_token=yes'
[Sat Jun 22 23:57:27 CEST 2024] timeout=
[Sat Jun 22 23:57:27 CEST 2024] _CURL='curl --silent --dump-header ./http.header -L --trace-ascii /tmp/tmp.lBOv5qlCVC -g --insecure '
[Sat Jun 22 23:57:28 CEST 2024] ret='0'
[Sat Jun 22 23:57:28 CEST 2024] error_code='102'
[Sat Jun 22 23:57:28 CEST 2024] Failed to authenticate with error: 102.
[Sat Jun 22 23:57:28 CEST 2024] Cleanuping temp admin info...
[Sat Jun 22 23:57:31 CEST 2024] Error deploy for domain:nas.bbb.com
[Sat Jun 22 23:57:31 CEST 2024] Deploy error.
Seems that 'https://nas.bbb.com:5501/webapi/entry.cgi?api=SYNO.API.Auth&version=6&method=login&format=sid&account=sc-acmesh-tmp&passwd=JIwBeSN2H2FKP20D&enable_syno_token=yes' isn't working anymore on DSM6 ?
The text was updated successfully, but these errors were encountered: