Search the Community

Showing results for tags 'lets encrypt'.

  • 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
    • CHINESE
    • HUNGARIAN

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 4 results

  1. Привет всем! Зделал хук на проверку домена (DNS API) для ACME-клиента acme.sh Если у Вас есть желание потестировать - вэлкам. Процедуру описал на англоязычном форуме. Жду комментариев.
  2. As you know standard certificate issuing wizard supports wildcards only for Synology DDNS. If you want to issue wildcard certificate for your own domain you can use 3rd-party ACME Client. At first I've tried to use Certbot in Docker with no success. Then I found acme.sh that is working fine on Synology DSM (mine is 6.2 on DS918+). Below you can find a short list for issuing, updating and deploying wildcard cert for you own domain on Synology DSM with Synology DNS Server. 1. Installing acme.sh Open SSH client's terminal, go to any folder with write access permissions (e.g.
  3. This is my first attempt at a tutorial here, so please go easy on me. I've spent some time yesterday understanding the process and various issues and common errors we can easily make. This guide is based on 6.2.2-24922 U6. It may work with other versions of DSM, but I've tested it and managed to get it working on this one. First, a few pre-requisites: You need a domain name for which you have administrative access and control. I already had one I could use. I think getting it to work on free dynamic DNS domain names is very difficult due to Let's Encrypt (LE) limi
  4. 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/acm