You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Unable to set encryption settings within adguard and hass (could be port configuration in the addon configuration?
error message:
2024/09/04 09:58:04.922744 [error] POST myhass.mydomain.com /control/tls/configure: starting forwarding dns server: could not reconfigure the server: configuring listeners: listening on tls addr 192.168.0.3:3853: listen tcp 192.168.0.3:3853: bind: address already in use
same error with all other ports tried: 443 (which is understandably why it would fail), 447, 3843, 853, 3853, 784, 3784
Expected behavior
able to access adguard encryption configuration through one of the encrypted ports 853/784 or 3853/3784/3443
Actual behavior
once the encryption settings are set (ports, cert, etc) adguard crash and wont restart - solution so far is uninstall and start again with the setup, I lost count of how many times I have done this (past 2 or 3 weeks trying every combination of ports as per expected behavior comment)
Steps to reproduce
upgraded Adguard addon, (about 1 or 2 months ago)
there would be new option under Encryption settings (check box for plain DNS):
Enable Encryption & Enable plain DNS
setup:
due to erros and adguard not starting, decided to uninstall the addon and re-install after the upgrade
under Set Upstream DNS to:
tls://..."cloudflare.blabla..
https://..."cloudflare.blabla..
under Encryption settings:
check both "enable encryptions and plan DNS
set cert file path to ssl file and got "This is a valid RSA private key" message
if I leave the ports blank (all 3 of them) adguard continues to work normal
if I set the ports to their corresponding https/443 tls/853 and QUIC/784.. i get an error message saying ports already in use
If I add a 3 in front of all ports 3443 + 3853 + 3784...I still get the same error
I tried entering just the TLS port 3853 and 853 with same result, error message:
2024/09/04 09:58:04.922744 [error] POST myhass.mydomain.com /control/tls/configure: starting forwarding dns server: could not reconfigure the server: configuring listeners: listening on tls addr 192.168.0.3:3853: listen tcp 192.168.0.3:3853: bind: address already in use
Proposed changes
Instructions call for the ports to be set, however, I was unable to find within the configuration of the addon an option to set the ports (I believe the prior version had it? unknown)
PS problem may be between the screen and the chair and I cant figure it out.... however, I have spent about 2 weeks thinkering, installing and uninstalling more times that I can keep count and decided to run a version in docker from a diff computer in the meantime - however, I like my adguard within hass ..any help appreciated...
The text was updated successfully, but these errors were encountered:
There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!
Problem/Motivation
Unable to set encryption settings within adguard and hass (could be port configuration in the addon configuration?
error message:
2024/09/04 09:58:04.922744 [error] POST myhass.mydomain.com /control/tls/configure: starting forwarding dns server: could not reconfigure the server: configuring listeners: listening on tls addr 192.168.0.3:3853: listen tcp 192.168.0.3:3853: bind: address already in use
same error with all other ports tried: 443 (which is understandably why it would fail), 447, 3843, 853, 3853, 784, 3784
Expected behavior
able to access adguard encryption configuration through one of the encrypted ports 853/784 or 3853/3784/3443
Actual behavior
once the encryption settings are set (ports, cert, etc) adguard crash and wont restart - solution so far is uninstall and start again with the setup, I lost count of how many times I have done this (past 2 or 3 weeks trying every combination of ports as per expected behavior comment)
Steps to reproduce
upgraded Adguard addon, (about 1 or 2 months ago)
there would be new option under Encryption settings (check box for plain DNS):
Enable Encryption & Enable plain DNS
setup:
due to erros and adguard not starting, decided to uninstall the addon and re-install after the upgrade
under Set Upstream DNS to:
tls://..."cloudflare.blabla..
https://..."cloudflare.blabla..
under Encryption settings:
check both "enable encryptions and plan DNS
set cert file path to ssl file and got "This is a valid RSA private key" message
if I leave the ports blank (all 3 of them) adguard continues to work normal
if I set the ports to their corresponding https/443 tls/853 and QUIC/784.. i get an error message saying ports already in use
If I add a 3 in front of all ports 3443 + 3853 + 3784...I still get the same error
I tried entering just the TLS port 3853 and 853 with same result, error message:
2024/09/04 09:58:04.922744 [error] POST myhass.mydomain.com /control/tls/configure: starting forwarding dns server: could not reconfigure the server: configuring listeners: listening on tls addr 192.168.0.3:3853: listen tcp 192.168.0.3:3853: bind: address already in use
Proposed changes
Instructions call for the ports to be set, however, I was unable to find within the configuration of the addon an option to set the ports (I believe the prior version had it? unknown)
PS problem may be between the screen and the chair and I cant figure it out.... however, I have spent about 2 weeks thinkering, installing and uninstalling more times that I can keep count and decided to run a version in docker from a diff computer in the meantime - however, I like my adguard within hass ..any help appreciated...
The text was updated successfully, but these errors were encountered: