Use Lisar with your browser

Start with the device you are using

A browser name does not determine the VPN protocol. On Windows, macOS, Linux, iPhone, iPad or Android, configure a supported connection for the operating system. Browser requests then follow the routes available to that device, subject to any proxy, split-tunnel or separate relay configuration.

Chrome, Edge and Brave

Start the VPN outside the browser, confirm it is connected, then open a new page. You do not need to import a Lisar .ovpn file into these browsers. A browser proxy extension or a separately enabled browser VPN can change where traffic exits, so check those features if the result differs from your device connection.

Keep organizational browser policies intact on a managed computer. If a work proxy is required, ask its administrator how it should interact with your personal VPN.

Firefox

Firefox can use system proxy settings, a manual proxy or an automatic proxy configuration. Those settings are separate from the VPN on your computer. If other applications work but Firefox does not, inspect its connection settings for a stale proxy or an extension controlling the connection.

Do not paste a Lisar VPN server address into the HTTP or SOCKS proxy fields. A VPN profile is not a browser proxy configuration. Mozilla's connection settings guide explains where the controls are in current Firefox versions.

Safari on Mac, iPhone and iPad

Use the relevant macOS or iOS and iPadOS setup guide. Safari does not import a Lisar profile file as a browser extension. A separate relay, proxy or route configuration can affect the address a website sees; compare those settings when diagnosing an unexpected result.

Check the route, not just the browser window

1. Confirm the VPN is connected in the app, operating system or router.
2. Open a page and check that name resolution and browsing work. If you use an IP-check service, compare the result with the exit expected for your active profile.
3. If one browser differs, check its proxy, secure DNS, extensions and any separate VPN or relay feature.
4. Disconnect the VPN deliberately when finished and verify the connection state again after changing networks.

Browser secure DNS may use a resolver different from the one selected by your VPN profile. This can affect profile-dependent DNS features such as eligible-plan DNS AdBlock; it does not by itself prove that all browsing traffic bypasses the VPN. Review the complete route before drawing that conclusion.

Private windows and browser-only protection

Incognito or private browsing changes what the browser keeps locally; it does not create a VPN tunnel or make you anonymous to websites. Signing into an account can still identify you. A browser-only proxy may cover a different scope from a device VPN, so do not infer protection for other apps from a working browser alone.

For a television or console, check the device guide before choosing a compatible client or router connection. A compatible router connection may route traffic from devices without a compatible client through Lisar. It depends on the router's VPN client support and routing configuration.

Official platform references

• Mozilla: Firefox connection settings
• Mozilla: DNS over HTTPS protection levels
• Apple: iCloud Private Relay
• Google: what Incognito mode does

More setup help