Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
[ERROR] Making new certificate manager: could not save user: mkdir /etc/ssl/caddy/acme: read-only file system #347
[ERROR] Making new certificate manager: could not save user: mkdir /etc/ssl/caddy/acme: read-only file system
無奈自己是個小白，很長時間不知道這是什麼原因造成，只能在VPS上不斷重裝系統試錯，Debian 7/8/9、Ubuntu 16.04，到上週搞了CentOS 7，但都不成功，還試著改用Caddy的官方一鍵安裝腳本，也是不行。直到看到下面兩篇教學，試著把systemd用的caddy.service文檔裡的ReadWritePaths=/etc/ssl/caddy改成ReadWriteDirectories=/etc/ssl/caddy，然後證書申請就通過了。如果也是碰到同樣問題的朋友，不妨試試。
Hello! I am an engineer at Let's Encrypt. We had some problems because V2Ray was sending us too many requests, and we had to block some V2Ray users. We discussed the problem here: https://community.letsencrypt.org/t/need-unblock-ip/103584.
@233boy, you made a fix at 5fbdf86#diff-e16fccbf00a60d8781b481f7547dffe5R37-R58. But I am worried that these lines will cause problems in the future:
These mean that if there is a problem, Caddy will restart quickly, and send too many requests to Let's Encrypt.
In the systemd unit provided by Caddy, it has these lines:
I think these are better. Could you change these lines?
Even better, could you switch back to the systemd unit provided by Caddy after caddyserver/caddy#2798 is merged?