Ive been a qnap qsync user for maybe 15 years now. I am very familiar with the setup process.
For the last year I have been troubleshooting my QSYNC deployment to my MAC. It simply doesnt work. Even Fable 5 couldn’t figure out what the issue was (I used gemini pro, and opus 5 as well). I have QSYNC running perfectly fine on multiple windows 11 deployments.
I have reinstalled the MacOS multiple times, thinking it was some corrupt residual QSYNC application that wasnt working and not fully removed…
I have reinstalled the QSYNC application maybe 10 times in the last year every time I think I want to give it another shot at fixing it..
It logs in with the single user/pass I use across my LAN. It logs in both with the network address, and qnap id.. both work.. on every deployment across OS’s.
It SAYS its fully synced. I even SEE the files in the file directory. But no matter what I try and open it fails saying its corrupted.
It even says its syncs NEW files when I make them on my MAC, but they dont show up on the NAS or other QSYNC deployments anywhere else…
This is EVERY file extension, even text files just for testing.
I am convinced nobody is running this completely working… am I correct?
When using AI. the main problem is not the “model”, but the lack of accurate “data” that feeds the engine. If the model had access to internal QNAP resource data, it would perhaps to more accurate.
Going direct to the source, that has the actual experience and access to the code is typically more helpful for non-generic information at this point, or at least worth a try. You may even find QNAP support reps will respond here.
Probably not critical, but what NAS model do you have? Have you tried creating a new destination share for the data to see if it will sync to a new location? Are there any indications of issues in the logs? How are you connected to the NAS? If samba is in play, what versions are you running?
yeah im not disclosing what I do… but I am all set on the AI education. thanks… not that you know or care
As for the questions. Maybe you are not a QSYNC user but QNAP does not allow the qsync directory to be ‘shared’ like a traditional network share (SMB or otherwise). I get around this by just sharing the synced folder from another device - but not relevant. I am troubleshooting direct NAS/QSYNC functionality. I have a 451+. And in line with the “new share” I have said that I have qsync installed and working properly on several other devices on windows 11. It works, and has worked through multiple upgrades and installs over the years. I have created network shares from other public folders, dlna streaming, licensed NVR, and a host of other network based tools from this QNAP (docker pi-hole for example)… everything works. perfectly. This is an application problem, not a networking problem. And yes I have checked the logs, there is nothing there becuase as I stated, the loggin works as stated, the sync reports all files synced, there is no errors being announced or logged. For what its worth (nothing) I am running SAMBA 2, 2.1, 3. And AFP is enabled, along with all available NFS protocols. However, again, QSYNC uses http (443/80) so there is nothing to actually troubleshoot there. My firewall/router is not blocking anything on my LAN there.
Correct. Just trying to find similarity to other issues encountered by members and perhaps make you think of something that you may have missed or hadn’t thought of. If a Windows system works correctly, but the MAC doesn’t, it narrows things down, and there have been a number of changes and issues with MAC O/S lately it seems, hence the suggestion that you get QNAP support involved. Worst case, they should be able to setup a similar environment and perhaps replicate the issue or at least get some detailed logs or configuration info from you to isolate the problem. Seems like you have the standard stuff covered.
This is the error I get no matter what file:
“Excel cannot open the file ‘[filename]Conflicted copy 2026-03-14 by [nameremoved]).xlsx’ because the file format or file extension is not valid. Verify that the file has not been corrupted and that the file extension matches the format of the file.”
or another file (pdf) -
“The file “Home Cleaning Estimate.pdf” could not be opened.
It may be damaged or use a file format that Preview doesn’t recognize.”
Again, nothing hits any log or error in the QSYNC or QNAP application.
These files all say they are fully synced.
the file opens fine on every other device. including the file station application - even on my iphone.
I’d like to understand your exact flow first.
Are you uploading the file on the NAS, then trying to open it on the Mac, and that’s where it fails?
In the meantime, could you try this on that PDF file: set Space-Saving Mode → Always Keep on this device, then open it again and see whether it displays correctly.
If possible, some screenshots would help us understand what you’re seeing as well.
If I create it on the MAC it works to open on the MAC. It will say its SYNC’d on the QSYNC application - but it never shows up on the NAS. If I create it on my Windows PC it will sync and work on other windows PCs in my home. It will show up as a file on my MAC under QSYNC and say that it sync’d (even in the logs) but it will say its corrupted and cannot be opened. I use space saving mode on all of my devices.
The clue is that files appear synced and even show up in the directory, but open as corrupted and never actually push to the NAS. That pattern often means Qsync lacks Full Disk Access on modern macOS, so it’s only writing placeholder stubs, not real data. Check System Settings, Privacy and Security, Full Disk Access, and make sure Qsync is enabled there, then restart it. Sonoma and later broke a lot of sync apps this exact way.
I wouldn’t blame QNAP but Apple. They are trying to solve security problems with apps that don’t exist and so by default nearly everything gets locked down. It’s a real pain…
