@
cloudjo23, not sure how familiar you are with Docker, Vagrant, or Linux.
Besides the obvious solution (as stated in that GitHub repo) to get a Debian/Ubuntu computer with a public IP or get one from a cloud provider like AWS and DigitalOcean, you can try this in Docker and Vagrant. (Google them up if you are not familiar with them)
With Docker, you will be doing Docker in Docker using
docker:dind
image. Not the best solution and I doubt it would work. I tried it but it failed. The next step was to try building it with an Ubuntu image via Docker:
Dockerfile
Code:
FROM ubuntu:18.04
LABEL description="Dockerfile for https://github.com/ab77/nêtflïx-proxy"
RUN apt-get update\
&& apt-get -y install vim dnsutils curl sudo\
&& curl -fsSL https://get.docker.com/ | sh || apt-get -y install docker.io\
&& mkdir -p ~/nêtflïx-proxy\
&& cd ~/nêtflïx-proxy\
&& curl -fsSL https://github.com/ab77/nêtflïx-proxy/archive/latest.tar.gz | gunzip - | tar x --strip-components=1\
&& ./build.sh
CMD ["/bin/sh"]
To build this Docker image, do
docker build -f Dockerfile -t nêtflïx-proxy .
However this fails to
Code:
Bad argument `tcp'
Try `ip6tables -h' or 'ip6tables --help' for more information.
...fail!
* creating Docker and sniproxy configuration templates...
...done.
* disabling Docker iptables control...
cp: cannot create regular file '/etc/docker/': Not a directory
If you are in the mood to troubleshoot this Dockerfile, be my guest and let me know your findings.
The other way is via Vagrant.
1. Install Vagrant and VirtualBox
2. Create a directory in your computer
3. Open a terminal to this directory and do
vagrant init generic/ubuntu1804
We are installing an Ubuntu image to VirtualBox which will be automated by Vagrant.
4. Login to the machine.
vagrant up
and then
vagrant ssh
5. Now on the terminal copy and paste this:
Code:
sudo apt-get update\
&& apt-get -y install vim dnsutils curl sudo\
&& curl -fsSL https://get.docker.com/ | sh || sudo apt-get -y install docker.io\
&& mkdir -p ~/nêtflïx-proxy\
&& cd ~/nêtflïx-proxy\
&& curl -fsSL https://github.com/ab77/nêtflïx-proxy/archive/latest.tar.gz | gunzip - | tar x --strip-components=1\
&& sudo ./build.sh
It may take a while for these commands to finish but at the end of the day, you should be able to see Docker processes running at the end of the script when do you do
sudo docker ps
Code:
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
e15e30669552 andyshinn/dnsmasq:latest "dnsmasq -k --port=5…" 10 minutes ago Up 10 minutes dnsmasq-bogus
4ff49e24830b andyshinn/dnsmasq:latest "dnsmasq -k" 10 minutes ago Up 10 minutes dnsmasq
aedf9b3920b0 abiosoft/caddy:latest "/bin/parent caddy -…" 10 minutes ago Up 10 minutes caddy
d939a018afd6 ab77/sniproxy:latest "/bin/sh -c ./run.sh" 10 minutes ago Up 10 minutes sniproxy
Also you should be able to
curl
the login page via
curl -H "X-CSRF-Token: 97b8750f6d214ca08de58d72e2488bd2" -X POST -F 'username=admin' -F 'password=something' localhost:8080/login
. I am using curl instead of using an actual browser. The reason why you would login here is because according to the Github docs:
At the end of the day I don't really need this nêtflïx proxy because I am already in the US and I can watch nêtflïx. Only reason I did the processes above are for education purposes. Also there is no point in running Docker or Vagrant on your local machine if your purpose is to make a proxy because essentially at the end of the line, it will still show your IP. What you should do is the steps above on a cloud provider.
Also why I do keep mentioning docker, well if you read the Github docs, this tool is really meant to be run inside Docker
Ok I'm back to playing chess online.
EDIT: I notice this forum mangles the word nêtflïx. Is it a taboo word?