You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If needed, edit URL so it doesn't include a protocol (e.g. example.com instead of https://example.com)
Click on open URL button
The URL in the browser is https:/ (missing a /)
Expected Result
The URL should start with https:// not https:/
Actual Result
https:/ instead of https://. The protocol in the URL is missing the second /.
Screenshots or Videos
No response
Additional Context
No response
Build Version
2025.1.0 (19622)
What server are you connecting to?
US
Self-host Server Version
No response
Environment Details
Version: 2025.1.0 (19622)
📱 google Pixel 7 🤖 15@35 📦 prod-fdroid
local
Issue Tracking Info
I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.
The text was updated successfully, but these errors were encountered:
It is especially apparent with the DuckDuckGo browser. You don't quite see it in Chromium- and Firefox-based browsers as it seems that those have mechanisms to handle the missing /.
Thank you for your report. I was able to reproduce this behaviour and have flagged it to the Engineering department.
Please feel free to post additional information, such as screenshots or a screen video recordings, if you wish.
Steps To Reproduce
https:/
(missing a/
)Expected Result
The URL should start with
https://
nothttps:/
Actual Result
https:/
instead ofhttps://
. The protocol in the URL is missing the second/
.Screenshots or Videos
No response
Additional Context
No response
Build Version
2025.1.0 (19622)
What server are you connecting to?
US
Self-host Server Version
No response
Environment Details
Version: 2025.1.0 (19622)
📱 google Pixel 7 🤖 15@35 📦 prod-fdroid
local
Issue Tracking Info
The text was updated successfully, but these errors were encountered: