isConnected failed: ETIMEDOUT (Connection timed out) #1765

Closed
opened 2025-11-26 22:57:34 -06:00 by GiteaMirror · 2 comments
Owner

Originally created by @Gooberpatrol66 on GitHub (Nov 15, 2023).

Steps To Reproduce

  1. enter email
  2. click selfhosted
  3. enter server
  4. click continue

Expected Result

Works, like in browser extension

Actual Result

Exception message: failed to connect to (port 443) from (port 46162) after 86400000ms: isConnected failed: ETIMEDOUT (Connection timed out)

Screenshots or Videos

No response

Additional Context

No response

Operating System

Android

Operating System Version

No response

Device

No response

Build Version

2023.10.0

Beta

  • Using a pre-release version of the application.
Originally created by @Gooberpatrol66 on GitHub (Nov 15, 2023). ### Steps To Reproduce 1. enter email 2. click selfhosted 3. enter server 4. click continue ### Expected Result Works, like in browser extension ### Actual Result Exception message: failed to connect to <server>(port 443) from <client> (port 46162) after 86400000ms: isConnected failed: ETIMEDOUT (Connection timed out) ### Screenshots or Videos _No response_ ### Additional Context _No response_ ### Operating System Android ### Operating System Version _No response_ ### Device _No response_ ### Build Version 2023.10.0 ### Beta - [ ] Using a pre-release version of the application.
GiteaMirror added the bug label 2025-11-26 22:57:34 -06:00
Author
Owner

@TroyBW commented on GitHub (Nov 18, 2023):

Hi there,

I attempted to reproduce your issue and was unable to do so. I think your error may be a network configuration issue, but it is hard to say for certain.

We use GitHub issues as a place to track bugs and other development related issues. If your issue persists, please write us back using our contact form, so we can continue troubleshooting: https://bitwarden.com/contact/

You can include a link to this issue in the message content.

Alternatively, you can also search for an answer in our help documentation (https://bitwarden.com/help/) or get help from other Bitwarden users on our community forums (https://community.bitwarden.com/c/support/).

The issue here will be closed.

Thanks!

@TroyBW commented on GitHub (Nov 18, 2023): Hi there, I attempted to reproduce your issue and was unable to do so. I think your error may be a network configuration issue, but it is hard to say for certain. We use GitHub issues as a place to track bugs and other development related issues. If your issue persists, please write us back using our contact form, so we can continue troubleshooting: https://bitwarden.com/contact/ You can include a link to this issue in the message content. Alternatively, you can also search for an answer in our help documentation (https://bitwarden.com/help/) or get help from other Bitwarden users on our community forums (https://community.bitwarden.com/c/support/). The issue here will be closed. Thanks!
Author
Owner

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

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

@vvolkgang commented on GitHub (Jun 20, 2024): Issue migrated to https://github.com/bitwarden/mobile/issues/2870
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/android#1765