How to Set Up a Dedicated Link

Some paid AdGuardHome services provide a dedicated link that does not allow users to access the backend management, with administrators managing the rules on their behalf.

This indicates that they do not offer private backend management functionality, but rather implement the service through domain reverse proxy, which is relatively cost-effective.

You need to rent a server to run the AdGuardHome service and configure Nginx reverse proxy to achieve this functionality.

Taking the service link 5r69hxdx9onl70hp.example.com as an example, the key Nginx configuration is as follows:

http {
  server {
    listen 1080;
    server_name 5r69hxdx9onl70hp.example.com;
    location / {
      proxy_pass http://worker.example.com:5002;
      proxy_set_header Host $http_host;
    }
  }
  server {
    listen 1443 ssl;
    server_name 5r69hxdx9onl70hp.example.com;
    ssl_certificate /app/data/certs/5r69hxdx9onl70hp/fullchain.pem;
    ssl_certificate_key /app/data/certs/5r69hxdx9onl70hp/privkey.pem;
    location / {
      proxy_pass https://worker.example.com:5003;
      proxy_set_header Host $http_host;
    }
  }
}
stream {
  ssl_protocols TLSv1.2 TLSv1.3 SSLv3;
  map $ssl_preread_server_name $targetBackend {
    5r69hxdx9onl70hp.example.com worker.internal.com:5004;
  }
  server {
    listen 1853;
    proxy_pass $targetBackend;
    ssl_preread on;
  }
}

Each paying user only needs to add a similar Nginx configuration, with domain resolution pointing to the server. When there are many users and the pressure on a single application service is high, it can be proxied to different backends.

Such services cannot achieve true personalization; users need to be able to access the backend to truly control their internet data, which is an advantage of our private service where a user truly has exclusive use of a service, utilizing all the features of AdGuardPrivate.

• ←Previous Page
• Next Page→