# Problem Every time there is a login form of `login.example.com`, I a warning against `login.example.com` making access to apps and services on devices connected to my local network. # Expectation The warning should either not appear, or report the addon as being the source of the connection. # Correlation Everytime I get the drop-down from the bitwarden addon, I can see the connections being made to the self-hosted `remote.vpn.domain.name` in the network panel of the devtools, while at the same time having a drop-down warning. Note, the connection are coming through successfully even if blocked. # Setup Today I have the following setup: I have a tailscale connection under the `domain.name` domain. - One computer named `remote` which host vaultwarden behind nginx, and uses let's encrypt with DNS challenges to provide HTTPS connections. - One computer named `client` uses firefox with the bitwarden addon. The bitwarden addon is configured to use the `remote.vpn.domain.name` computer.
Bug 1984359 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
# Problem Every time there is a login form of `login.example.com`, I a warning against `login.example.com` making access to apps and services on devices connected to my local network. # Expectation The warning should either not appear, or report the addon as being the source of the connection. # Correlation Everytime I get the drop-down from the bitwarden addon, I can see the connections being made to the self-hosted `remote.vpn.domain.name` in the network panel of the devtools, while at the same time having a drop-down warning. Note, the connection are coming through successfully even if blocked. # Setup Today I have the following setup: I have a tailscale connection under the `domain.name` domain. - One computer named `remote` (100.64.0.17) which host vaultwarden behind nginx, and uses let's encrypt with DNS challenges to provide HTTPS connections. - One computer named `client` (100.64.0.11) uses firefox with the bitwarden addon. The bitwarden addon is configured to use the `remote.vpn.domain.name` computer.
# Problem Every time there is a login form of `login.example.com`, I get a warning against `login.example.com` making access to apps and services on devices connected to my local network. # Expectation The warning should either not appear, or report the addon as being the source of the connection. # Correlation Everytime I get the drop-down from the bitwarden addon, I can see the connections being made to the self-hosted `remote.vpn.domain.name` in the network panel of the devtools, while at the same time having a drop-down warning. Note, the connection are coming through successfully even if blocked. # Setup Today I have the following setup: I have a tailscale connection under the `domain.name` domain. - One computer named `remote` (100.64.0.17) which host vaultwarden behind nginx, and uses let's encrypt with DNS challenges to provide HTTPS connections. - One computer named `client` (100.64.0.11) uses firefox with the bitwarden addon. The bitwarden addon is configured to use the `remote.vpn.domain.name` computer.