Skip to content
View in the app

A better way to browse. Learn more.

Enpass Discussion Forum

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

BunnyStrider

Members
  • Joined

  • Last visited

  1. Subject: Fix found (in my case): WSL virtual adapter on the SERVER breaks discovery Same symptom as OP: desktop client stuck on "Looking up for servers..." forever, refresh unclickable. Server = Windows 11 Pro, client = Windows 10 Pro, both on latest Enpass, same Wi-Fi SSID/band, both network profiles Private. What I ruled out first: TCP path was fine: Test-NetConnection <server-ip> -Port <sync-port> succeeded from the client, even with firewalls on (after allowing the three Enpass entries — Enpass, mDNS discovery, wifisyncserver_bin — on Private) OS-level mDNS was fine: ping <servername>.local resolved from the client Firewalls fully disabled on both machines: still spinning So multicast and unicast both worked, but Enpass's own discovery didn't. The fix: the server had a vEthernet (WSL (Hyper-V firewall)) adapter active. I shut down WSL and disabled that adapter (elevated PowerShell): wsl --shutdown Disable-NetAdapter -Name "vEthernet (WSL (Hyper-V firewall))" Then fully quit and relaunch Enpass on the server (tray icon → quit — the restart matters, the server seems to bind interfaces at startup). Client discovered the server immediately after that. My guess is the Wi-Fi Sync server binds or advertises the WSL NAT interface (172.x) instead of the LAN interface, so clients either never hear the announcement or get an unreachable address. Note for others in this thread: disabling virtual adapters on the client didn't help me either — it had to be the server's virtual adapter, followed by an Enpass restart. Once a client is paired, sync keeps working even with WSL running again — discovery only matters at pairing time. Hope this helps someone. Enpass team: an interface-binding option (or just preferring the default-route interface) would fix this class of problem properly.
  2. I used wi-fi sync with all my devices instead, that's better than cloudsync anyway. I tried setting a drive backup, sharing it with my wife, putting a shortcut at the same location in her drive account that points back to my walletx file. When I log in in the android app on her phone with backup/vault set to google drive it says there are no passwords but there should be over 100. I also see no activity on her drive account...or mine for that matter. How do I share my currently backed-up-by-google-drive enpass personal account with my wife.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.