🎥 Hint: you can also watch DataUnlocker setup tutorial video.
At the first step, you will be asked to set up a proxy endpoint, which can be either:
- DNS-based (default and preferred)
- Path-based (when you want to use your own proxy servers - see below)
Choose a DNS-based option if you have an access to your domain, as it is the easiest option available. The second option requires you to set up a reverse proxy on your own, which will forward all traffic to DataUnlocker's proxy servers with a few additional headers.
You can also add multiple proxy endpoints, but usually only one is required, and only one proxy endpoint is used by DataUnlocker's script at a time. You can add more proxy endpoints in case your previous proxy endpoints are getting blocked (ultra-rare for not globally known websites), or you add a new proxy endpoint and then switch to it to for example change the proxy method from DNS-based to path-based.
The setup guide will suggest a new DNS record you will need to add to your domain at the very beginning. This is usually done on the website where you have purchased your domain. The exact steps for adding a DNS record vary between domain registrars, and we suggest you to look at some common cases to understand how DNS is configured.
Add DNS records exactly as the setup guide suggests, and you should get a working endpoint soon:
Note the following:
- ⏳ It takes around 5 minutes for the new DNS record to propagate through the DNS network and reach Google DNS servers (which is used by DataUnlocker). For some providers it may take a bit longer. You can use different tools to check whether your new DNS record started to propagate.
- ⚡ If you're using CloudFlare for managing DNS records, please ensure the proxy is turned off for this DNS record (an orange-cloud icon is not orange).
There are a few use-cases for choosing path-based over DNS-based proxy endpoints:
- Your (website hosting) provider doesn't provide you with access to manage your domain's DNS records. Then you can even run a free back end ("cloud function") like this one, connecting it to DataUnlocker servers.
- You want blocked browser request to be proxied through your own IP address. This will make proxy effective against DNS blocking or DNS uncloaking (which are anyway used by < 1% of content blocking software users).
If you decide to use the path-based proxy endpoint, you will need to run your own reverse proxy back end like this one. You also need to ensure that your reverse proxy server additionally:
x-du-ipheader to all proxied requests
- It doesn't modify any existing headers.
- It strips the "proxy path prefix" from the request (URL path prefix requested by DataUnlocker).