Skip to content
This repository has been archived by the owner on Feb 17, 2019. It is now read-only.

does this still work with netflix's new blocking methods ? #35

Open
diginfo opened this issue Jun 6, 2016 · 3 comments
Open

does this still work with netflix's new blocking methods ? #35

diginfo opened this issue Jun 6, 2016 · 3 comments

Comments

@diginfo
Copy link

diginfo commented Jun 6, 2016

As netflix have 'improved' their VPN / unlocker checks, does this still work ?

@chrisbensch
Copy link

I tried recently and they can tell that I'm using some kind of service. I was using DigitalOcean.com and looks like they've at least blocked their SFO IP space.

@ehintz
Copy link

ehintz commented Jun 10, 2016

Broke for me, so far I've seen no solution. Probably going to go to a full vpn solution to get around it. Seems there are ways around it tho, the commercial services seem to have figured it out, but I've been keeping an eye on the forum here for a month or so and no significant action. A few googles haven't found enlightenment either, so while the commercials have it sorted they aren't talking about how as far as I've seen.

@janusqa
Copy link

janusqa commented Jan 4, 2017

Hi
How do I fix the below error...

web@smartdns:~/dockerflix$ docker-compose up -d us
ERROR: Couldn't connect to Docker daemon at http+docker://localunixsocket - is it running?

If it's at a non-standard location, specify the URL with the DOCKER_HOST environment variable.

Thanks in advance.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants