github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-03-13 13:44:36 -05:00
Code Issues 144 Packages Projects Releases 116 Wiki Activity

Android App Ignores Ports in Hostnames #1370

New Issue
Closed
opened 2025-11-26 22:46:33 -06:00 by GiteaMirror · 18 comments
GiteaMirror commented 2025-11-26 22:46:33 -06:00
Owner
Copy Link

Originally created by @gregg098 on GitHub (Oct 29, 2021).

Steps To Reproduce

  1. Add a site with a hostname and a port and set the match to "Host"

For example, for my Synology NAS (Diskstation), a local domain in Bitwarden that works fine on Windows is:
http://diskstation.services.lan:5000 (Host Matching)

  1. Open http://diskstation.services.lan:5000 on Chrome on Android
  2. Bitwarden will not find any matches.
  3. Manually search for "diskstation", select the proper entry. Then get popup to autofill, autofill and save (I think that's the wording), etc.
  4. If I hit "autfill and save," it fills in the user/pass fields and moves on.
  5. Now, my Diskstation site in Bitwarden has two sites:

This will now find the site in BW every time, but now all my other home services on the *.services.lan domain will also have a "Diskstation" entry, which I was trying to avoid.

Expected Result

Expect auto search to be able to find the correct site just as it would in Windows

Actual Result

Many home services are the exact same domain, just different ports. Instead of having to scroll through a giant list of them, I set each entry to "Host" so that it matches everything exactly. No issues with this approach in Windows, but Android never finds the BW entry and wants a basic domain stripped of ports.

Screenshots or Videos

No response

Additional Context

No response

Operating System

Android

Operating System Version

11

Device

Samsung Galaxy S21+

Build Version

2.14.0 (3977)

Beta

  • Using a pre-release version of the application.
Originally created by @gregg098 on GitHub (Oct 29, 2021). ### Steps To Reproduce 1) Add a site with a hostname and a port and set the match to "Host" For example, for my Synology NAS (Diskstation), a local domain in Bitwarden that works fine on Windows is: http://diskstation.services.lan:5000 (Host Matching) 2) Open http://diskstation.services.lan:5000 on Chrome on Android 3) Bitwarden will **not** find any matches. 4) Manually search for "diskstation", select the proper entry. Then get popup to autofill, autofill and save (I think that's the wording), etc. 5) If I hit "autfill and save," it fills in the user/pass fields and moves on. 6) Now, my Diskstation site in Bitwarden has two sites: - http://diskstation.services.lan:5000 (host) - http://diskstation.services.lan (default match) This will now find the site in BW every time, but now all my other home services on the *.services.lan domain will also have a "Diskstation" entry, which I was trying to avoid. ### Expected Result Expect auto search to be able to find the correct site just as it would in Windows ### Actual Result Many home services are the exact same domain, just different ports. Instead of having to scroll through a giant list of them, I set each entry to "Host" so that it matches everything exactly. No issues with this approach in Windows, but Android never finds the BW entry and wants a basic domain stripped of ports. ### Screenshots or Videos _No response_ ### Additional Context _No response_ ### Operating System Android ### Operating System Version 11 ### Device Samsung Galaxy S21+ ### Build Version 2.14.0 (3977) ### Beta - [ ] Using a pre-release version of the application.
GiteaMirror added the bug label 2025-11-26 22:46:33 -06:00
GiteaMirror commented 2025-11-26 22:46:34 -06:00
Author
Owner
Copy Link

@Sim0nW0lf commented on GitHub (Nov 11, 2021):

I am having the same and another related issue!
The browser Extentions work well, only the app has this problem...

I set my whole app to "Host", just like my browser extentions and saw other problems as well.
If I take your site as example:
http://diskstation.services.lan will work just fine
http://www.services.lan does not work

That means if the app is in "Host" mode, then no website without custom subdomain or with port will work.
(Not sure if that is entirely true, didn't test enough but that's my theory)
Hopefully that will be fixed! Thanks for your awesome development! :)

@Sim0nW0lf commented on GitHub (Nov 11, 2021): I am having the same and another related issue! The browser Extentions work well, only the app has this problem... I set my whole app to "Host", just like my browser extentions and saw other problems as well. If I take your site as example: http://diskstation.services.lan will work just fine http://www.services.lan does not work That means if the app is in "Host" mode, then no website without custom subdomain or with port will work. (Not sure if that is entirely true, didn't test enough but that's my theory) Hopefully that will be fixed! Thanks for your awesome development! :)
GiteaMirror commented 2025-11-26 22:46:34 -06:00
Author
Owner
Copy Link

@Sim0nW0lf commented on GitHub (Nov 19, 2021):

Everything is working for me now!
Running the Bitwarden App Beta V2.14.2

Maybe the stable app only has this issue? I don't know.
Is it working for you as well?

@Sim0nW0lf commented on GitHub (Nov 19, 2021): Everything is working for me now! Running the Bitwarden App Beta V2.14.2 Maybe the stable app only has this issue? I don't know. Is it working for you as well?
GiteaMirror commented 2025-11-26 22:46:34 -06:00
Author
Owner
Copy Link

@gregg098 commented on GitHub (Nov 21, 2021):

Signed up for beta, but didnt get an app update. Still have the same issue on stable.

@gregg098 commented on GitHub (Nov 21, 2021): Signed up for beta, but didnt get an app update. Still have the same issue on stable.
GiteaMirror commented 2025-11-26 22:46:34 -06:00
Author
Owner
Copy Link

@Sim0nW0lf commented on GitHub (Nov 21, 2021):

Which app version are you running at the moment?
It will probably take a while for the update! If you get it, I hope it will work :)

@Sim0nW0lf commented on GitHub (Nov 21, 2021): Which app version are you running at the moment? It will probably take a while for the update! If you get it, I hope it will work :)
GiteaMirror commented 2025-11-26 22:46:34 -06:00
Author
Owner
Copy Link

@gregg098 commented on GitHub (Nov 21, 2021):

Version: 2.14.2 (4005)

@gregg098 commented on GitHub (Nov 21, 2021): Version: 2.14.2 (4005)
GiteaMirror commented 2025-11-26 22:46:35 -06:00
Author
Owner
Copy Link

@lcasale commented on GitHub (Mar 27, 2022):

I have this issue on 2.16.2

@lcasale commented on GitHub (Mar 27, 2022): I have this issue on 2.16.2
GiteaMirror commented 2025-11-26 22:46:36 -06:00
Author
Owner
Copy Link

@Sim0nW0lf commented on GitHub (Mar 27, 2022):

For me it is also broken again.

URI Match Detection "base domain" works
but
URI Match Detection "host" which I am using is not working

@Sim0nW0lf commented on GitHub (Mar 27, 2022): For me it is also broken again. URI Match Detection "base domain" works but URI Match Detection "host" which I am using is not working
GiteaMirror commented 2025-11-26 22:46:36 -06:00
Author
Owner
Copy Link

@redxtech commented on GitHub (Jul 11, 2022):

I am still getting this issue on version 2022.6.1 (4795).

I'm wondering if this is at all on the radar of the team?

@redxtech commented on GitHub (Jul 11, 2022): I am still getting this issue on version 2022.6.1 (4795). I'm wondering if this is at all on the radar of the team?
GiteaMirror commented 2025-11-26 22:46:36 -06:00
Author
Owner
Copy Link

@KevoM commented on GitHub (Jan 31, 2023):

Same on android 12 and Bitwarden version 2023.1.0

@KevoM commented on GitHub (Jan 31, 2023): Same on android 12 and Bitwarden version 2023.1.0
GiteaMirror commented 2025-11-26 22:46:36 -06:00
Author
Owner
Copy Link

@Kartoffl commented on GitHub (Apr 25, 2023):

same on android 12, bitwarden version 2023.3.2 (6098)

@Kartoffl commented on GitHub (Apr 25, 2023): same on android 12, bitwarden version 2023.3.2 (6098)
GiteaMirror commented 2025-11-26 22:46:37 -06:00
Author
Owner
Copy Link

@2PieceCombo commented on GitHub (Jul 30, 2023):

I have an issue that seems to be along these same lines.

I have a service running on https://10.13.1.100
My entry was set to: https://10.13.1.100/login
Browser works fine, but on mobile is says "no item found for 10.13.1.100" (using android btw)
Ive tried changing the URI match to base domain, host, and starts with, none of them worked on mobile.
If i change the entry to https://10.13.1.100/ it still does not work, but if I remove the / at the end, it suddenly does recognize it. However I run dozens of internal services on the same IP but different ports. The android version completely ignores entries if there is anything following the IP address, regardless if it actually matches.

This means that I can't use any of my saved logins on my internal services, unless I manually search for them. This is incredibly frustrating because mobile is already the least convenient to use, and this issues makes it nearly unusable.

@2PieceCombo commented on GitHub (Jul 30, 2023): I have an issue that seems to be along these same lines. I have a service running on https://10.13.1.100 My entry was set to: https://10.13.1.100/login Browser works fine, but on mobile is says "no item found for 10.13.1.100" (using android btw) Ive tried changing the URI match to base domain, host, and starts with, none of them worked on mobile. If i change the entry to https://10.13.1.100/ it still does not work, but if I remove the / at the end, it suddenly does recognize it. However I run dozens of internal services on the same IP but different ports. The android version completely ignores entries if there is anything following the IP address, regardless if it actually matches. This means that I can't use any of my saved logins on my internal services, unless I manually search for them. This is incredibly frustrating because mobile is already the least convenient to use, and this issues makes it nearly unusable.
GiteaMirror commented 2025-11-26 22:46:37 -06:00
Author
Owner
Copy Link

@jufy111 commented on GitHub (Sep 13, 2023):

I'm also having the same issue. Autofill works without issue on desktop but on mobile it won't auto fill HOST:IP correctly, regardless of the match settings.

@jufy111 commented on GitHub (Sep 13, 2023): I'm also having the same issue. Autofill works without issue on desktop but on mobile it won't auto fill HOST:IP correctly, regardless of the match settings.
GiteaMirror commented 2025-11-26 22:46:37 -06:00
Author
Owner
Copy Link

@Meinnick commented on GitHub (Sep 14, 2023):

same on android 13, bitwarden version 2023.8.0 (7466)

@Meinnick commented on GitHub (Sep 14, 2023): same on android 13, bitwarden version 2023.8.0 (7466)
GiteaMirror commented 2025-11-26 22:46:37 -06:00
Author
Owner
Copy Link

@weilah commented on GitHub (Nov 24, 2023):

I'm facing the same problem on Android (bitwarden version 2023.10.0 (8257)). I tried chrome and brave with same results. The port gets somehow lost in the way when trying to match URIs. I tried "starts with..." and "host", but bitwarden only sees the local IP and not the port.

If I press add login then the URI is shown without the port

@weilah commented on GitHub (Nov 24, 2023): I'm facing the same problem on Android (bitwarden version 2023.10.0 (8257)). I tried chrome and brave with same results. The port gets somehow lost in the way when trying to match URIs. I tried "starts with..." and "host", but bitwarden only sees the local IP and not the port. If I press add login then the URI is shown without the port
GiteaMirror commented 2025-11-26 22:46:38 -06:00
Author
Owner
Copy Link

@sv87411 commented on GitHub (Nov 26, 2023):

Same issue here on 2023.10.0 (8257) (Android 13).

With multiple home hosted apps often with the same home domain/host hosting apps on multiple ports with multiple logins Bitwarden needs to recognise the port as a part of the URI.

In the Bitwarden docs it says port is considered to be part of the host for matching purposes so why doesn't it behave like this on Android?

Update: Oh. Just realised this was raised in 2021. No chance of this getting resolved then. Looking at alternative Bitwarden options now as this is a deal breaker for me.

@sv87411 commented on GitHub (Nov 26, 2023): Same issue here on 2023.10.0 (8257) (Android 13). With multiple home hosted apps often with the same home domain/host hosting apps on multiple ports with multiple logins Bitwarden needs to recognise the port as a part of the URI. In the Bitwarden docs it says port is considered to be part of the host for matching purposes so why doesn't it behave like this on Android? Update: Oh. Just realised this was raised in 2021. No chance of this getting resolved then. Looking at alternative Bitwarden options now as this is a deal breaker for me.
GiteaMirror commented 2025-11-26 22:46:38 -06:00
Author
Owner
Copy Link

@TheColtron commented on GitHub (Apr 10, 2024):

Exact same in v2024.3.0. I've had this problem for ages, and only finally tried to pin down the problem today.

No issues with the browser extension, and this happens on all auto fill modes (inline and whatever the normal one is called).

Here's how it works. URIs like http://{IP}:{Port}:

  • Fail to auto fill on Host
  • Fail to auto fill on Starts With
  • Fail to auto fill on Regex
  • Successfully auto fills when using base domain

Why is it a problem?:

  • Saving a login on a http://{IP}:{Port} page (via the + button or "Auto fill & save") doesn't capture the port in the URI. Users will then edit the URI and add the port to fix this, but some users will also change the match type at the same time (since hostname matching, according to its name, should not be used in this case).
  • The docs describe the extension behavior, but the mobile app behaves differently

So hopefully that helps point in the right direction of a fix. For anyone having this issue, you can workaround it by using base domain matching on the full socket address. I've only been on mobile since writing, so I don't know if this will mess up matching on the extension version though.

@TheColtron commented on GitHub (Apr 10, 2024): Exact same in v2024.3.0. I've had this problem for ages, and only finally tried to pin down the problem today. No issues with the browser extension, and this happens on all auto fill modes (inline and whatever the normal one is called). Here's how it works. URIs like `http://{IP}:{Port}`: - Fail to auto fill on Host - Fail to auto fill on Starts With - Fail to auto fill on Regex - Successfully auto fills when using base domain Why is it a problem?: - Saving a login on a `http://{IP}:{Port}` page (via the + button or "Auto fill & save") doesn't capture the port in the URI. Users will then edit the URI and add the port to fix this, but some users will also change the match type at the same time (since hostname matching, according to its name, should not be used in this case). - The docs describe the extension behavior, but the mobile app behaves differently So hopefully that helps point in the right direction of a fix. For anyone having this issue, you can workaround it by using base domain matching on the full socket address. I've only been on mobile since writing, so I don't know if this will mess up matching on the extension version though.
GiteaMirror commented 2025-11-26 22:46:39 -06:00
Author
Owner
Copy Link

@MossyGreen commented on GitHub (Jun 4, 2024):

Same issue here on v2024.4.0

It's disappointing to see that the issue has persisted since 2021

@MossyGreen commented on GitHub (Jun 4, 2024): Same issue here on v2024.4.0 It's disappointing to see that the issue has persisted since 2021
GiteaMirror commented 2025-11-26 22:46:39 -06:00
Author
Owner
Copy Link

@vvolkgang commented on GitHub (Jun 20, 2024):

Issue migrated to https://github.com/bitwarden/mobile/issues/1620

@vvolkgang commented on GitHub (Jun 20, 2024): Issue migrated to https://github.com/bitwarden/mobile/issues/1620
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
app:authenticator
app:password-manager
bug
bug-passkey
customer-support
duplicate
enhancement
good first issue
help wanted
needs-reply
needs-response
pull-request
Mirrored from GitHub Pull Request
 question
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/android#1370
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?