Syncthing won't start...qtls.ClientSessionState not compatible with tls.ClientSessionState

Hello

I run Syncthing on Centos7 and today syncthing crashed and i cannot boot it back up.

Looking at the system logs, this is what i see…

Aug 20 15:50:54 production.brighter-ir.com systemd[1]: Started Syncthing - Open Source Continuous File Synchronization for root. Aug 20 15:50:54 production.brighter-ir.com syncthing[11513]: panic: qtls.ClientSessionState not compatible with tls.ClientSessionState Aug 20 15:50:54 production.brighter-ir.com syncthing[11513]: goroutine 1 [running]: Aug 20 15:50:54 production.brighter-ir.com syncthing[11513]: github.com/lucas-clemente/quic-go/internal/handshake.init.2() Aug 20 15:50:54 production.brighter-ir.com syncthing[11513]: /builddir/build/BUILD/syncthing/pkg/mod/github.com/lucas-clemente/quic-go@v0.17.3/internal/handshake/unsafe.go:26 +0x205 Aug 20 15:50:54 production.brighter-ir.com systemd[1]: syncthing@root.service: main process exited, code=exited, status=2/INVALIDARGUMENT Aug 20 15:50:54 production.brighter-ir.com systemd[1]: Unit syncthing@root.service entered failed state. Aug 20 15:50:54 production.brighter-ir.com systemd[1]: syncthing@root.service failed.

They built it wrong without testing, unfortunately. Use our binaries, or downgrade.

Thanks for the speedy response!

How can i downgrade? and will it affect the existing set-up?

I’m not sure, that’s a CentOS procedure. Downgrading might require resetting the database. Might be easier to just grab our binary for the same version from github. Hopefully once the package updates next time this will be sorted and you’ll be back on track.

Thanks a lot for you help!

Ran command to check my version which was 1.8, so got the binary for 1.8 from github but logs had “detected upgrade from 1.7 to 1.8” weirdly. Nevertheless all works fine!

1 Like

The same problem appears on my raspberry pi. But this seems to work.

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