• AnyStream is having some DRM issues currently, Netflix is not available in HD for the time being.
    Situations like this will always happen with AnyStream: streaming providers are continuously improving their countermeasures while we try to catch up, it's an ongoing cat-and-mouse game. Please be patient and don't flood our support or forum with requests, we are working on it 24/7 to get it resolved. Thank you.

Https proxy support? (Best proxy service to get around geo location?)

Pelvis Popcan

Well-Known Member
Thread Starter
Joined
Jan 28, 2007
Messages
1,675
Likes
60
I am using AnyStream on a VPS in the USA. Works great!

But to get access to other countries, I cannot use a VPN, because I would then lose access to the VPS and have other issues. So, I need a proxy.

In the past, I could use Nord. Nord works good for getting around geo location restrictions on streaming services, and has proxies in many countries:

https://nordvpn.com/servers/tools/

But in the recent past couple of years, Nord has removed http support and socks5 support, which has degraded the usefulness of the service for me. Nord proxies now only work on https on port 89. This does work well in browser.

I was surprised to find that AnyStream doesn't have https proxy support. I tried a Nord proxy on port 89 anyway, and was not surprised to find that it did not work.

Is there a way to get https proxies working in AnyStream, or could support for it be added?

If not, what do you recommend for a SOCKS5 proxy service that has locations in UK, France, Australia, etc. and can be used to bypass geo location restrictions (i.e., is not banned from the streaming services)?
 
Actually, I just tried SOCKS5 through IPVanish, and that doesn't work either. Works fine in Firefox/FoxyProxy.

XFs0KCJ.png

Code:
00:00:00.000 - [Debug] [tabs] Setting up provider Amazon Prime Video
00:00:00.000 - [Debug] [tabs] Starting up Amazon Prime Video
00:00:00.070 - [Debug] [tabs] Setting up provider Netflix
00:00:00.070 - [Debug] [tabs] Starting up Netflix
00:00:00.070 - [Debug] [tabs] Setting up provider Disney+
00:00:00.070 - [Debug] [tabs] Starting up Disney+
00:00:00.071 - [Debug] [tabs] Setting up provider Hulu USA
00:00:00.071 - [Debug] [tabs] Starting up Hulu USA
00:00:00.071 - [Debug] [tabs] Setting up provider HBOmax
00:00:00.071 - [Debug] [tabs] Starting up HBOmax
00:00:00.085 - [Notice] [main window] Start logging at Thu Dec 16 19:06:22 2021 GMT
00:00:00.086 - [Debug] [tabs] Tab changed
00:00:00.086 - [Debug] [tabs] Checking for matching provider...
00:00:00.086 - [Debug] [tabs] Create new panel for Amazon Prime Video
00:00:00.093 - [Debug] [Prime] using proxy: Socks5, host: lon.socks.ipvanish.com, port 1080
00:00:00.121 - [Debug] [CEFView::prime] Browser has been created
00:00:00.122 - [Debug] [tabs] New provider widget: Amazon Prime Video
00:00:00.122 - [Debug] [tabs] Amazon Prime Video panel loaded.
00:00:00.122 - [Debug] [main window] Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/96.0.4664.45 Safari/537.36
00:00:00.136 - [Debug] License confirmed.
00:00:00.136 - [Notice] AnyStream version 1.2.7.0 (42)
00:00:00.497 - [Error] [CEFView::Handler::prime] Load error: ERR_SOCKS_CONNECTION_FAILED
00:00:00.497 - [Debug] [CEFView::Handler::prime] CEFHandler::OnDocumentAvailableInMainFrame
00:00:00.499 - [Debug] [CEFView::prime] Load completed. Status code: 0 - https://www.amazon.co.uk/av
00:00:03.537 - [Debug] [License] updated: available 100, timeToNext -1
00:00:12.095 - [Debug] [prime] using proxy: Socks5, host: lon.socks.ipvanish.com, port 1080
00:00:12.097 - [Debug] [netflix] not using proxy
00:00:12.097 - [Debug] [disney] not using proxy
00:00:12.098 - [Debug] [hulu] not using proxy
00:00:12.098 - [Debug] [hbomax] not using proxy
00:00:29.394 - [Debug] [prime] using proxy: Socks5, host: lon.socks.ipvanish.com, port 1080
00:00:29.394 - [Debug] [netflix] not using proxy
00:00:29.394 - [Debug] [disney] not using proxy
00:00:29.394 - [Debug] [hulu] not using proxy
00:00:29.394 - [Debug] [hbomax] not using proxy
00:00:29.395 - [Debug] [tabs] Setting up provider Amazon Prime Video
00:00:29.395 - [Debug] [tabs] Already up
00:00:29.395 - [Debug] [tabs] Setting up provider Netflix
00:00:29.395 - [Debug] [tabs] Already up
00:00:29.395 - [Debug] [tabs] Setting up provider Disney+
00:00:29.395 - [Debug] [tabs] Already up
00:00:29.395 - [Debug] [tabs] Setting up provider Hulu USA
00:00:29.396 - [Debug] [tabs] Already up
00:00:29.396 - [Debug] [tabs] Setting up provider HBOmax
00:00:29.396 - [Debug] [tabs] Already up
00:01:14.827 - [Error] [CEFView::Handler::prime] Load error: ERR_SOCKS_CONNECTION_FAILED
00:01:14.827 - [Debug] [CEFView::Handler::prime] CEFHandler::OnDocumentAvailableInMainFrame
00:01:14.828 - [Debug] [CEFView::prime] Load completed. Status code: 0 - https://www.amazon.co.uk/av

