Solved by Gus Edit: changed to functional but cant connect still TUNNEL: dysfunctional; Error: timed out waiting for bridge descriptor

[agiteg]

Hello,

• Debian 12 stable + regular kernel Linux freya 6.1.0-10-amd64
  disabled ipv6*

• nginx-1.25.3 compiled with proxy site running /http2/3 /scout.x1studio.eu

• webtunnel with go1.21.3

• Tor 0.4.8.7

• Torrc:
  BridgeRelay 1
  ORPort 127.0.0.1:auto
  AssumeReachable 1
  ServerTransportPlugin webtunnel exec /usr/local/bin/webtunnel
  ServerTransportListenAddr webtunnel 127.0.0.1:15000
  ServerTransportOptions webtunnel url=CYBERX dev - Freya|A7 INC.
  ExtORPort auto
  ContactInfo
  Nickname AgileTorTunnel
  SocksPort 0

[Wardz]

Getting same error on my freshly reinstalled obfs4 bridge even though it runs and connects just fine.
Anyone know if the statuscheck website itself is broken? Tormetrics shows it as running too.

[agiteg]

Hm text changed to functional, but that tbb tunnel bridge dont works still .

[gus]

Have you tried to connect to your bridge using TB 13? Can you paste your Tor Browser logs?

[agiteg]

Hello Gus,

Yes, I use latest stable 13.0.1

Tbb log:

[gus]

When you built your bridge line, did you copy the right fingerprint?

[agiteg]

0.0
Gus, right !

Tbb running, Im connected, super

Only metrics show up red dot, but there’s time lag, I think
metrics.torproject.org/rs.html#details/25A6360C1FF4640B54D2A54A683F8A64F04AF5C1

[gus]

@agiteg

Only metrics show up red dot, but there’s time lag, I think

You can ignore the metrics status until we fix this issue: 'Running' flag for counting bridges and network size (#318) · Issues · The Tor Project / Network Health / Team · GitLab.

[agiteg]

Looks like my tunnel is really fast