Hi,

So I had changed the listener port for obfs4, it's now 8181.

Upon running your steps, and systemctl status tor, it returns the following:

● tor.service - Anonymizing overlay network for TCP (multi-instance-master)
Loaded: loaded (/lib/systemd/system/tor.service; enabled; vendor preset: enabled)
Active: active (exited) since Tue 2023-02-28 05:42:48 UTC; 18s ago
Process: 15314 ExecStart=/bin/true (code=exited, status=0/SUCCESS)
Main PID: 15314 (code=exited, status=0/SUCCESS)

Feb 28 05:42:48 instance-1 systemd[1]: Starting Anonymizing overlay network for TCP (multi-instance-master)...
Feb 28 05:42:48 instance-1 systemd[1]: Started Anonymizing overlay network for TCP (multi-instance-master).

Will check it in a few hours, but is there a way to limit the bridge to only connections of a certain size? Thanks.

--Keifer

On Sun, Feb 26, 2023 at 3:16 AM <lists@for-privacy.net> wrote:

On Freitag, 24. Februar 2023 04:11:27 CET Keifer Bly wrote:
> Yes, the limit is 50GB per month, but for some reason the distribution
> mechanism is not updating and the bridge keeps going offline despite the
> new torrc.

What comes to my mind without logs (& your 'killall -HUP' of a systemd service
is not optimal), your wrong config (2x same Port) has maxed out 'Restart=on-
failure'.

Try:
~# systemctl stop tor
~# systemctl list-units --failed

if not zero than:
~# systemctl reset-failed
~# systemctl start tor

To see if the tor.service has finished successfully:
~# systemctl status tor

if not, read log:
journalctl -xe

--
╰_╯ Ciao Marco!

Debian GNU/Linux

It's free software and it gives you freedom!_______________________________________________
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays