Dashy in bridge network can't access to a domaine with access control (on Synology)

[MilesTEG1]

Hello @Lissy93
I'm using Dashy for several months now, and I'm happy to use it :D Thanks for your work 👍🏻

I see recently that you added this option :

It works fine for an access with https://ip_service:port.

But it doesn't work for another type of access : https://router.my_domaine.tld (so with 443 port) when I have restricted access for this domaine :

• it's unavailable oustide my LAN
• it's available throught my VPN server on my router (Syno RT2600AC)
• it's available inside my LAN with AdGuard Home rewriting the URL to 192.168.x.y (witch is my NAS IP).
  (I have set up a virtual IP address in order to let my NAS access to adguard Home, so normaly the containers too...)

On DSM, I set Access Control Profile for https://router.my_domaine.tld (and some other like https://dsm.my_domaine.tld).
I put my LANs IP CIDR : 192.168.2.0/24
I put my VPN IP CIDR : 192.168.2.10/24
I put the Dashy container IP : 172.28.0.2

But Dashy can't access to the domaine name... :

I don't know why...
Because dashy can access to my vaultwarden vault (but this one is without access control).
So Dash can access to AdGuard Home, I see it in AdG journal request...

Do you have an idea on with IP I can try to let Dashy check the status of my services domaine name ?

Thanks in advance :)

[Lissy93]

Hmm that's weird, are these services accesible from where your hosting Dashy? All the status checking happens within your network, so this should work.
It's likley an authorization, cors, or missing protocol error. What result do you get when you manually call the endpoint? Here's a troubleshooting guide which should help.

[MilesTEG1]

Hmm that's weird, are these services accesible from where your hosting Dashy? All the status checking happens within your network, so this should work.
I'm hosting Dashy in Docker on my NAS Synology, and DSM is obviously on this NAS too :)
The router not, but it get the same error.
I can access both of them from my computer.

It's likley an authorization, cors, or missing protocol error. What result do you get when you manually call the endpoint?
What do you mean ?

Here's a troubleshooting guide which should help.
I didn't understand everything, but I found a workaround with Status Check URL property by filling it with the LAN IP of my services and its port.

If I found another way, I'll let you know.
Thanks for your help :)