Piped-Docker icon indicating copy to clipboard operation
Piped-Docker copied to clipboard

Nginx cannot connect to pipedproxy

Open ormoyo opened this issue 1 year ago • 2 comments

Hello,

I am trying to self host, I ran the configure-instance.sh and chose nginx, I use nginx proxy manager as the reverse proxy. I followed all of the steps in the self host docs, my instance can show video titles but doesn't show thumbnails or play videos. I looked at the docker logs for the piped containers, they all look working, except the nginx logs which showed the error:

2024/06/21 04:01:05 [crit] 22#22: *53 connect() to unix:/var/run/ytproxy/actix.sock failed (13: Permission denied) while connecting to upstream,
client: 172.29.0.6, server: pipedproxy.example.org, request: "GET /sw.js HTTP/1.1", upstream: "http://unix:/var/run/ytproxy/actix.sock:/sw.js", host: "youtube.example.org"

All of the containers run on the same user so I don't understand why there are permission problems.

I kept all of the configuration files the same and I am running this on a nixos 23.11 server.

ormoyo avatar Jun 21 '24 05:06 ormoyo

Hello, same procedure and I have a 400 Bad Request on a generic Ubuntu 22.04 server

KevinSalmon avatar Jun 24 '24 21:06 KevinSalmon

Heys I might have found the issue. When adding website using configure-instance.sh It fails to edit "config>config.properties" There could be permission issue idk I'm doing this on windows You can edit this file manually as they are mounted in docker container

Replace HTTP_Mode_Placeholder with https or http based on what you choose during configure-instance.sh

You can look at Piped-Backend Repo for comparision

https://github.com/TeamPiped/Piped-Backend/blob/master/config.properties

after editing you simply restart the backend container. And if it doesn't work create new container..

And you might wanna clear site cache from your browser. Because it may continue loading prevoius website that HTTP_Mode_Placeholder issue.

FatVenom avatar Jan 15 '25 06:01 FatVenom