<html><head></head><body>Thanks for the prompt response. My apologies for the omission in the original post.<br>My relays are called 405test1 and 405test2.<br>Both relays are vm's on a proxmox server with the only difference in set up being port numbers. I have had both operating since July 2022 with no issues.<br>Thanks again! <br><br><div class="gmail_quote">On October 6, 2022 4:59:22 AM CDT, tor-relays-request@lists.torproject.org wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre dir="auto" class="k9mail">Send tor-relays mailing list submissions to<br> tor-relays@lists.torproject.org<br><br>To subscribe or unsubscribe via the World Wide Web, visit<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>or, via email, send a message with subject or body 'help' to<br> tor-relays-request@lists.torproject.org<br><br>You can reach the person managing the list at<br> tor-relays-owner@lists.torproject.org<br><br>When replying, please edit your Subject line so it is more specific<br>than "Re: Contents of tor-relays digest..."<br><br><br>Today's Topics:<br><br> 1. Re: Moving middle relays to bridges? (Chris)<br> 2. Consensus weight tanking (Me)<br> 3. Re: Consensus weight tanking (Georg Koppen)<br> 4. Re: many connections (Chris)<hr>Message: 1<br>Date: Wed, 05 Oct 2022 05:32:20 -0400<br>From: Chris <tor@wcbsecurity.com><br>To: tor-relays@lists.torproject.org<br>Subject: Re: [tor-relays] Moving middle relays to bridges?<br>Message-ID: <2d1975a2-6362-48d3-8dc3-05bd16797797@wcbsecurity.com><br>Content-Type: text/plain; charset="utf-8"<br><br>Bridges more or less function as guard relays except their IP addresses are not known. Having a bridge with an IP address that's already know somehow defeats the purpose.<br><br>As far as I'm concerned the list of relays should not be public. Only exit relays need to be known for liability reasons. Once we stop publishing IP addresses of relays, the need for bridges will be greatly reduced.<br><br>That being said, I believe if your relay is no longer a relay for a week, it will be removed from the public relay list. Not sure if it will be removed from the censors' list.<br>??<br><br><br>-------- Original Message --------<br>From: "Isaac Grover, Aileron I.T." <igrover@aileronit.com><br>Sent: Tue Oct 04 12:15:52 EDT 2022<br>To: "tor-relays@lists.torproject.org" <tor-relays@lists.torproject.org><br>Subject: [tor-relays] Moving middle relays to bridges?<br><br>Good morning,<br><br>According to tor metrics, there have been nearly three times the number of relays as bridges over the last three months so I would like to move my handful of middle relays to bridges. They will keep their same IP address. Is there a best practice with regards to doing this so the directories don't get confused?<br><br>Make your day great,<br>Isaac Grover<hr>tor-relays mailing list<br>tor-relays@lists.torproject.org<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>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <<a href="http://lists.torproject.org/pipermail/tor-relays/attachments/20221005/8da902a3/attachment-0001.htm">http://lists.torproject.org/pipermail/tor-relays/attachments/20221005/8da902a3/attachment-0001.htm</a>><hr>Message: 2<br>Date: Wed, 05 Oct 2022 10:07:32 -0500<br>From: Me <theyarewatching@disroot.org><br>To: tor-relays@lists.torproject.org<br>Subject: [tor-relays] Consensus weight tanking<br>Message-ID: <D028F9D8-5159-4904-832A-0E4F6A402022@disroot.org><br>Content-Type: text/plain; charset="utf-8"<br><br>Good day,<br>Not sure if this would be the proper avenue to pursue this. I operate a couple of middle relays from my home server. All seemed well until this morning. Three days ago one was promoted to guard status while the other lags behind. This morning I check the Tor metrics page and the consensus weight graphs on both relays have bottomed out. The other metrics do not have appeared to have remained normal for daily operations.<br>Any suggestions or input are greatly appreciated <br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <<a href="http://lists.torproject.org/pipermail/tor-relays/attachments/20221005/d0e51c9c/attachment-0001.htm">http://lists.torproject.org/pipermail/tor-relays/attachments/20221005/d0e51c9c/attachment-0001.htm</a>><hr>Message: 3<br>Date: Thu, 6 Oct 2022 08:02:51 +0000<br>From: Georg Koppen <gk@torproject.org><br>To: tor-relays@lists.torproject.org<br>Subject: Re: [tor-relays] Consensus weight tanking<br>Message-ID: <a774a7bc-162f-913d-e2c2-751b54bd8755@torproject.org><br>Content-Type: text/plain; charset="utf-8"; Format="flowed"<br><br>Me via tor-relays:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;">Good day,<br>Not sure if this would be the proper avenue to pursue this. I operate a couple of middle relays from my home server. All seemed well until this morning. Three days ago one was promoted to guard status while the other lags behind. This morning I check the Tor metrics page and the consensus weight graphs on both relays have bottomed out. The other metrics do not have appeared to have remained normal for daily operations.<br>Any suggestions or input are greatly appreciated<br></blockquote><br>My first idea would be sending you to the relay lifecycle blog post[1], <br>in particular Phase 3. But maybe we could look closer if you said which <br>relays you are running (and which are affected). :)<br><br>Georg<br><br>[1] <a href="https://blog.torproject.org/lifecycle-of-a-new-relay/">https://blog.torproject.org/lifecycle-of-a-new-relay/</a><br><br>-------------- next part --------------<br>A non-text attachment was scrubbed...<br>Name: OpenPGP_signature<br>Type: application/pgp-signature<br>Size: 833 bytes<br>Desc: OpenPGP digital signature<br>URL: <<a href="http://lists.torproject.org/pipermail/tor-relays/attachments/20221006/345261cc/attachment-0001.sig">http://lists.torproject.org/pipermail/tor-relays/attachments/20221006/345261cc/attachment-0001.sig</a>><hr>Message: 4<br>Date: Thu, 6 Oct 2022 05:47:18 -0400<br>From: Chris <tor@wcbsecurity.com><br>To: tor-relays@lists.torproject.org, Richie <richie@zuviel.org><br>Subject: Re: [tor-relays] many connections<br>Message-ID: <783f8f8a-cf2d-b289-1066-6ec31b8fbe98@wcbsecurity.com><br>Content-Type: text/plain; charset="us-ascii"<br><br>An HTML attachment was scrubbed...<br>URL: <<a href="http://lists.torproject.org/pipermail/tor-relays/attachments/20221006/291074b2/attachment.htm">http://lists.torproject.org/pipermail/tor-relays/attachments/20221006/291074b2/attachment.htm</a>><br>-------------- next part --------------<br>A non-text attachment was scrubbed...<br>Name: 0x6FF16D076C04AB67.asc<br>Type: application/pgp-keys<br>Size: 8757 bytes<br>Desc: not available<br>URL: <<a href="http://lists.torproject.org/pipermail/tor-relays/attachments/20221006/291074b2/attachment.key">http://lists.torproject.org/pipermail/tor-relays/attachments/20221006/291074b2/attachment.key</a>><hr>Subject: Digest Footer<hr>tor-relays mailing list<br>tor-relays@lists.torproject.org<br><a href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays">https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays</a><hr>End of tor-relays Digest, Vol 141, Issue 5<br>******************************************<br></pre></blockquote></div></body></html>