session-pysogs icon indicating copy to clipboard operation
session-pysogs copied to clipboard

SOGS-proxied: oxen/v4/lsrpc failed (2: No such file or directory),

Open slrslr opened this issue 2 years ago • 1 comments

Hello, in sogs-proxied 0.3.5 on Debian 11 (apt package) with nginx "tail /var/log/nginx/error.log" shows many:

22:31:57 [error] redacted: *545 open() "/var/www/html/oxen/v4/lsrpc" failed (2: No such file or directory), client: redacted, server: 127.0.0.1, request: "POST /oxen/v4/lsrpc HTTP/1.1", host: "redacted" 22:31:58 [error] redacted: *548 open() "/var/www/html/oxen/v4/lsrpc" failed (2: No such file or directory), client: redacted, server: 127.0.0.1, request: "POST /oxen/v4/lsrpc HTTP/1.1", host: "redacted" 22:31:58 [error] redacted: *549 open() "/var/www/html/oxen/v4/lsrpc" failed (2: No such file or directory), client: redacted, server: 127.0.0.1, request: "POST /oxen/v4/lsrpc HTTP/1.1", host: "redacted"

I am unable to find any directory/file like that: find / -name lsrpc;find / -name oxen|grep v4

My nginx.conf is here.

Which command to run, what to modify to prevent this please?

slrslr avatar Dec 07 '22 17:12 slrslr

On Wed, 07 Dec 2022 09:11:03 -0800 slrslr @.***> wrote:

Hello, in sogs-proxied 0.3.5 on Debian 11 (apt package) with nginx "tail /var/log/nginx/error.log" shows many:

22:31:57 [error] redacted: *545 open() "/var/www/html/oxen/v4/lsrpc" failed (2: No such file or directory), client: redacted, server: 127.0.0.1, request: "POST /oxen/v4/lsrpc HTTP/1.1", host: "redacted" 22:31:58 [error] redacted: *548 open() "/var/www/html/oxen/v4/lsrpc" failed (2: No such file or directory), client: redacted, server: 127.0.0.1, request: "POST /oxen/v4/lsrpc HTTP/1.1", host: "redacted" 22:31:58 [error] redacted: *549 open() "/var/www/html/oxen/v4/lsrpc" failed (2: No such file or directory), client: redacted, server: 127.0.0.1, request: "POST /oxen/v4/lsrpc HTTP/1.1", host: "redacted"

I a unable to find any directory/file like that: find / -name lsrpc;find / -name oxen|grep v4

My nginx.conf is here.

Which command to run, what to modify to prevent this please?

the resulting nginx config will have the sogs only accessible via https://domain.tld and https://www.domain.tld but not http://main.domain.tld http://domain.tld and http://www.domain.tld

it may be best to use a dedicated subdomain like sogs.domain.tld to make it easier to configure nginx.

if not you can use a location blocks in the server blocks you want to allow sogs accessed by

location /oxen/v4/lsrpc { proxy_set_header X-Real-IP $remote_addr; proxy_pass http://127.3.2.1:4242$request_uri; }

majestrate avatar Dec 07 '22 17:12 majestrate