Bad certificate, after upgrading one side to 1.8

Support
1

After months of everything working fine, I upgraded one of my nodes to 1.8.0 (via the plugin manager on FreeNAS).

The other side is a Mac, running 1.7.0.

Now I see this on the 1.8.0 side: " 2020-08-18 20:05:43: Bad certificate from atto at 172.16.0.2:38865-198.245.49.122:22067/relay-server/TLS1.3-TLS_AES_128_GCM_SHA256: x509: certificate relies on legacy Common Name field, use SANs or temporarily enable Common Name matching with GODEBUG=x509ignoreCN=0"

and it won’t sync. Any ideas?

2

I see this is in https://github.com/syncthing/syncthing/issues/6867 but it’s not clear what to actually DO about it. Is syncthing simply broken and unusable until 1.9.0 comes out, or what?

3

Unfortunately I guess they built with Go 1.15 which doesn’t work on that version. (I’m surprised it isn’t also panicking due to the QUIC incompatibility.) You can downgrade or complain to the packager. :confused:

Or set GODEBUG=x509ignoreCN=0 somewhere in the startup.

4

Thanks for letting me know. JIRA filed with iXsystems

5

And fixed locally by adding setenv GODEBUG x509ignoreCN=0 to the jail’s /etc/csh.cshrc

6

Can confirm adding

setenv GODEBUG x509ignoreCN=0

to the /etc/csh.cshrc worked.

7

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.