Joplin sync failure on IPv6 only networks.

[AesaraB]

Environment

Joplin version: Flatpak 2.8.8 Platform: Linux OS specifics: Fedora 36

Steps to reproduce

With Dropbox on an IPv6 network:

1. Set up Dropbox sync (may need to do so on IPv4 enabled network)
2. Attempt to synchronise database
3. Joplin tries to connect to https://content.dropboxapi.com using it's A (IPv4) DNS record instead of the AAAA (IPv6) record.

Last error: FetchError: request to https://content.dropboxapi.com/2/files/download failed, reason: connect EHOSTUNREACH 162.125.83.14:443

I've never developed with Electron/Node.js before, but this is probably an upstream bug, see: signalapp/Signal-Desktop/issues/4121

[ghost]

Environment

Joplin version: 2.8.8 Platform: Linux OS specifics: Arch Linux

Comment

I'm having the same problem, I'm not able to sync my Joplin with Dropbox when I'm on IPV6, but when I'm on IPV4, the sync works. I then had to disable IPV6 for synchronization in Joplin to work.

[github-actions[bot]]

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? If you require support or are requesting an enhancement or feature then please create a topic on the Joplin forum. This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.

[github-actions[bot]]

Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, feel free to create a new issue with up-to-date information.