I had to rebuild my VPS today. Before doing so, I copied off everything I thought I needed to rebuild my bridges. Following the rebuild, the bridges appear to start correctly, according to both the logs and https://metrics.torproject.org/rs.html#search/OhNoAnotherBridge. However attempting to connect via the tor browser from my home system just hangs.
The ports on the VPS are open. I can see an ESTABLISHED connection from home, but the browser just hangs throwing out this: [WARN] Proxy Client: unable to connect to aaa.bbb.ccc.ddd:443 ("general SOCKS server failure")
Not sure what to check next.
On Mon, Feb 08, 2021 at 06:58:55PM -0800, Eddie wrote:
Following the rebuild, the bridges appear to start correctly, according to both the logs and https://metrics.torproject.org/rs.html#search/OhNoAnotherBridge. However attempting to connect via the tor browser from my home system just hangs.
The ports on the VPS are open. I can see an ESTABLISHED connection from home, but the browser just hangs throwing out this: [WARN] Proxy Client: unable to connect to aaa.bbb.ccc.ddd:443 ("general SOCKS server failure")
Not sure what to check next.
It looks like the "vanilla ORPort" part of your bridge works (I just bootstrapped my Tor through it to confirm), but your obfs4 port is busted somehow: https://bridges.torproject.org/status?id=8BBAB62EA65E47CDF204E3D795DAD12E504... https://lists.torproject.org/pipermail/tor-relays/2021-January/019221.html
I wonder if, when you restored things, you also restored the obfs4 keys?
It looks like OhNoAnotherBridge80 is doing better? https://bridges.torproject.org/status?id=B080140DC1BAB5B86D1CE5A4CA2EF64F202...
--Roger
Ha. I copied the complete keys directory from my old configuration to the new, hoping everything would be the same. But I didn't realise that the cert used in the connection string would now be different. Using the new cert and original fingerprint I can now connect over the port 80 bridge. Is there any way to revert back to the original cert, so that the folks who already have the bridge configured can use it as they always have.
Let me look at what might be wrong with the 443 port, but I did exactly the same "shift and drop" technique for both the bridges.
Cheers.
On 2/8/2021 10:30 PM, Roger Dingledine wrote:
On Mon, Feb 08, 2021 at 06:58:55PM -0800, Eddie wrote:
Following the rebuild, the bridges appear to start correctly, according to both the logs and https://metrics.torproject.org/rs.html#search/OhNoAnotherBridge. However attempting to connect via the tor browser from my home system just hangs.
The ports on the VPS are open. I can see an ESTABLISHED connection from home, but the browser just hangs throwing out this: [WARN] Proxy Client: unable to connect to aaa.bbb.ccc.ddd:443 ("general SOCKS server failure")
Not sure what to check next.
It looks like the "vanilla ORPort" part of your bridge works (I just bootstrapped my Tor through it to confirm), but your obfs4 port is busted somehow: https://bridges.torproject.org/status?id=8BBAB62EA65E47CDF204E3D795DAD12E504... https://lists.torproject.org/pipermail/tor-relays/2021-January/019221.html
I wonder if, when you restored things, you also restored the obfs4 keys?
It looks like OhNoAnotherBridge80 is doing better? https://bridges.torproject.org/status?id=B080140DC1BAB5B86D1CE5A4CA2EF64F202...
--Roger
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
This e-mail was checked for spam by the freeware edition of CleanMail. The freeware edition is restricted to personal and non-commercial use. You can remove this notice by purchasing a commercial license: http://antispam.byteplant.com/products/cleanmail/index.html
OK, I *CAN* connect to the 443 port bridge using the new cert and the original fingerprint, just like port 80. So I'm not sure why the bridge status page reports what it does.
So, my question is still, is there a way to get my new configuration to rebuild itself to use the previous certs.
Cheers.
On 2/8/2021 10:30 PM, Roger Dingledine wrote:
On Mon, Feb 08, 2021 at 06:58:55PM -0800, Eddie wrote:
Following the rebuild, the bridges appear to start correctly, according to both the logs and https://metrics.torproject.org/rs.html#search/OhNoAnotherBridge. However attempting to connect via the tor browser from my home system just hangs.
The ports on the VPS are open. I can see an ESTABLISHED connection from home, but the browser just hangs throwing out this: [WARN] Proxy Client: unable to connect to aaa.bbb.ccc.ddd:443 ("general SOCKS server failure")
Not sure what to check next.
It looks like the "vanilla ORPort" part of your bridge works (I just bootstrapped my Tor through it to confirm), but your obfs4 port is busted somehow: https://bridges.torproject.org/status?id=8BBAB62EA65E47CDF204E3D795DAD12E504... https://lists.torproject.org/pipermail/tor-relays/2021-January/019221.html
I wonder if, when you restored things, you also restored the obfs4 keys?
It looks like OhNoAnotherBridge80 is doing better? https://bridges.torproject.org/status?id=B080140DC1BAB5B86D1CE5A4CA2EF64F202...
--Roger
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
This e-mail was checked for spam by the freeware edition of CleanMail. The freeware edition is restricted to personal and non-commercial use. You can remove this notice by purchasing a commercial license: http://antispam.byteplant.com/products/cleanmail/index.html
tor-relays@lists.torproject.org
-
Eddie -
Roger Dingledine