502 Bad Gateway - Githubissues

tianon / squignix

NGINX, configured to act like Squid

MIT License

32 stars 5 forks source link

502 Bad Gateway #5

Open CatAnonymous opened 4 years ago

CatAnonymous commented 4 years ago

Can not connect to Youtube app
Only works on Chrome and some browsers.
502 status frequently occurs

tianon commented 4 years ago

I'm not sure why you're filing this here? How does this relate to squignix?

CatAnonymous commented 4 years ago

I'm not sure why you're filing this here? How does this relate to squignix?

https://github.com/khaiphan9x/hls-live-streaming-server-auto-installer/blob/master/http-proxy.conf

tianon commented 4 years ago

Are you saying you're routing YouTube traffic through that NGINX configuration? What are you hoping to accomplish by doing so?

CatAnonymous commented 4 years ago

Are you saying you're routing YouTube traffic through that NGINX configuration? What are you hoping to accomplish by doing so?

I am using your config, and when I use HTTP Proxy there was an error status as stated above. Sorry, please let me know if there is a copyright issue

CatAnonymous commented 4 years ago

Are you saying you're routing YouTube traffic through that NGINX configuration? What are you hoping to accomplish by doing so?

Can you fix it to work on the Youtube app?

tianon commented 4 years ago

I'm still really confused why you'd be routing the Youtube app through this configuration -- Youtube is going to use HTTPS, which isn't likely to work with this configuration. This was designed to cache distribution repositories transparently via DNS or TCP/IP hijacking for the purposes of speeding up repeated builds, and it's frankly a hack at best. If you need a general-purpose transparent proxy, I don't think this is the right solution, and something designed for that (like Squid) would probably give you a better experience.

CatAnonymous commented 4 years ago

I'm still really confused why you'd be routing the Youtube app through this configuration -- Youtube is going to use HTTPS, which isn't likely to work with this configuration. This was designed to cache distribution repositories transparently via DNS or TCP/IP hijacking for the purposes of speeding up repeated builds, and it's frankly a hack at best. If you need a general-purpose transparent proxy, I don't think this is the right solution, and something designed for that (like Squid) would probably give you a better experience.

I think it is still possible to add some SSL certificates