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.
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.
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
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
