guardianproject / guardianproject/orbot-android

[BUG] Orbot fails to bootstrap - "Failed to find node for hop #1"

Open
#1,699 1 comment 0 reactions 0 assignees View on GitHub
Bug
Dominant language
Kotlin
Stars
3.5k
Forks
485
Avg merge
2d 14h
Merged PRs (30d)
24

Description

**Description:**
- Device: [realme 10 pro]
- Android Version: [Android 16]
- Orbot Version: [v17.9.4 BETA 1 (tor 0.4.9.6.2)]

**Problem:**
Orbot stuck at bootstrap. Repeatedly shows:
- Failed to find node for hop 1
- "DANGEROUS_SOCKS" warnings
- Circuit timeout after 120 seconds

**Tried:**
- Multiple bridge configurations (obfs4, snowflake,)
- Clearing data and reinstalling
- Different networks (WiFi/Mobile)

**Logs:**
[Message (STATUS_CLIENT): WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=95.85.16.212:443
NOTICE: Failed to find node for hop #1 of our path. Discarding this circuit.
Message (STATUS_CLIENT): WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=95.85.16.212:443
NOTICE: Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Message (STATUS_CLIENT): WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=159.203.148.75:443
NOTICE: Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up.
NOTICE: Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
NOTICE: Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
NOTICE: Failed to find node for hop #1 of our path. Discarding this circuit.]

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.