Skip to content

Conversation

JohnMertz
Copy link
Contributor

As discussed here: #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.

As discussed here: #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.
@buchdag buchdag changed the title Specific error for socket permission feat: specific error for socket permission Sep 19, 2024
@buchdag buchdag merged commit f513d5a into nginx-proxy:main Sep 19, 2024
36 checks passed
@buchdag
Copy link
Member

buchdag commented Sep 19, 2024

Thanks @JohnMertz

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants