Closed igor-bn closed 7 years ago
I get the same error when following the C option with greyltc/nextcloud:latest.
I have the same error. I tracked it down to the certbot
command specifying the webroot to be /srv/http
and /etc/httpd/conf/extra/httpd-acme.conf
pointing .well-known/acme-challenge
to /var/lib/letsencrypt/
. In a running owncloud container named oc
, this command fixes it:
sudo docker exec -it oc sed -i 's/srv\/http/var\/lib\/letsencrypt/' /usr/sbin/setup-apache-ssl-key
I couldn't find where that script is added though.
There, now I have a pull request for you @greyltc. It's always easier to get a fix served :)
Much appreciated,
Thank you!
On 01/31/2017 10:17 PM, Johan Swetzén wrote:
There, now I have a pull request for you @greyltc https://github.com/greyltc. It's always easier to get a fix served :)
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/greyltc/docker-owncloud/issues/112#issuecomment-276495359, or mute the thread https://github.com/notifications/unsubscribe-auth/AXs9o7rbW2n1CSp5bgQDPyJlUX5y2Gycks5rX6UBgaJpZM4LR_Ev.
PR accepted. Thanks!
Here is the second issue I faced after updating to l3iggs/owncloud:latest (aka 9.1.2-1). I get following error from certbot:
Please note, I replaced my domain with "home-net.example.com" in this example. The output makes me think that Apache delivers some standard web page here (404?) instead of actually serving the file. It looks like apache rules got broken.