private discovery server, remote error: tls: no application protocol

Support
1

Hi Support,

Here I am after a lot of troubleshoot, try and errors.

I am trying the current setup :

  • private discovery server
  • hosted syncthing server
  • client synthing on my local network

I am using an NSX gateway on VMware for the hosted environment

Here for the syncthing server status:

SyncthingServer_DiscoveryConnection
SyncthingServer_DiscoveryConnection883Ă—173 7.44 KB
SyncthingServer_DiscoveryStatus

Here for the syncthing client status:

SyncthingClient_DiscoveryConnection
SyncthingClient_DiscoveryConnection855Ă—41 1.86 KB
SyncthingClient_DiscoveryStatus

nmap test on my public ip

PORT STATE SERVICE 8443/tcp open https-alt

PORT STATE SERVICE 22000/tcp open snapenetio

I have try with and without the syncthing public relays as well

I have put down all 3 Windows firewalls of the setup such as :

  • discover server
  • syncthing server
  • syncthing client

The discovery server is running on Windows, with the certificates generated by the application

I am running version 1.27.5 of syncthing

I have rebuild the complete 2 times without any more success, more precisely, same result

I have also asked 2 colleague to install the syncthing client with the same error for them also

I have looked upon some post/documentation from syncthing and that type of error could occured because of the certificate but now I’m not sure it is about that because of the following:

  • the syncthing server connect without any issue to the discovery server
  • i have rebuild the syncthing discovery 2 times, each time with a brand new directory and certs, basically, a fresh install

I’m using syncthing to create a proof of concept at our company where it’s going to be used to help us leverage the sync abilities of the product and host one of our home application.

I would appreciate any help and be very responsive about it because at this point in time, there’s isn’t much that i know of that I didn’t tried.

I will also continu my investigation using Wireshark to see if I can catch anything with that

Thank you all for your time in advance :slight_smile:

EDIT:

I have tried to add the port 21027 to my NAT configuration and the firewall as well, open, in destination to both the sync server and the discovery server

2

The “remote error: tls: …” means the other side is returning the error in question. I can’t say why, you’ll have to ask that proxy thing.

3

When you say the “other side” you mean, server side ? How come the server would throw the error to the syncthing client and not the syncthing server?

4

“Other side” from the point of view of the Syncthing discovery client that is showing the error – which, since this is a TLS error, is the handshake with the “NSX gateway” as I understand your setup.

5

Hi,

just to clarify the NSX Gateway is the “software” used on VMWare Cloud Director for the NAT Gateway and Firewall

image
image1044Ă—506 28.7 KB

Are you saying there’s something to be configured in the NSX gateway in order to import or accept the cert.pem generated by the syncthing server?

Because as I am reading the documentation that I’ve found that may be related to what you’re saying, I will review it and get back with a status here

Thanks a lot for the direction

6

I know nothing about NSX, but “remote error: whatever” means the other side reported an error and troubleshooting needs to continue on the other side. That’s all.

1 Like
7

Update and possible resolution :

I have set up a VM ubuntu on AWS (amazon web services) and opened the required ports and everything worked like a charm.

I have set up a VM ubuntu on the same environment used previously in this setup on VMWare Cloud Director, behind the NAT gateway (NSX) and turns out that the cert validation is blocked by the gateway and isn’t done on the OS level of things.

So basically, our setup will be moved to either Azure Microsoft, AWS or Google Cloud Provider

again, thanks for all your help @calmh

Cheers