John Mertz 517d59438c Specific error for socket permission ... As discussed here: https://github.com/nginx-proxy/acme-companion/issues/1054 If socket is not readable, for example when protected with SELinux and/or run as a rootless user, the existing error is deceptive. An additional error to check that it is readable before checking if it is a socket will clarify the problem. SELinux tip included for good measure.		2024-09-10 20:02:17 -06:00
..
dhparam	feat: use pre generated RFC7919 DH groups	2021-12-14 23:32:39 +01:00
cert_status	fix: don't display LE certificate as erroneously expired	2023-12-25 15:43:03 +01:00
cleanup_test_artifacts	Fix unintentional file globbing during wildcard lookup	2021-03-15 18:14:22 -07:00
dhparam.pem.default	Use background DH group creation (#394)	2018-06-08 15:09:50 +02:00
entrypoint.sh	Specific error for socket permission	2024-09-10 20:02:17 -06:00
force_renew	Shellcheck linting (#641)	2020-03-23 08:20:46 +01:00
functions.sh	refactor: ensure we never grep more than one container id	2024-05-04 12:41:59 +02:00
letsencrypt_service	feat: global & per container acme.sh DNS API config	2024-07-16 23:33:20 +02:00
letsencrypt_service_data.tmpl	refactor: remove unused range index	2024-07-17 07:33:31 +02:00
nginx_location.conf	Set auth_request off for acme challenge location	2019-08-18 21:19:36 -04:00
signal_le_service	Remove old procps specific pkill command (#400)	2018-06-13 14:12:29 +02:00
start.sh	refactor: apply suggestions from code review	2024-07-19 08:46:27 +02:00