Obfs4: dysfunctional Error: timed out waiting for bridge descriptor (again)

I’ve been running a bridge for a some time now. I reboot every month and it has never been easy to get the bridge up after that.

This time it is not any better. Checking the status of the bridge relay produces:

obfs4: dysfunctional Error: timed out waiting for bridge descriptor

There is a topic about this error message, but unfortunately without solution although it ended up working.

There is nothing strange in the log except that “Publishing server descriptor” takes minutes rather than seconds when the bridge ended up functional in the past.

Jan 10 22:34:45.000 [notice] Tor 0.4.7.10 opening log file.
Jan 10 22:34:45.347 [notice] We compiled with OpenSSL 1010111f: OpenSSL 1.1.1q  5 Jul 2022 and we are running with OpenSSL 1010111f: 1.1.1q. These two versions should be binary compatible.
Jan 10 22:34:45.358 [notice] Tor 0.4.7.10 running on Linux with Libevent 2.1.12-stable, OpenSSL 1.1.1q, Zlib 1.2.11, Liblzma N/A, Libzstd N/A and Unknown N/A as libc.
Jan 10 22:34:45.358 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://support.torproject.org/faq/staying-anonymous/
Jan 10 22:34:45.358 [notice] Read configuration file "/tmp/torrc".
Jan 10 22:34:45.365 [notice] Processing configuration path "/etc/tor/torrc" at recursion level 1.
Jan 10 22:34:45.366 [notice] Including configuration file "/etc/tor/torrc".
Jan 10 22:34:45.368 [notice] Based on detected system memory, MaxMemInQueues is set to 741 MB. You can override this by setting MaxMemInQueues by hand.
Jan 10 22:34:45.375 [notice] Opening Socks listener on 127.0.0.1:9050
Jan 10 22:34:45.376 [notice] Opened Socks listener connection (ready) on 127.0.0.1:9050
Jan 10 22:34:45.376 [notice] Opening OR listener on 0.0.0.0:29013
Jan 10 22:34:45.376 [notice] Opened OR listener connection (ready) on 0.0.0.0:29013
Jan 10 22:34:45.376 [notice] Opening Extended OR listener on 127.0.0.1:0
Jan 10 22:34:45.376 [notice] Extended OR listener listening on port 33843.
Jan 10 22:34:45.376 [notice] Opened Extended OR listener connection (ready) on 127.0.0.1:33843
Jan 10 22:34:46.000 [notice] Parsing GEOIP IPv4 file /usr/share/tor/geoip.
Jan 10 22:34:47.000 [notice] Parsing GEOIP IPv6 file /usr/share/tor/geoip6.
Jan 10 22:34:48.000 [notice] Configured to measure statistics. Look for the *-stats files that will first be written to the data directory in 24 hours from now.
Jan 10 22:34:48.000 [notice] Your Tor server's identity key  fingerprint is 'FortunaBridge *'
Jan 10 22:34:48.000 [notice] Your Tor bridge's hashed identity key  fingerprint is 'FortunaBridge *'
Jan 10 22:34:48.000 [notice] Your Tor server's identity key ed25519 fingerprint is 'FortunaBridge *'
Jan 10 22:34:48.000 [notice] You can check the status of your bridge relay at https://bridges.torproject.org/status?id=*
Jan 10 22:34:48.000 [notice] Bootstrapped 0% (starting): Starting
Jan 10 22:34:51.000 [notice] Starting with guard context "default"
Jan 10 22:35:36.000 [notice] Registered server transport 'obfs4' at '[::]:29014'
Jan 10 22:35:37.000 [notice] Bootstrapped 5% (conn): Connecting to a relay
Jan 10 22:35:37.000 [notice] Bootstrapped 10% (conn_done): Connected to a relay
Jan 10 22:35:37.000 [notice] Bootstrapped 14% (handshake): Handshaking with a relay
Jan 10 22:35:37.000 [notice] Bootstrapped 15% (handshake_done): Handshake with a relay done
Jan 10 22:35:37.000 [notice] Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits
Jan 10 22:35:37.000 [notice] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits
Jan 10 22:35:37.000 [notice] Bootstrapped 95% (circuit_create): Establishing a Tor circuit
Jan 10 22:35:38.000 [notice] Bootstrapped 100% (done): Done
Jan 10 22:35:38.000 [notice] Now checking whether IPv4 ORPort *:29013 is reachable... (this may take up to 20 minutes -- look for log messages indicating success)
Jan 10 22:35:44.000 [notice] Self-testing indicates your ORPort *:29013 is reachable from the outside. Excellent. Publishing server descriptor.
Jan 10 22:37:38.000 [notice] Performing bandwidth self-test...done.

I am running out of ideas. Who can help?

Today https://bridges.torproject.org/status reports that the bridge is functional. So I tried connecting to it myself and after a few failed attempts before getting the line right (even after reading all the manuals) the tor browser connected. Without changing anything. So after the next reboot, I’ll ignore a dysfunctional bridge for a few days.