- #Youtube proxifier .exe#
- #Youtube proxifier code#
- #Youtube proxifier Pc#
- #Youtube proxifier torrent#
Proxies still play an important role in Internet filtering and connectivity, especially for users who struggle to bypass restrictions and firewall rules that block certain websites and services. Proxifier allows network applications that do not support working through proxy servers to operate through a SOCKS or HTTPS proxy and chains.
#Youtube proxifier .exe#
exe versions: ffmpeg 4.3.1, ffprobe 4.3.The Most Advanced Proxy Client. Encodings: locale UTF-8, fs utf-8, out utf-8, pref UTF-8 This is the port 80 socks5 $ youtube-dl -v ''
#Youtube proxifier code#
I'm not sure how difficult that might be to fix - I might have a look at the code and see, but for now I think I'm going to try a SOCKS proxy instead, as I'm pretty sure I've seen those working with youtube-dl so it should work as long as I can find a NordVPN server which still supports it.Įdit: Ugh, nope, it seems they now have literally no servers which support SOCKS (and the P2P server category is completely empty, for the UK at least). it's just treating proxy URLs the same as ones). So the issue is with youtube-dl not handling HTTPS proxies correctly (i.e. I also tried using openssl as a client to connect to the NordVPN server on port 89, manually sent it a copy of what youtube-dl sends, and even though it's a lot simpler/less headers than what Chrome sends, the NordVPN server still responded that the connection had been established ok. So the NordVPN proxy server sees that as an SSL protocol error, which is why it terminates the connection, not because it detects that the connection isn't from Chrome/another browser. It turns out that both youtube-dl and the Proxy Checker program mentioned above are completely ignoring the HTTP/HTTPS setting and treating both as a HTTP proxy, so what gets sent to the proxy server is a plaintext CONNECT HTTP request, whereas it should be establishing an SSL connection first, then sending the HTTP request within that. I ended up using openssl to create a listening SSL server so that I could see what exactly each of these programs is sending when they try to connect to it as a HTTPS proxy. I've also tried connecting to the proxy with this program, with the same result, the connection just gets closed immediately: As you say, port 89 works via Chrome so I've just been trying to narrow down what exactly is different about the connection from Chrome compared to youtube-dl. It was previously working with port 80, but that's now been closed on the NordVPN server I was using with it and I haven't been able to find any others with that port open.
#Youtube proxifier torrent#
though some comments in r/nordvpn suggests they only support proxy use via browsers and torrent clients (?!) - no idea how they figure that out. (tagging /u/Nouphal cause i made a large edit)Įdit 2: port 89 is also available, i think that's the port used by the browser extension. and youtube-dl works with other proxies, like i run tinyproxy in a few places to access youtube via other countries easily.
However, i could so far only get it to work with curl, not youtube-dl. but port 90 is open and works as https, because this is the cybersec ssl (i think it's a service that filteres for malware) port 443 was, but i get ssl error if using https on it, and empty response if using http. port 80 on the nordvpn servers that i tested was filtered, not open. If this don't help, post the error message.Įdit: looked more into this. (it gave a connect error when syntax was wrong)
I've tried this recently, and that's the syntax that worked, however, i kept getting timeouts while trying to load the webpage. both should be at port 80 i believe, as strange as it is. use http if you picked a http proxy in nordvpn's service list. The syntax is -proxy you've picked a https proxy. This is noob question but please help me out. do I need to be on my regular network for the proxy in my config to work. if im already logged in to vpn whats the point of putting a proxy in my config.
proxy service ***credinetial id:service credential socks5:// service ***credinetial id:service credential of these don't workĭo I literally have to not change the example and plug socks5://127.0.0.1:1080/ which I did btw into config file. I have config file in ~.config/youtube-dl/config
#Youtube proxifier Pc#
proxies acts as an ip address stand in, where vpn is like a tunnel from your pc to the vpn provider to some site.
I have done some reading and I understand the basics. proxy URL Use the specified HTTP/HTTPS/SOCKS proxy.
0 kommentar(er)
