NGiNX doesn't want to work with a unix-socket. #1

New Issue

Arav · 2022-06-25T04:22:30+04:00

Arav commented

2022-06-25 04:22:30 +04:00

For some reason I cannot make NGiNX communicate with this service over unix-sockets.
I get recursive 301 redirects that remove and add slashes over and over again in one case. Or 502 bad request and an error "(20: Not a directory)" in error.log in another.

For some reason I cannot make NGiNX communicate with this service over unix-sockets. I get recursive 301 redirects that remove and add slashes over and over again in one case. Or 502 bad request and an error "(20: Not a directory)" in error.log in another.

Arav self-assigned this 2022-08-25 04:47:08 +04:00

Arav commented

2022-08-25 04:49:28 +04:00

Okay, the issue was that I had to add a ':' sign after path, and only then place '/'.

proxy_pass http://unix:/var/run/justcaptcha/j.sock:/;

And not:

proxy_pass http://unix:/var/run/justcaptcha/j.sock/;

Okay, the issue was that I had to add a ':' sign after path, and only then place '/'. proxy_pass http://unix:/var/run/justcaptcha/j.sock:/; And not: proxy_pass http://unix:/var/run/justcaptcha/j.sock/;

Arav closed this issue

2022-08-25 04:49:28 +04:00

Sign in to join this conversation.

No Label

No Milestone

No Assignees

1 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Reference: Arav/justcaptcha#1