Dear Joplin users,
I'm trying to sync my Joplin data to an IPv6 only sync target and Joplin alwasy takes the IPv4 information out of the DNS record.
My setup: portable Joplin v 2.9.17 on a windows 10 22H2 x64 system; the sync target is a Nextcloud 24.0.3 instance on a Ubuntu 20.0.4 LTS server with php 8.1.
As my provider changed to Deutsche Glasfaser who doesn't provide an IPv4 address I had to move my cloud to IPv6 - until that moment syncing to Nextcloud ran smooth since years.
When I now check the sync settings the system reports
Fehler. Bitte überprüfe, ob die URL, der Benutzername, das Passwort usw. korrekt sind und dass das Synchronisationsziel erreichbar ist. Fehlermeldung:
request to https://wicloud.sytes.net/remote.php/webdav/Joplin_Wo/ failed, reason: connect ETIMEDOUT 100.85.45.18:443 (Code ETIMEDOUT)
(Please check if the URL, the user name, the password etc. are correct and that the sync target is reachable.
Error message: request ...).
When I'm trying to run a synchronisation the systemn tells me "completed: 21.02.2023 07:27 (106s)", but nothing is synced.
Both on my iPad (iPadOS 16.2) and my android phone (Android 13) the sync runs correct - so the target itself should be working correct.
I found the discussion " Joplin sync failure on IPv6 only networks. #6717 " (Joplin sync failure on IPv6 only networks. · Issue #6717 · laurent22/joplin · GitHub) ... but it says more or less this is an upstream error of node.js.
Does anybody know if there is a way to get Joplin syncing to an IPv6 system at the moment and how to achieve it?
Thank you very much for information!
Yours
Wolfgang
tessus
2
I am confused. If it is IPv6 only, why does DNS return an A record?
e.g. I cannot even connect to https://wicloud.sytes.net/ via my web browser. IMO this is an admin issue on their side.
Dear Helmut,
yes – since the transition to Deutsche Glasfaser it is a IPv6 only site …
The A record from DNS results from NOIP – I cannot enter a AAAA record without an A record; the A record is simply the one my FRITZ!Box gives.
Do you have IPv6 on your computer?
I experienced from my office at the university that I cannot even connect to my nextcloud Landing page when my PC has not an IPv6 address. With an IPv6 address I reach the Landing page of my cloud, but not the sync target of Joplin.
Over my cell phone I can sync with Joplin using mobile data, not WiFi … therefore I think my nextcloud and my Joplin instance is configured correctly.
When I try to enter the IPv6 address of my Cloud (not the DNS Name in Joplin (either with […] or without the brackets the sync target cannot be reached.
Yours
Dr. Wolfgang Wirth
tessus
4
Ok, you are running the server in your home network. I thought it would be in a DC.
I am not using IPv6 at home. My ISP did not use IPv6 for the longest time and I deactivated everything IPv6 (even on a kernel basis on my Linux VMs). Thus my home network is entirely IPv4.
I believe that the ISP now supports IPv6, but I would have to verify this and change my settings on my VPN/router which is an OPNsense box (the cable modem is in bridged mode and connected to it).
Currently I only request an IPv4 address.
I experienced from my office at the university that I cannot even connect to my nextcloud Landing page when my PC has not an IPv6 address.
Hmm, isn't there a bridge between IPv4 and IPv6, irrc it's called NAT64.
With an IPv6 address I reach the Landing page of my cloud, but not the sync target of Joplin.
With a browser you can reach one but not the other? Or do you mran Joplin cannot connect to the sync target?
Over my cell phone I can sync with Joplin using mobile data, not WiFi … therefore I think my nextcloud and my Joplin instance is configured correctly.
Yes, this makes sense somehow and I think confirms that this is a nodejs issue.
On mobile the OS stack is used for communication (which also explains why the connections are h2), while on desktop the connections are made via a nodejs module.
This module can't do h2, and apparently also has issues with IPv6.
In this case I believe we are out of luck unless the module supports IPv6.
Please open a new issue in github for tracking purposes (you can also call it Joplin sync failure on IPv6 only networks) and I will label it accordingly, so that it is not closed by the bot.
But since this is most likely an upstream issue, I am not sure what we can do. But werespective module.
Ok, then I think it’s clear that you will not reach my nextcloud - seems to be the same problem I had at the university as long my PC there was configured to use IPv4 only.
No, with a browser I can reach the cloud and use it; I also can use the Nextcloud sync client which is able to connect over IPv6 with my cloud.
As far as I see it is only Joplin sync which refuses to use the IPv6 address - in the error message Joplin states not to be able to reach the cloud over the IPv4 (!) address.
I’m going to open a GitHub issue … we’re gonna see what happens 
Thanks for your help !
Wolfgang
tessus
6
Yes, this also pretty much points to an issue with the request module.
Let me know when you have created the issue. Cheers.
Good morning,
I created the issue now – hope everything’s correct 
Wolfgang
1 Like
tessus
8
Thanks, looks good. For reference:
system
Closed
9
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
