Jump to content
XPEnology Community

Search the Community

Showing results for tags 'not synology dns'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Information
    • Readers News & Rumours
    • Information and Feedback
    • The Noob Lounge
  • XPEnology Project
    • F.A.Q - START HERE
    • Loader Releases & Extras
    • DSM Updates Reporting
    • Developer Discussion Room
    • Tutorials and Guides
    • DSM Installation
    • DSM Post-Installation
    • Packages & DSM Features
    • General Questions
    • Hardware Modding
    • Software Modding
    • Miscellaneous
  • International
    • РУССКИЙ
    • FRANÇAIS
    • GERMAN
    • SPANISH
    • ITALIAN
    • KOREAN

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


About Me

Found 1 result

  1. Hello all, as my Let's Encrypt certificates weren't no longer extended, I tried it manually using: /usr/syno/sbin/syno-letsencrypt renew-all -v But this didn't work so I checked the debug message: DEBUG: start to renew [/usr/syno/etc/certificate/XXXXXX. DEBUG: setup acme url https://acme-v01.api.letsencrypt.org/directory DEBUG: GET Request: https://acme-v01.api.letsencrypt.org/directory DEBUG: strat to do new-authz for www.XXX.tld DEBUG: ==> start new authz. DEBUG: new authz: do new-authz. DEBUG: Post JWS Request: https://acme-v01.api.letsencrypt.org/acme/new-authz DEBUG: Post Request: https://acme-v01.api.letsencrypt.org/acme/new-authz DEBUG: Not synology DDNS. DEBUG: DNS challenge failed, reason: {"error":108,"file":"challenge.cpp","msg":"Not synology DDNS."} DEBUG: Normal challenge failed, reason: {"error":200,"file":"client.cpp","msg":"new_authz: unexpect httpcode."} Does this mean only original Synologys (with enabled Quick Connect) can extend the certificates? Thanks!
×
×
  • Create New...