Internxt now has native rclone support, but it still isn’t available as a provider under Data Protection → Cloud Sync in TrueNAS.
It would be useful to have it added the same way pCloud and the other supported providers are, so Internxt backups can be configured and scheduled directly from the GUI rather than having to maintain separate rclone scripts/cron jobs.
Internxt’s native rclone backend is already available upstream, so hopefully this wouldn’t require building a completely new integration.
The main benefit would be being able to use the normal TrueNAS Cloud Sync workflow for scheduling, encryption, logs, restore tasks, etc.
I wonder how stable the rclone implementation is. Did you try?
Every time I have given Internxt a try, the downloads just stalled, but this could also be related to the web browser implementation of it. I hypothesize that they distribute data blocks across many nodes, some of which are slow or use cold storage. Every download then needs to collect those blocks, which takes time. It was too unreliable, at least for me.
I haven’t tested the native rclone implementation yet. I only just upgraded to Ultimate specifically so I can set it up on TrueNAS, so I’ll be interested to see how it behaves with a large backup.
My hope is that the native rclone backend is more reliable than the browser/WebDAV side, but I definitely don’t know that yet. I’ll probably start with a smaller test set, verify uploads/downloads, and then try it against a much larger media library.
If I run into stalls or unusually slow restores I’ll update the thread. It would actually be useful to know whether anyone here has tested the newer native rclone backend specifically.
I’ve now put Internxt’s native rclone backend through a fairly substantial real-world test on TrueNAS.
I’m using a standalone rclone 1.75.1 because the version currently included with TrueNAS doesn’t expose the Internxt backend. I’ve successfully backed up and restored Vaultwarden, OpenCloud, Immich (~423 GB), and several multi-TB media libraries through it.
There are some Internxt-specific quirks (mainly occasional HTTP 500s and stalled requests) but with conservative concurrency/retries it has been reliable enough for scheduled backups, including successful restore and hash verification.
So after actually testing it, I think the original request still makes sense: could Internxt be added as a provider under Data Protection → Cloud Sync once TrueNAS ships an rclone version containing the backend?
The backend itself is already upstream in rclone, and having it exposed through Cloud Sync would eliminate the need for a separately maintained rclone binary and custom scheduling for normal file backups, while bringing Internxt into the standard TrueNAS workflow for tasks, logging, encryption and restores.
I’m happy to provide test results or configuration details if they would be useful for evaluating support.
