Hello everyone.
I’v been dealing with the impossibility of running Syncthing-fork over OpenVPN. The details are here:
opened 05:25PM - 19 Jul 25 UTC
closed 09:38PM - 19 Jul 25 UTC
> > I tested 1.29.6.4 and obtained the same results described here:
> > [#957 (c… omment)](https://github.com/Catfriend1/syncthing-android/issues/957#issuecomment-2825552327)
> > There is no way to connect over OpenVPN.
> > Android side is connected through WiFi, data is off.
> > In the same scenario Syncthing 1.28.1 (last version, discontinued) auto connects and works fine.
>
> I tested syncthing-fork version 1.30.0.1 (f-droid) and obtained the same results as with 1.29.6.4. All firewalls where disabled on either side. Desktop syncthing used in the test is v1.29.6, Windows (64-bit Intel/AMD). Windows version is 10, Android OS version is 10. Android is connected to the vpn though wifi, and mobile data is off.
>
> Syncthing-fork does not connect over openvpn. On either side the errors are "i/o timeout" or "connection refused".
>
> With the same configuration, sycthing-fork connects immediately over the physical lan.
>
> Also, previous syncthing 1.28.1 (discontinued) connects fine in both scenarios. Openvpn is like the physical lan here, no difference between them for previous syncthing.
>
> Using PCAPdroid I was able to determine that syncthing-fork does generate a connection to the openvpn desktop side. The packets never make it through, though.
>
> Could it be that some how the packets that should go to the vpn are sent to the physical wifi lan and die there?
>
> It's a pity this problem still persists, since your version if far better than the discontinued one in every other aspect. I hope a solution will come up soon, before the old version falls into oblivion. I'll keep testing new versions and report here if anything different is found.
>
> Thanks and keep up the good work!
>
> I carried out some more tests.
>
> I tested syncthing-fork 1.28.1 to discard that the problem could have been introduced due to changes in native syncthing that only affect Android.
> I obtained the same results as with latest version: "connection refused" in Android side, "i/o timeout" in Windows side.
>
> Tracking packets in the network in Android, I also noticed that the original syncthing sends UDP packets to "x.y.z.255:21027" beeing "x.y.z" the physical lan, but also the openvpn lan.
> Syncthing-fork only sends those packets to the physical lan, ignoring the existance of the openvpn lan.
>
> I hope this helps.
>
_Originally posted by @stuser11 in [#957](https://github.com/Catfriend1/syncthing-android/issues/957#issuecomment-3092467401)_
Following up that issue, I tested Syncthing-fork over OpenVPN in the described conditions in a different Android setup in a revived old phone (LineageOS 18 - Android 11, with MicroG) and it worked fine.
So, I now blame my actual Android OS: Android 10, xiaomi.eu.
Has anybody had issues related to xiaomi ROMs, in particular xiaomi.eu ROMs?
Thanks, and special thanks to Catfriend for his work and for guiding me to isolating this problem. (I may be going back to Lineage in the near future…)
1 Like
Does your setup rely on local discovery or nat pmp?
Local discovery is on. No nat or global discovery. The OpenVPN lan has just two entities, the server and the client.
The addresses and port of client and server are manualy configured in the server and the client. Something like this:
In the OpenVPN server side (Windows): “tcp4://x.y.z.client:port, dynamic”
In the OpenVPN client side (Android): “tcp4://x.y.z.server:port, dynamic”
In discontinued syncthing with only “dynamic” in the server side, it works.
Local discovery will be fixed in a future release; but setting direct ip:port should be fine as you have it.
As a general debugging measure you could try to set up a different vpn. I’m running syncthing over Wireguard between my phone and my server and laptop. At least that could tell you if the issue is specific to OpenVPN or not.
1 Like
I’m happy to report that after reinstalling Android OS (same OS but this time google services replaced with microG), version 1.30.0.1 works fine over openvpn.
No idea what the problem could have been, but it is solved.
1 Like
system
(system)
Closed
September 18, 2025, 8:48pm
7
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.