Am I doing something wrong, or is this a bug or known issue?
 

Attachments

  • AnyStream_1.2.7.0.astlog
    1.6 KB · Views: 2
Last edited:
I was able to switch regions to Amazon UK in AnyStream and use a UK SOCKS5 proxy (IPVanish) using Proxifier. So that appears to be a solution for SOCKS5.

For HTTPS, Proxifier is supposed to support it. But I cannot get it to work with Nord. It appears to be a problem with how Proxifier is trying to authenticate. I actually remember trying to use Proxifier with Nord last year via HTTPS on port 89, and I e-mailed Proxifier support. Their response was that "Nord is unstable" which isn't promising, because I find that Nord is VERY stable in Chrome/SwitchyOmega and Firefox/FoxyProxy via HTTPS/port 89. They also said, "Find a https proxy that works and send logs". I don't know of any other commercial service that uses https proxies with authentication. It seems most services use SOCKS5. It's strange that Nord removed SOCKS5 support and went with HTTPS. Anyway, I suspect it would fail the same way... when trying to use Nord HTTPS on port 89 with Proxifier, it only gives the error, "Proxy closed the connection unexpectedly". It actually behaves the exact same way if I use a randomly generated user name and password, so I'm sure it's an authentication problem. Don't expect it to be fixed a this point.

Anyway, at least there exists a SOCKS5 solution for now! :p
 
Troubleshooting and solving my own issues... :p

So, I got HTTPS to work with AnyStream, using a simple command line utility called Stone, located here: https://raw.githubusercontent.com/xtkoba/yt-dlp/stone/stone-2.4-x64.zip

This is just a HTTP repeater that uses OpenSSL for decryption.

So for Nord, open the command line at the directory with stone, then run stone.exe serverofchoice.nordvpn.com:89/ssl 8080

Keep the above command line open as long as you want the proxy active.

In AnyStream, set HTTP proxy for provider as localhost at port 8080, with your NordVPN user name and password.

So for Amazon UK, set region in AnyStream to United Kingdom, then enter the above for the proxy, with Stone running on the command line in the background using the above posted command line, using a UK NordVPN server. Then restart AnyStream.

This technique will also work in Proxifier for any application, but the server type in Proxifier needs to be specified as HTTPS.

(Just a side note... keep in mind that torrent applications don't work 100% with HTTP/HTTPS/SOCKS4 proxies.)

I attached the Stone executable archive just in case it's needed in the future by someone (or me :p).
 

Attachments

  • stone-2.4-x64.zip
    1.7 MB · Views: 5
Just a question: How would one determine if this "stone" utility is "trustworthy"?
I mean, it appears to me as if you are passing both your NordVPN as well as ServiceProvider (Amazon) username and passwords via this application?
 
@NeedToKnow
I hope you won't mind if I'll put my reply here.

The posted archive seems to contain also the tool source code (stone.c).
Usually, when you post source code, you have nothing to hide.

If someone is skilled enough might be able to analyze it and/or recompile it from source.
Maybe @Pelvis Popcan did exactly that.
 
It's an extremely simple repeater with OpenSSL for decryption. It's been around since 1995. It's written by Hiroaki Sengoku. Homepage: http://www.gcd.org/sengoku/stone/

The above page only has version 2.4 for Linux. The 2.3e Windows downloads from the above page don't support TLS 1.2 (needed for Nord HTTPS), but you could remedy that by overwriting the two OpenSSL dll's (libeay32.dll and ssleay32.dll) with the ones from openssl-1.0.2u-x64_86-win64.zip (from this repository). But the version I linked/attached above is a 64 bit build of version 2.4 for Windows that includes OpenSSL 1.1.1m.
 
I always wanted a way to do this! Thanks for sharing these details and appreciate your research! :)

This post is worth to be a sticky..
 
The proxy server can be configured in the system settings on a PC or laptop. You won’t need any additional software to do this. This method allows you to organize an anonymous connection only through one intermediary server. I use the cheap cpanel license. Firstly you should press Win+C to connect a proxy server to Windows. Then find the section on changing network settings and open the proxy server settings. Then specify the IP address and port of the server you are going to use.
 
Last edited:
Troubleshooting and solving my own issues... :p

So, I got HTTPS to work with AnyStream, using a simple command line utility called Stone, located here: https://raw.githubusercontent.com/xtkoba/yt-dlp/stone/stone-2.4-x64.zip

This is just a HTTP repeater that uses OpenSSL for decryption.

So for Nord, open the command line at the directory with stone, then run stone.exe serverofchoice.nordvpn.com:89/ssl 8080

Keep the above command line open as long as you want the proxy active.

In AnyStream, set HTTP proxy for provider as localhost at port 8080, with your NordVPN user name and password.

So for Amazon UK, set region in AnyStream to United Kingdom, then enter the above for the proxy, with Stone running on the command line in the background using the above posted command line, using a UK NordVPN server. Then restart AnyStream.

This technique will also work in Proxifier for any application, but the server type in Proxifier needs to be specified as HTTPS.

(Just a side note... keep in mind that torrent applications don't work 100% with HTTP/HTTPS/SOCKS4 proxies.)

I attached the Stone executable archive just in case it's needed in the future by someone (or me :p).
This is what I feel like when trying to understand this stuff. :LOL:

download.jpg
 
Back
Top