Originally created by @martinvolf on GitHub (Dec 15, 2015).
When letsencrypt.sh creates ${WELLKNOWN}, it should probably chmod 0711 it, otherwise it has 0700 mode.
Originally created by @martinvolf on GitHub (Dec 15, 2015).
When letsencrypt.sh creates ${WELLKNOWN}, it should probably `chmod 0711` it, otherwise it has 0700 mode.
i kinda fixed this by removing the functionality to automatically create the directory in 5a29d1853e
since the default path is useless anyway i think this is better for now, may reimplement this when #34 is done.
@lukas2511 commented on GitHub (Dec 16, 2015):
i kinda fixed this by removing the functionality to automatically create the directory in 5a29d1853efcfda2e3880f8a5a56931701a1ae07
since the default path is useless anyway i think this is better for now, may reimplement this when #34 is done.
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 @martinvolf on GitHub (Dec 15, 2015).
When letsencrypt.sh creates ${WELLKNOWN}, it should probably
chmod 0711it, otherwise it has 0700 mode.@ik0 commented on GitHub (Dec 16, 2015):
+1
nginx can't read it and return "Permission denied", so challenge is invalid.
@lukas2511 commented on GitHub (Dec 16, 2015):
i kinda fixed this by removing the functionality to automatically create the directory in
5a29d1853esince the default path is useless anyway i think this is better for now, may reimplement this when #34 is done.