Hello,
I am new to AMTM and am facing a problem that I do not understand and cannot solve.
Merlin: Current Version : 3004.388.5
amtm 4.2 FW
Diversion 5.0
Unbound 3.23
The "simple" installation of Unbound runs without errors.
The external traffic is also resolved without problems and the cache works as desired.
What no longer works, however, is the reverse proxy for internal, lan-only requests. Background: A Vaultwarden is running on a Synology (.49) , which should and is only accessible in the internal network.
After a long search, I was able to identify Unbound as the cause of the reverse proxy error. As soon as I deactivate Unbound, the internal reverse proxy resolution works as desired again.
Perhaps, a little naively, I thought I could exclude the internal domain address in unbound. But I haven't found anything on how to do that.
Probably that was the wrong way, but I don't know what to do right now, but I would like to use undbound; and understand where the error lies.
Support is very welcome! Thank you!
I am new to AMTM and am facing a problem that I do not understand and cannot solve.
Merlin: Current Version : 3004.388.5
amtm 4.2 FW
Diversion 5.0
Unbound 3.23
The "simple" installation of Unbound runs without errors.
The external traffic is also resolved without problems and the cache works as desired.
What no longer works, however, is the reverse proxy for internal, lan-only requests. Background: A Vaultwarden is running on a Synology (.49) , which should and is only accessible in the internal network.
After a long search, I was able to identify Unbound as the cause of the reverse proxy error. As soon as I deactivate Unbound, the internal reverse proxy resolution works as desired again.
Perhaps, a little naively, I thought I could exclude the internal domain address in unbound. But I haven't found anything on how to do that.
Probably that was the wrong way, but I don't know what to do right now, but I would like to use undbound; and understand where the error lies.
Support is very welcome! Thank you!
