Discovery server changes

(Jakob Borg) #1

I have a server migration going on which necessitated a move of discovery-1 from my own hardware to the cloud. The intention was for this not to be user visible. However in that maneuver I noticed that the server had a certificate that needed changing for technical reasons (RSA to ECDSA), which means it gets a new ID. Given that I’ve given it a new name as well so that it doesn’t get hammered by clients that can anyway not talk to it.

I’ve pushed a new commit to update the default discovery set in Syncthing, which will be in the 0.14.7 release. In the meantime all existing clients will run just fine with two out of three servers.

The change, for the interested, becomes:

Removed:

  • https://discovery-v4-1.syncthing.net/v2/?id=SR7AARM-TCBUZ5O-VFAXY4D-CECGSDE-3Q6IZ4G-XG7AH75-OBIXJQV-QJ6NLQA (194.126.249.5, Sweden)
  • https://discovery-v6-1.syncthing.net/v2/?id=SR7AARM-TCBUZ5O-VFAXY4D-CECGSDE-3Q6IZ4G-XG7AH75-OBIXJQV-QJ6NLQA (2001:470:28:4d6::5, Sweden)

Added:

  • https://discovery-v4-4.syncthing.net/v2/?id=LYXKCHX-VI3NYZR-ALCJBHF-WMZYSPK-QG6QJA3-MPFYMSO-U56GTUK-NA2MIAW) (95.85.19.244, NL)
  • https://discovery-v4-4.syncthing.net/v2/?id=LYXKCHX-VI3NYZR-ALCJBHF-WMZYSPK-QG6QJA3-MPFYMSO-U56GTUK-NA2MIAW (2a03:b0c0:0:1010::4ed:3001, NL)
0 Likes

(Jakob Borg) closed #2

This topic was automatically closed after 7 days. New replies are no longer allowed.

0 Likes