On Friday, May 8, 2020 at 7:39 PM, Anonforpeace <anonforpeace@xxxxxxxxxxxxxx> wrote:
I have the port forwarded. I've also noticed that the advertised bandwidth is only 248 KiB/s on the metrics page.
This is a first and I'm not sure how to raise the bandwidth. Could this be what's causing it to stay offline??
No. The advertised bandwidth tells you how much traffic you were able to handle in the last week.
For bridges the advertised bandwidth doesn't influence how much traffic you receive.
If you were offline for a week and your relay is still not reachable from the outside that's the reason why your
advertised bandwidth remains low.
Can you share the log lines that show your issue?
Are you able to run a "normal" web service on that computer that is accessible from the internet?
-------- Original Message --------
On May 8, 2020, 12:35 PM, Paul Geurts wrote:
Option: Dynamic internal ip address so the FW rule does point to the right internal ip address?
Machine has been off for a week so the lease could be expired.
Apologies for the length but detail is important. My bridge pc's internal power supply had to be replaced,
and was down for a week. After the replacement, I restarted the daemon and the tor service. Everything
seemed normal except that it's not reachable from outside. No configurations have been changed. The only
difference I see is a message in the log indicating that the network speed has changed/slowed down. The forwarded
port in the router is the same. The torrc file has not changed. I can surf the web. Literally the only change is the
replaced power supply. Any ideas?
Thanks