I got my bridge back online. Turns out I had to set a static NAT address with port forwarding which I've never had to do before. Thanks all!!<br><br><br><br><br><br><br>-------- Original Message --------<br>On May 10, 2020, 7:56 PM, < lists@for-privacy.net> wrote:<blockquote class="protonmail_quote"><br><p dir="ltr">On <a href="tel:0805202019">08.05.2020 19</a>:39, Anonforpeace wrote:</p>
<p dir="ltr">&gt; I have the port forwarded. I've also noticed that the advertised<br>
&gt; bandwidth is only 248 KiB/s on the metrics page. This is a first and<br>
&gt; I'm not sure how to raise the bandwidth.</p>
<p dir="ltr">I think Advertised Bandwidth on a bridge can be ignored.<br>
My bridge is alone on a bar metal server with 1 GBit/s port, same<br>
hardware as the relays. (Relays = 2 tor-instances pro server)</p>
<p dir="ltr"><a href="https://metrics.torproject.org/rs.html#search/TorOrDie4privacyNET">https://metrics.torproject.org/rs.html#search/TorOrDie4privacyNET</a><br></p>
<p dir="ltr">--<br>
&#9584;_&#9583; Ciao Marco!</p>
<p dir="ltr">Debian GNU/Linux</p>
<p dir="ltr">It's free software and it gives you freedom!<br>
_______________________________________________<br>
tor-relays mailing list<br>
<a href="mailto:tor-relays@lists.torproject.org">tor-relays@lists.torproject.org</a><br>
<a href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays">https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays</a><br>
</p>
</div>