Computer name causes certificate generation error on start

General
1

Hi,

first of all, I would like to thank the whole team for the great work they have done on this project.

without further ado, I want to expose a problem that I have three days ago when syncthing starts which I believe is caused by a character in the name of my PC (Vicenç-PC)

This log is constantly repeated and syncthing does not start:

[start] 00:45:03 INFO: syncthing v1.14.0 "Fermium Flea" (go1.16 windows-amd64) teamcity@build.syncthing.net 2021-02-26 12:21:13 UTC
[start] 00:45:03 INFO: Using large-database tuning
[4HCF3] 00:45:03 INFO: My ID: 4HCF36N
[4HCF3] 00:45:04 INFO: Single thread SHA256 performance is 595 MB/s using minio/sha256-simd (500 MB/s using crypto/sha256).
[4HCF3] 00:45:04 INFO: Hashing performance is 494.81 MB/s
[4HCF3] 00:45:04 INFO: Overall send rate is unlimited, receive rate is unlimited
[4HCF3] 00:45:04 INFO: Loading HTTPS certificate: x509: SAN dNSName is malformed
[4HCF3] 00:45:04 INFO: Creating new HTTPS certificate
[4HCF3] 00:45:04 INFO: Ready to synchronize "ORDENAR" (6fqmq-ufhzr) (sendreceive)
2021/03/05 00:45:04 connection doesn't allow setting of receive buffer size. See https://github.com/lucas-clemente/quic-go/wiki/UDP-Receive-Buffer-Size for details.
[4HCF3] 00:45:04 INFO: Stored folder metadata for "7eorr-fznfp" is 917h0m0s old; recalculating
[4HCF3] 00:45:04 WARNING: Failed starting API: create cert: x509: "Vicenç-PC" cannot be encoded as an IA5String
[4HCF3] 00:45:04 INFO: Loading HTTPS certificate: x509: SAN dNSName is malformed
[4HCF3] 00:45:04 INFO: Creating new HTTPS certificate
[4HCF3] 00:45:04 INFO: Failed initial scan of sendreceive folder "ORDENAR" (6fqmq-ufhzr)
[4HCF3] 00:45:04 INFO: QUIC listener ([::]:22000) starting
[4HCF3] 00:45:04 INFO: QUIC listener ([::]:22000) shutting down
[4HCF3] 00:45:04 INFO: TCP listener ([::]:22000) starting
[4HCF3] 00:45:04 WARNING: Starting API/GUI: create cert: x509: "Vicenç-PC" cannot be encoded as an IA5String
[4HCF3] 00:45:05 INFO: TCP listener ([::]:22000) shutting down

Thanks in advanced.

José Luis Martín.

2

Yeah, that’s a bug.

1 Like
3

Ok, thanks.

I look forward to the new version.

Until then, if I change my computer name, as a workaround, will it work ?

4

I just changed the the pc name and it is working correctly.

Thanks again to all team members for such awesome project.

2 Likes