Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add upstream proxy settings to AdGuard Home #458

Closed
tomiams opened this issue Nov 10, 2018 · 9 comments
Closed

Add upstream proxy settings to AdGuard Home #458

tomiams opened this issue Nov 10, 2018 · 9 comments

Comments

@tomiams
Copy link

tomiams commented Nov 10, 2018

Regarding AdGuard Home features, an essential one would be the integration of a proxy (with authentication) into it.

At the very least, as a temporary solution, add an option to mask/randomize the IP address going to the upstream DNS to fetch the website addresses.

@ameshkov
Copy link
Member

Do you mean an upstream proxy, right?

@tomiams
Copy link
Author

tomiams commented Nov 10, 2018

Correct.

@ameshkov ameshkov changed the title [Feature Request] [Important] Add Proxy settings to AdGuard Home 🔴 Add upstream proxy settings to AdGuard Home Nov 11, 2018
@ameshkov
Copy link
Member

This proxy is supposed to be used when AG downloads filters updates, right?

I am not sure using it for anything else would be viable

@hmage hmage added the waiting for data Waiting for users to provide more data. label Nov 23, 2018
@tomiams
Copy link
Author

tomiams commented Dec 3, 2018

Yes, that is exactly what it would be used for.
Potentially, when AdGuard Home auto-update (or GUI update) feature is implemented, the update checks and download could be fetched through the proxy as well.

@ameshkov ameshkov removed the waiting for data Waiting for users to provide more data. label Dec 4, 2018
@ameshkov
Copy link
Member

ameshkov commented Dec 4, 2018

@tomiams got it. Makes sense indeed

@hmage
Copy link
Contributor

hmage commented Dec 4, 2018

@tomiams While you wait for the GUI, you can already use upstream HTTP proxy by setting the HTTP_PROXY environment variable for AdGuardHome:

export HTTP_PROXY=http://proxy.lan:3128/

or, if there's username and password:

export HTTP_PROXY=http://user:[email protected]:3128/

You need to put this environment setting accordingly depending on how you launch AdGuardHome.

@tomiams
Copy link
Author

tomiams commented Dec 9, 2018

@hmage Thank you for the awesome tip! Works really well.

@desimone
Copy link

desimone commented Oct 9, 2019

Hey AdGuard team (@hmage , @ameshkov)

We recently added a recipe to do just this with Pomerium. Look forward to your thoughts. :)
pomerium/pomerium#359

@ameshkov
Copy link
Member

ameshkov commented Oct 9, 2019

@desimone looks good, thank you!

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

No branches or pull requests

5 participants