What to do if my extension is gray?
If the Dashlane extension in your browser is unable to connect, this will result in a grayed out impala icon.
The most common reason to investigate is your firewall and/or anti-virus application settings. Some network proxies and Virtual Private Networks can also keep the extension from connecting.
Firewalls, anti-virus software, network proxies and virtual private networks are very commonly the cause of connection problems with the Dashlane extension in your browser.
You can use the following guides to help you configure your applications and extensions in order to establish the connection with the Dashlane extension.
If you use none of these software, or if the guides below did not help, please refer to this article.
Also note that if are prompted to manually pair the Dashlane application and its extensions, but for whatever reason do not finalize this pairing, this will also cause your extension icon to be gray. In this case, simply quitting and reopening your browser will trigger the pairing process again.
Proxies and Firewalls
macOS proxy settings
To make sure that local connections are not blocked on 127.0.0.1 by a proxy on your Mac:
Go to your System Preferences and select Network.
In the Network pane, select your primary network interface (typically Wi-Fi, or Ethernet if you have a wired connection).
Click the Advanced button in the lower right corner of the pane, and select the Proxies tab.
In the list on the left, enable Web Proxy (HTTP).
In the Bypass proxy settings for these Hosts & Domains area, click to the right of the existing text, and type a comma followed by 127.0.0.1.
If Secure Web Proxy (HTTPS) is also checked:
- Select it.
- Click to the right of the existing text in the Bypass proxy settings for these Hosts & Domains area.
- Type a comma followed by 127.0.0.1 (as above).
Click the OK button to save your changes.
Windows firewall and proxy settings
If you are using the Windows firewall:
In your firewall configuration, please add the following ports to the exceptions list:
Please make sure that the following processes are allowed (“whitelisted”) by your firewall:
If you are using a proxy to connect to the Internet:
Open the Internet Options control panel.
Select the Connections tab, then click the LAN settings button.
Enable the Bypass proxy server for local addresses option, then click the Advanced button.
Under Exceptions, add 127.0.0.1 to the list of exceptions.
Click the OK button to close each of the dialog boxes.
Additional notes on configuring the proxy:
- If you are using a Firefox proxy extension, you may need to also configure it appropriately.
- If you are using a command-line switch with Chrome to access your proxy, you can add the following to the end of the command to bypass the proxy: -proxy-bypass-list="localhost;127.0.0.1".
AVG AntiVirus LinkScanner Surf-Shield might keep the Dashlane extension from connecting.
To avoid this, disable the Surf-Shield feature by following the steps below:
Use the AVG icon in the Windows system tray (notification area) to open the AVG Anti-Virus main window.
Click Options at the top right and then select Advanced settings.
Expand the Web Browsing Protection section and select LinkScanner Surf-Shield.
Disable (uncheck) the Enable Surf-Shield option.
Click OK to save the changes.
If prompted, click the Yes button at the prompt from User Account Control.
ESET NOD32 Antivirus
ESET NOD32 Antivirus needs to be configured to allow the browser extension to access the local 127.0.0.1 IP address (127.0.0.1, or localhost, is a special IP address used by computers to refer to themselves).
Open ESET NOD32. Press F5 or go to Setup and Advanced setup.
Select WEB AND EMAIL. In the PROTOCOL FILTERING section, click the Edit button next to Excluded applications.
Click the Add button at the bottom left of the window and select C:\USERS\...\DASHLANE.EXE in the list of applications. Click OK to add it. Repeat these steps for C:\USERS\...\DASHLANEPLUGIN.EXE. Then, exit this window by clicking OK.
In the PROTOCOL FILTERING section, now click the Edit button next to Excluded IP addresses (as shown in step 2). Click the Add button at the bottom left of the window and type 127.0.0.1 in the field before clicking OK. Then, you can exit the Excluded IP addresses setup by clicking OK.
Now select Web access protection in WEB AND EMAIL. Click the Edit button next to Address list in the URL ADDRESS MANAGEMENT section.
Select List of allowed addresses in the list and click the Edit button at the bottom left of the window.
Below the list, click the Add button and type in 127.0.0.1* (be sure to include the asterisk after the “1”) before clicking OK to add it.
Close all ESET NOD32 windows by clicking OK in order to save the changes.
If you still experience problems, ESET’s knowledge base contains an article that may help, "How do I exclude certain files or folders from Real-time scanning (4.x)".
Kaspersky Internet Security
It has been reported that Kaspersky anti-virus may block the communication between the application and the extension.
Here is how you can configure it to allow the communication:
Open Kaspersky main window and go to Settings.
Select the Additional tab and then Threats and Exclusions.
On the next window, select Configure exclusions. On the next page, click the Add button.
In the File or folder field, type : %AppData%\Dashlane. Leave all the Protection components checked and click Save.
Go back to the Threats and Exclusion settings and select Specify trusted applications (as shown in step 3).
Find DashlanePlugin.exe in the Information not available section and click Next. If you can't find it in the list, click Browse at the bottom left of the window and go find it in C:\Users\%Username%\AppData\Roaming\Dashlane.
Check Do not scan all traffic as well as Only for specified IP addresses and type 127.0.0.1, 188.8.131.52 in the following field. Then check Only for specified ports and type 11456, 15674, 17896, 21953, 32954 in the field. To finish, click Add.
Go back to Trusted applications and repeat the procedure for Dashlane.exe (as shown in steps 6 to 8). Do the same for Firefox.exe and/or Chrome.exe.
Close Kaspersky and relaunch your browser.
If it still doesn't work and if you enabled the Anti-Banner feature, please go back to the settings and select Protection. Then scroll down and click Anti-Banner.
On the following page, please click on Configure allowed URLs. On the next page, click the Add button.
Type 127.0.0.1 in the field and click the Add button. Then try restarting your browser again.
If it still doesn't work, please go back to the settings and select Additional and click on Network.
On this page, you need to select either Do not scan encrypted connections or Scan encrypted connections upon request from protection components.
Close Kaspersky and restart your browser. The Dashlane extension should now work properly.
Third party extension
We have discovered that disabling Ad Muncher allows the Dashlane browser extension to work properly. Here is how you can configure Ad Muncher to keep using it while using Dashlane:
Close all web browser windows.
Open Ad Muncher.
Select the Options tab and then the Filter Targets tab.
In the Filter targets dropdown menu, select My filter targets.
In the My filter targets area, paste the following text (as shown above):
Click the Apply button to save your changes.
Close the Ad Muncher window and relaunch your browsers.
If Dashlane stopped working in Firefox and if NoScript is installed in your browser, please follow the instructions below to add an exception to NoScript and allow Dashlane.
Open the settings in NoScript → Options → Advanced → ABE.
Select the SYSTEM ruleset.
Insert the following rule at the very beginning of the text box:
# Dashlane exception
Site http://127.0.0.1:11456 http://127.0.0.1:15674 http://127.0.0.1:17896 http://127.0.0.1:21953 http://127.0.0.1:32934
It will look like this on Windows:
And on macOS:
Lastly, restart your browser and the Dashlane extension will start working.
If you can't find your application above, no worries, all you need to do is configure it with a few simple rules:
- You need to allow Dashlane.exe, DashlanePlugin.exe and your web browsers to connect to localhost or 127.0.0.1.
- You need to allow communication on ports 11456, 15674, 17896, 21953 and 32934. If needed, you can allow all ports but it is preferable to limit to these specific ones.
- Add '%appdata%\Dashlane\DashlanePlugin.exe' to the exceptions list
- It’s often best to reboot to ensure the settings take effect.
If you manage to have it working, it would be great if you could send us your configuration and a few screenshots by clicking the "contact us" button below so we can add your program to the list above. If you still need help, please use the same button to let us know and we will do our best to help you.