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

dns over tls & https #64

Closed
stvnmbr1 opened this issue May 29, 2020 · 9 comments
Closed

dns over tls & https #64

stvnmbr1 opened this issue May 29, 2020 · 9 comments

Comments

@stvnmbr1
Copy link

is there a way to change the available ports to forward in the addon?
HTTPS 443 and 853 should be configurable.

I enabled dns over tls which causes the admin page to switch to the https port and actually has shut me out.

@addons-assistant
Copy link

👋 Thanks for opening your first issue here! If you're reporting a 🐛 bug, please make sure you include steps to reproduce it. Also, logs, error messages and information about your hardware might be useful.

@sinclairpaul
Copy link
Member

I think its likely you selected this:

image

Unfortunately that's a challenge (which we should probably look at), not knowing your OS/setup it would be difficult to help.

Only suggestion would be to uninstall and reinstall.

@stvnmbr1
Copy link
Author

stvnmbr1 commented May 29, 2020

haha yes i did indeed ..
thought this meant it redirects http requests from clients to https to internet nd such like the safesearch. so kinda screwed now unless i can edit the config manually from inside the container? this way i don't need to setup my filters nd such again.

i'm talking about the config tab / network in supervisor config addon where you can expose your ports from the container.
I would expose 443 and 853 to other not common use ports for outside access.

i just tried duplicating with exposed ports in portainer but doesn't want me to do it :(

any help on this would be greatly appreciated !

(i run hassio on debian buster with supervisor and 2x nginx )

@sinclairpaul
Copy link
Member

Edit /usr/share/hassio/addons/data/a0d7b954_adguard/adguard/AdGuardHome.yaml and set force_https key to false.

@stvnmbr1
Copy link
Author

ok that got me back in the admin console ;)
Thanks !

is there a way to add 443 and 853 to the exposed ports or are the exposed by default as the container uses host network in docker? don't know how the supervisor addons are setup, so kinda new to me

@sinclairpaul
Copy link
Member

Will look at how we deal with SSL, as there is nginx in the way, which will do the SSL for you. What's likely is that we just force remove the option, and leave the SSL down to ingress or the addon config.

It's likely we need to add 853 to the config as well. Are we good to close this for now?

@stvnmbr1
Copy link
Author

stvnmbr1 commented May 29, 2020

i don't mind the admin console not running https, as this won't be exposed and uses ingress in hassio.
Only access to the addon i need is through hassio.

dns over tls would be great as it only needs an extra port exposed in the config and is blocking me from going further.

I don't know if I can add this myself somewhere in the code or if this is a quick fix thing to add an extra port?
didn't see anything port-ish in dockerfile and duplicating the container wouldn't let me expose the ports

Edit:
can this be left open to track progress?

@sinclairpaul
Copy link
Member

Fixed via #67

@addons-assistant
Copy link

This thread has been automatically locked because it has not had recent activity. Please open a new issue for related bugs and link to relevant comments in this thread.

@addons-assistant addons-assistant bot locked as resolved and limited conversation to collaborators Jun 29, 2020
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

2 participants