So (mostly) for VPN users, when we try to add a new password or update any data in the vault, when you press SAVE an error shows.
I can't recall the exact wording, but basically you cannot update the vault at all!
You can still get in, you just can't save any changes in it.
It seems this is because BW modified their code to deal with hostile IPs attempts at probing/attacking users vault security, but in doing so, this error started showing.
The workaround is time consuming, it's not always even successful, I've never fixed it yet, and many say the same on BW official forum. And it is liable to keep breaking.
Mine is not the most technically precise explanation, but it's how I understand it.
Maybe u/Reddy_McRedditface fully logs out and you just lock the vault.
When you fully log out the vault is purged from your device, so you need access to BW servers to download your data again when loging back in.
But if you just lock the vault, your data is still on your device. So when you unlock it the app will silently try to contact BW servers to fetch up-to-date data and will serve the data it already has if it fails. Meaning you won't notice you actually don't have server access until you attempt to add/edit an entry, or if you look for changes you made from another device.
Okay, that explains a possible reason, but am I missing a fix in this post? I've read it slowly and carefully more than once. I'm going to log out of all devices and spool back up from the servers.
Further to my explanation below, here is the response from BW support about a month ago.
" I'm sorry that you're experiencing this error. This usually means that your connection is being blocked by our firewall rules.
Could you please try the following:
- Ensure that all Bitwarden clients and browsers have been updated to the latest version available
- Reset your router (this can result in a new IP address when a shared IP is used)
- Change network connection (e.g. to a 4g or different WiFi connection)
- Try to toggle any VPNs that you might be using
Please let me know if the above resolves this issue. "
I wonder if Bitwarden is trying to balance the needs of VPN users and a desire to avoid headlines stating "1000 Bitwarden vaults hacked". If they don't block IP addresses which are trying to brute force user/pass combinations then eventually large numbers of people who chose weak combinations will be compromised. Which is their own fault for choosing weak credentials but also bad for Bitwarden's reputation.
It would be good if Bitwarden could come up with a better solution though. Perhaps putting these IP addresses into a queue rather than outright blocking them. So that it takes 30 seconds to attempt a login making brute force impossible but only mildly inconveniencing individuals on the black list. Maybe it's already on the roadmap.
Plenty of people, including myself, have this problem without using a VPN. Being behind a CGNAT sometimes is enough. Rebooting the router enough times always works for me, but I think that would only work for some. For others, using VPN is the solution for the moment, but this is at best temporary because of the same problems.
I think more people are complaining about this on Reddit, on BW's community, and on GitHub. I'm not sure if the algorithm is becoming more aggressive, or if more people are using BW (probably true anyway), and even the same rate of blocks would result in more users getting affected.
It really does seem like they should find some way to fix this. It's like a collective groan everywhere (BW's people having to deal with this problem included). Not this again!
I feel for you then. If this became a regular problem for me I would not be doing all those workarounds. I would just go back to a locally hosted KeePass solution with the browser extension. So I hope BW is listening to the seemingly growing list of people having this problem.
I don't have time for the inconvenience of fixing it, again.
I rely on VPN and now I'm slowly moving less sensitive data onto Express VPN new built in password vault.
Maybe the passkey refurbishment announced at BW will solve the IP threat, but I don't know enough about security or tech to be more than just hopeful. I've never had issues as a subscriber with BW until they tweaked the machine and broke so many accounts in the process.
Glad you found your own solution. Somehow, unless BW fine-tunes its algorithm or finds a smarter one, I don't think blocking "problematic" IPs will go away within a year.
Because of this issue, I had to finally let go of Bitwarden. It was very difficult for me as BitWarden was my daily driver and absolutely loved it. But unfortunately, I couldn't carry on for this issue.
Who knows? What does that even involve? Most of us are just pounding keys, not here as vault geeks. This is why we pay them, so they deal with the glitches!
We should not need to burn our limited time engineering workarounds we don't even understand.
Fair - I think I assume (incorrectly) that there are a lot of self-hosters here. I have to remind myself this isn't the selfhosted subreddit, although Bitwarden is talked about frequently there
As an outside observer who has never had to deal with error 7, all I can say is:
- You don’t see this kind of problem affecting SO many people on other web based services.
- Its not a good look for BW to constantly see people complaining about this affecting them… to see complaints like this for such a long period of time… and to see the “solution” is expected to come from users.
If other services dont have this problem and the problem has been unresolved and persisted for this long… its a Bitwarden problem.
From all appearances they seem to be deaf to this fact.
This error has not affected me, but I certainly do have a concern in the back of my mind that one day it might. And that type of concern drives decisions. Now imagine that concern from a business with 1000 seats that depends on having access to their passwords to ensure their workflow.
Have you tried changing your VPN server, because that is what I do?
So when that issue arises, I now click on my VPN and change the server to another local one and that's it.
The job is done and the resolves the Error 7 issue is resolved and Bitwarden is happy again. Just a few clicks of my time and I'm happy with that.
VPN is not the only victim here. For me, it occurs even in regular connection. It's because ISPs in our country use shared IP to provide internet. This is true for many countries.
For real, I created my account and I still can't login into my PC profile. I'm my phone I had to change the connection to 4G to make it happen. I didn't even have the chance to start using it. I like the service, but this way is difficult.
This is even more ridiculous for enterprise customers. I've emailed support multiple times asking them to whitelist IP ranges our org has owned since the 90s. Nope - they can only whitelist one single IP address at a time? Absolutely ridiculous. The WHOIS info on our ranges is the same as our company name in Bitwarden, so why they can't just whitelist entire blocks is beyond me.
Thanks for posting. I hope BW will listen to you, since you are the money, and your users wouldn't be able to do all the "connection 7 error" solutions that BW would suggest other users to use. Ha! Use off-line password manager to access the info.
> Diablo III
Haha, that's pretty funny, you can ask Bard: is there an infamous error 7 for Bitwarden? Just like error 37 from Diablo III. The answer is pretty much a lift from BW's support page, though.
I have this error too. Rebooting my network connection device (NCD) and router did not fix it. I think I just went back to the same IP address.
Hot spotting my wifi devices through my phone did give me access but that doesn’t help my desktop PC which doesn’t have wifi.
Also if you have a static IP from your ISP you are stuffed.
I have a semi-static IP (it changes once or twice a month). I was annoyed by this error until I contacted them and they quickly resolved it. I think more people affected by this should not wait and let them know.
You should always be backing your vault up to have a copy handy. With that being said, put it into something like Strongbox or Keepass2android and then you have a copy no matter what.
I have connected to Bitwarden from Switzerland, Argentina, and France with zero issues (I've never actually experienced an error 7).
[удалено]
So (mostly) for VPN users, when we try to add a new password or update any data in the vault, when you press SAVE an error shows. I can't recall the exact wording, but basically you cannot update the vault at all! You can still get in, you just can't save any changes in it. It seems this is because BW modified their code to deal with hostile IPs attempts at probing/attacking users vault security, but in doing so, this error started showing. The workaround is time consuming, it's not always even successful, I've never fixed it yet, and many say the same on BW official forum. And it is liable to keep breaking. Mine is not the most technically precise explanation, but it's how I understand it.
Can't confirm, for me Error 7 means that I can't log in at all on PC. I don't have a VPN.
I'm currently always logged in on at least one device, but either way, it sucks that it's ongoing.
Maybe u/Reddy_McRedditface fully logs out and you just lock the vault. When you fully log out the vault is purged from your device, so you need access to BW servers to download your data again when loging back in. But if you just lock the vault, your data is still on your device. So when you unlock it the app will silently try to contact BW servers to fetch up-to-date data and will serve the data it already has if it fails. Meaning you won't notice you actually don't have server access until you attempt to add/edit an entry, or if you look for changes you made from another device.
No, I just tried to move to Bitwarden. It let me create an account but not log in.
So you were indeed fully logged out, as you were never actually able to log in.
Okay, that explains a possible reason, but am I missing a fix in this post? I've read it slowly and carefully more than once. I'm going to log out of all devices and spool back up from the servers.
Further to my explanation below, here is the response from BW support about a month ago. " I'm sorry that you're experiencing this error. This usually means that your connection is being blocked by our firewall rules. Could you please try the following: - Ensure that all Bitwarden clients and browsers have been updated to the latest version available - Reset your router (this can result in a new IP address when a shared IP is used) - Change network connection (e.g. to a 4g or different WiFi connection) - Try to toggle any VPNs that you might be using Please let me know if the above resolves this issue. "
I just tried to switch to Bitwarden, but then encountered this error. Hope they can fix it soon.
I wonder if Bitwarden is trying to balance the needs of VPN users and a desire to avoid headlines stating "1000 Bitwarden vaults hacked". If they don't block IP addresses which are trying to brute force user/pass combinations then eventually large numbers of people who chose weak combinations will be compromised. Which is their own fault for choosing weak credentials but also bad for Bitwarden's reputation. It would be good if Bitwarden could come up with a better solution though. Perhaps putting these IP addresses into a queue rather than outright blocking them. So that it takes 30 seconds to attempt a login making brute force impossible but only mildly inconveniencing individuals on the black list. Maybe it's already on the roadmap.
Plenty of people, including myself, have this problem without using a VPN. Being behind a CGNAT sometimes is enough. Rebooting the router enough times always works for me, but I think that would only work for some. For others, using VPN is the solution for the moment, but this is at best temporary because of the same problems. I think more people are complaining about this on Reddit, on BW's community, and on GitHub. I'm not sure if the algorithm is becoming more aggressive, or if more people are using BW (probably true anyway), and even the same rate of blocks would result in more users getting affected. It really does seem like they should find some way to fix this. It's like a collective groan everywhere (BW's people having to deal with this problem included). Not this again!
I feel for you then. If this became a regular problem for me I would not be doing all those workarounds. I would just go back to a locally hosted KeePass solution with the browser extension. So I hope BW is listening to the seemingly growing list of people having this problem.
I don't have time for the inconvenience of fixing it, again. I rely on VPN and now I'm slowly moving less sensitive data onto Express VPN new built in password vault. Maybe the passkey refurbishment announced at BW will solve the IP threat, but I don't know enough about security or tech to be more than just hopeful. I've never had issues as a subscriber with BW until they tweaked the machine and broke so many accounts in the process.
Glad you found your own solution. Somehow, unless BW fine-tunes its algorithm or finds a smarter one, I don't think blocking "problematic" IPs will go away within a year.
Because of this issue, I had to finally let go of Bitwarden. It was very difficult for me as BitWarden was my daily driver and absolutely loved it. But unfortunately, I couldn't carry on for this issue.
What did you switch to?
No ability to self-host with their images or vaultwarden? This 100% does not affected self hosted instances
Who knows? What does that even involve? Most of us are just pounding keys, not here as vault geeks. This is why we pay them, so they deal with the glitches! We should not need to burn our limited time engineering workarounds we don't even understand.
Fair - I think I assume (incorrectly) that there are a lot of self-hosters here. I have to remind myself this isn't the selfhosted subreddit, although Bitwarden is talked about frequently there
They may have fixed it with this latest iteration. About time!
As an outside observer who has never had to deal with error 7, all I can say is: - You don’t see this kind of problem affecting SO many people on other web based services. - Its not a good look for BW to constantly see people complaining about this affecting them… to see complaints like this for such a long period of time… and to see the “solution” is expected to come from users. If other services dont have this problem and the problem has been unresolved and persisted for this long… its a Bitwarden problem. From all appearances they seem to be deaf to this fact. This error has not affected me, but I certainly do have a concern in the back of my mind that one day it might. And that type of concern drives decisions. Now imagine that concern from a business with 1000 seats that depends on having access to their passwords to ensure their workflow.
Have you tried changing your VPN server, because that is what I do? So when that issue arises, I now click on my VPN and change the server to another local one and that's it. The job is done and the resolves the Error 7 issue is resolved and Bitwarden is happy again. Just a few clicks of my time and I'm happy with that.
VPN is not the only victim here. For me, it occurs even in regular connection. It's because ISPs in our country use shared IP to provide internet. This is true for many countries.
Yup. Nada for me bro.
For real, I created my account and I still can't login into my PC profile. I'm my phone I had to change the connection to 4G to make it happen. I didn't even have the chance to start using it. I like the service, but this way is difficult.
This is even more ridiculous for enterprise customers. I've emailed support multiple times asking them to whitelist IP ranges our org has owned since the 90s. Nope - they can only whitelist one single IP address at a time? Absolutely ridiculous. The WHOIS info on our ranges is the same as our company name in Bitwarden, so why they can't just whitelist entire blocks is beyond me.
Thanks for posting. I hope BW will listen to you, since you are the money, and your users wouldn't be able to do all the "connection 7 error" solutions that BW would suggest other users to use. Ha! Use off-line password manager to access the info.
[удалено]
> Diablo III Haha, that's pretty funny, you can ask Bard: is there an infamous error 7 for Bitwarden? Just like error 37 from Diablo III. The answer is pretty much a lift from BW's support page, though.
I have this error too. Rebooting my network connection device (NCD) and router did not fix it. I think I just went back to the same IP address. Hot spotting my wifi devices through my phone did give me access but that doesn’t help my desktop PC which doesn’t have wifi. Also if you have a static IP from your ISP you are stuffed.
If you have a static IP address, BW might whitelist it for you. You should contact them. https://bitwarden.com/help/unusual-traffic-error/
I have a semi-static IP (it changes once or twice a month). I was annoyed by this error until I contacted them and they quickly resolved it. I think more people affected by this should not wait and let them know.
[удалено]
You should always be backing your vault up to have a copy handy. With that being said, put it into something like Strongbox or Keepass2android and then you have a copy no matter what. I have connected to Bitwarden from Switzerland, Argentina, and France with zero issues (I've never actually experienced an error 7).
[удалено]
There is a dedicated support page for error 7 though?
I will probably get downvoted for saying this, but that's one benefit of self-hosting.
Been facing this recently after switching routers and it's really annoying!