Originally created by @amelroua on GitHub (Dec 10, 2019).
I tried to create a let's encrypt certificate in my openwert router using the following tuto http://blog.shahada.abubakar.net/post/getting-free-ssl-certificates-from-letsencrypt-org-on-openwrt-using-dehydrated-
however when I execute the command : ./dehydrated -c
I get this error : ERROR: WELLKNOWN directory doesn't exist, please create /etc/www/dehydrated and set appropriate permissions.
I have already created /etc/www/dehydrated and I can access to it and permissions are set @ drwxrwxrwx for /etc/www/dehydrated and -rwxrwxrwx for etc/dehydrated/config.
Originally created by @amelroua on GitHub (Dec 10, 2019).
I tried to create a let's encrypt certificate in my openwert router using the following tuto http://blog.shahada.abubakar.net/post/getting-free-ssl-certificates-from-letsencrypt-org-on-openwrt-using-dehydrated-
however when I execute the command : ./dehydrated -c
I get this error : ERROR: WELLKNOWN directory doesn't exist, please create /etc/www/dehydrated and set appropriate permissions.
I have already created /etc/www/dehydrated and I can access to it and permissions are set @ drwxrwxrwx for /etc/www/dehydrated and -rwxrwxrwx for etc/dehydrated/config.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @amelroua on GitHub (Dec 10, 2019).
I tried to create a let's encrypt certificate in my openwert router using the following tuto http://blog.shahada.abubakar.net/post/getting-free-ssl-certificates-from-letsencrypt-org-on-openwrt-using-dehydrated-
however when I execute the command : ./dehydrated -c
I get this error : ERROR: WELLKNOWN directory doesn't exist, please create /etc/www/dehydrated and set appropriate permissions.
I have already created /etc/www/dehydrated and I can access to it and permissions are set @ drwxrwxrwx for /etc/www/dehydrated and -rwxrwxrwx for etc/dehydrated/config.
@lukas2511 commented on GitHub (Apr 28, 2020):
Can't reproduce this issue and got no similar reports over any available channel, closing for now.