WebTunnel: Cannot confirm reachability on ORPort

Support Relay Operator
1

I recently set up a WebTunnel, but I noticed that the console kept spamming reachability errors.

I have allowed the orport through my firewall, made sure to add it to the docker compose file as well, yet it still complains about reachability

The tunnel works just fine if I connect with it, although it does not appear on the metrics website, and the bridge url has no information just says no resources for the given id

I do see some relays try to visit /tor/keys/fp/LONG-ID but thats apparently a 404

1 Like
2

Welcome VasilisTheChu :slight_smile:

Which instruction did you use?

What are the exact errors in the console? (Make sure to obfuscate IPv4 and/or IPV6 before posting)

ORPort does not need to be reacheable…

Sometimes you just need to wait a little more until it is picked up here:

→ https://onionoo.torproject.org/details?lookup=$hashed_fingerprint
→ https://bridges.torproject.org/status?id=$hashed_fingerprint

1 Like
3

Webtunnel Bridge use port 443 with a webserver in front.

There is no need to open the OR port, it only has to be accessible via 443

Make sure you have the following parameters in the configuration In addition to the nickname, etc. It’s not immediate, but in a couple of hours at most you should see your Bridge in the metrics if you search for it by nickname.

BridgeRelay 1
PublishServerDescriptor 1
ORPort 127.0.0.1:auto
AssumeReachable 1
ExtORPort auto
1 Like
4

Sorry for the late response, I apparently did not enable notifications and got busy

The one here Tor Project | WebTunnel Bridge using docker

Mar 25 14:49:10.000 [warn] Your server has not managed to confirm reachability for its ORPort(s) at IPv4:port. Relays do not publish descriptors until their ORPort and DirPort are reachable. Please check your firewalls, ports, address, /etc/hosts file, etc.

Mar 25 15:29:59.000 [notice] Unable to find IPv6 address for ORPort port. You might want to specify IPv4Only to it or set an explicit address or set Address. [60 similar message(s) suppressed in last 3540 seconds]

Mar 25 15:46:01.000 [warn] Received http status code 404 ("Not found") from server 192.42.116.203:9002 while fetching "/tor/keys/fp/SomeHash".

I have waited like 24 hours and it is still not showing up

I am using the premade docker container… i assume this is all setup for me no?

1 Like
5

This part it’s for the FrontEnd it’s ok

Ok my bad then sorry, I tried the official Container and I don’t receive this messages. It seems more a Middle Relay Docker Image.

Are you using the official Docker Setup Guide?

https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/webtunnel/-/raw/main/release/container/docker-compose.yml

Source:

1 Like
6

Yeah thats the one im using

1 Like