[Bug]: Support Account Domains Matching Common Bundle Extensions

[sjg2203]

⚠️ Before submitting, please verify the following: ⚠️

• [x] This is a bug, not a question or a configuration issue.
• [x] This issue is not already reported on Github (I've searched it).
• [x] Nextcloud Server and Desktop Client are up to date. See Server Maintenance and Release Schedule and Desktop Releases for supported versions.
• [x] I agree to follow Nextcloud's Code of Conduct

Bug description

I am trying to use Virtual files with Nextcloud desktop on macOS, but this functionality does not seem to work. I installed Nextcloud desktop Virtual files 3.15.3 and skipped the setup part.

I then enabled Virtual files as well as fast sync.

I saw that it scanned over the files currently on the server, though after it seemed it had finished, there was nothing in Users/macos/Library/CloudStorage/Nextcloud-admin@IP (Locations → Nextcloud), it is empty. The loading wheel keeps turning indefinitely.

I tried to click on the sign-in button on the top right but welcomed me with this blank popup that didn't go anywhere and had to relaunch the Finder.

Any idea how to fix this and have Virtual files working on macOS? If needed, I can troubleshoot on an Intel Mac Pro or ARM MacBook Pro; both are running macOS 15.3.1 (24D70) Sequoia.

Steps to reproduce

1. Installed Nextcloud desktop 3.15.3 macOS Virtual files 12+
2. Connected using my server IP address
3. Skipped setting up the account
4. Enabled Enable virtual files and Enable fast sync in Settings → Virtual file sync
5. Scanned files on the server
6. Locations → Nextcloud is empty, keeps loading

Expected behavior

When enabling Virtual files and after it finished scanning files, it should appear in Locations → Nextcloud on macOS

Which files are affected by this bug

All

Operating system

macOS

Which version of the operating system you are running.

macOS 15.3.1 (24D70) Sequoia

Package

Official macOS 12+ universal pkg

Nextcloud Server version

31.0.0

Nextcloud Desktop Client version

3.15.3

Is this bug present after an update or on a fresh install?

Fresh desktop client install

Are you using the Nextcloud Server Encryption module?

Encryption is Disabled

Are you using an external user-backend?

• [x] Default internal user-backend
• [ ] LDAP/ Active Directory
• [ ] SSO - SAML
• [ ] Other

Nextcloud Server logs

Additional info

Anonymised Nextcloud desktop debug archive: 2025-03-06_nextcloud-debug-archive.zip

[buiapp]

VFS also doesn't work for me on MacOS 15.3.1. But I get an error message when clicking on the Location entry:

You can’t open the application “[email protected]” because it may be damaged or incomplete.

[nilsding]

@buiapp the issue you're facing has been fixed with #7835 and will be part of the next release 3.16.0 (assuming the domain of your Nextcloud instance ends in .app)

as for OP's issue, I wonder if #7768 resolved this too (that PR is also part of 3.16.0)

[buiapp]

Wow, that's a very niche bug I tapped into. 😅 Just because of the .app domain...

[sjg2203]

I sometimes have this bug #7768 on my Intel macOS after a reboot, but never on my ARM macOS. I tried with Nextcloud 3.16.0-rc2, as I could not find rc3 on this site, same empty Finder with loading wheel appears.

as for OP's issue, I wonder if #7768 resolved this too (that PR is also part of 3.16.0)

[nilsding]

@sjg2203 hmm, interesting that the architecture matters there. 🤔

Regarding this issue you've opened -- does that occur on both Intel and ARM?

[sjg2203]

Got this issue on both Intel and ARM, on both I had 3.15.3. I updated my ARM macOS to 3.16.0-rc2, same issue with it. However, in 3.16.0-rc2, the pause icon is no longer shown and is replaced by the sync icon, even though it says 'All synced!'

@sjg2203 hmm, interesting that the architecture matters there. 🤔

Regarding this issue you've opened -- does that occur on both Intel and ARM?

[buiapp]

@nilsding My Mac client still crashes even with the newest version 16.0. I attached a console log that could help troubleshoot.

It crashes only when I use the Nextcloud VFS client. The normal client works as expected.

nextcloud.log

20250310_1411_nextcloud.log

[sjg2203]

@nilsding I updated to Nextcloud 3.16.0, rebooted my Mac, still no change.

I played around a bit and found that some people had to add showExperimentalOptions=true to nextcloud.cfg under /Users/youruser/Library/Preferences/Nextcloud/, though it did not help in this case. In the same file, there is isVfsEnabled=false, I tried to switch to true but it automatically reverted to false.

As seen here, it is recommended to install notify_push, though its installation is not the most straightforward and quite buggy, I managed to have it installed and more or less running. It, however, did not help in this case.

Any idea what could cause VFS not to work? Could you guys investigate this

[SchVinzenz]

Same problem here. I'm using Nextcloud 3.16.1 (with ARM) and it still doesn't work. Like @buiapp the normal client works for me without any problems.

[masterbachelormaster]

exact same issue. It's frustrating. I've already tried everything. Looking forward to a solution :)

[Rello]

Hello, we had an issue with VFS on systems where no notfy_push was installed. can you give the new .2 another try?

thank you for your support

[buiapp]

I installed 3.16.2 yesterday but it still crashed. But I didn‘t reboot (will try later). Do you need any specific logs to debug it further?

Update: Reboot didn't helped.

[masterbachelormaster]

Hello, we had an issue with VFS on systems where no notfy_push was installed. can you give the new .2 another try?

thank you for your support

.2 doesn't work for me. I also installed the notify_push from the appstore. It did not fix the issue, unfortuantely :/

[sjg2203]

@Rello, version 3.16.2 did not resolve the issue. Using a domain instead of the IP address helps see the server in Locations in the Finder's menu, but once in there I can access the first order of folders but then these are empty.

Hello, we had an issue with VFS on systems where no notfy_push was installed. can you give the new .2 another try?

thank you for your support

[SchVinzenz]

@sjg2203 Thank you for your advice. I know it still doesn't work for you, but I also tried using the IP address (with http) instead of the domain (with SSL certificate). And it works wonderfully! Files are also displayed in the folders and I can open and view them without any problems.

[mark-ka]

You have to add the account newly, after you installed the VF-client. there you can set the virtual-files-function

[masterbachelormaster]

You have to add the account newly, after you installed the VF-client. there you can set the virtual-files-function

Thanks for your comment and the advice. What do you mean exactly? Many people have tried various things without any success including resetting the Nextcloud installation and signing only into the vsf option. Would be curious about your suggested solution, since nothing works for me.

[mark-ka]

You have to add the account newly, after you installed the VF-client. there you can set the virtual-files-function

Thanks for your comment and the advice. What do you mean exactly? Many people have tried various things without any success including resetting the Nextcloud installation and signing only into the vsf option. Would be curious about your suggested solution, since nothing works for me.

I had the same problem before, like described above. after I removed the complete account (click on the three points beside your account-name) and added it again (server-address), it gave me the option to use VF. when the account was set, I activated it SETTINGS >>> STANDARD FILE SYNC >>> three points >>>. lowest point: enable VF ... and it worked.

But key was: setting your account from new. Maybe it helps some of you guys :)

[masterbachelormaster]

You have to add the account newly, after you installed the VF-client. there you can set the virtual-files-function

Thanks for your comment and the advice. What do you mean exactly? Many people have tried various things without any success including resetting the Nextcloud installation and signing only into the vsf option. Would be curious about your suggested solution, since nothing works for me.

I had the same problem before, like described above. after I removed the complete account (click on the three points beside your account-name) and added it again (server-address), it gave me the option to use VF. when the account was set, I activated it SETTINGS >>> STANDARF FILE SYNC >>> three points >>>. lowest point: enable VF ... and it worked.

But key was: setting your account from new. Maybe it helps some of you guys :)

Thanks for this. It was recommended somewhere else. I did try this several times. Even completely erased Nextcloud with AppCleaner. IT DOES NOT WORK. Thanks for the suggestion though!

[sjg2203]

Thank you for the advice but as stated by @masterbachelormaster, this trick does not work either, unfortunately☹️

I had the same problem before, like described above. after I removed the complete account (click on the three points beside your account-name) and added it again (server-address), it gave me the option to use VF. when the account was set, I activated it SETTINGS >>> STANDARD FILE SYNC >>> three points >>>. lowest point: enable VF ... and it worked.

But key was: setting your account from new. Maybe it helps some of you guys :)

[buiapp]

My VFS client crashes immediately on startup. How do I actually make a clean uninstall of Nextcloud? I searched around on Github and Google, but couldn't find a satisfying answer.

[buiapp]

Nextcloud VFS doesn't crash anymore with the new 3.16.3 version. But clicking on the sidebar entry Locations -> Nextcloud, doesn't do anything for me.

[masterbachelormaster]

Quick update on my side again... I just got the new M4 Air and set it up from scratch without any backups to see whether the issue is a server or client side issue. The issue is even present with an absolutely new clean MacOS installation on my new M4 Air. So, it must be a server side issue. Pretty sad that I don't get it to work. So, I'm going to move back to Synology Drive, as there's no solution in sight. Good luck y'all!

Edit: spelling

[Rello]

Nextcloud VFS doesn't crash anymore with the new 3.16.3 version. But clicking on the sidebar entry Locations -> Nextcloud, doesn't do anything for me.

Hi, you can create the debug log in the settings. see if you find something - or post it here. In general it is working with >20k installations of 16.2. lets see...

[buiapp]

Nextcloud VFS doesn't crash anymore with the new 3.16.3 version. But clicking on the sidebar entry Locations -> Nextcloud, doesn't do anything for me.

Hi, you can create the debug log in the settings. see if you find something - or post it here. In general it is working with >20k installations of 16.2. lets see...

Here are my logs.

logs.zip

[masterbachelormaster]

Jeez, I actually wanted to give up.. haha. Here's mine. Thaaaaaanks!:

2025-04-16 17:04:25:144 [ info nextcloud.gui.folder.manager gui/folderman.cpp:1218 ]: <========== Sync finished for folder [Nextcloud] of account [[REDACTED_USERNAME]@[REDACTED_SERVER_ADDRESS]] with remote [https://[REDACTED_SERVER_ADDRESS]/remote.php/dav/files/[REDACTED_USERNAME]/Dokumente] 2025-04-16 17:04:25:741 [ info nextcloud.sync.accessmanager libsync/accessmanager.cpp:75 ]: 2 "" "https://[REDACTED_SERVER_ADDRESS]/ocs/v1.php/cloud/user?format=json" has X-Request-ID "a47d48fb-23e5-42d5-af1f-3f33f7ee318d" 2025-04-16 17:04:25:742 [ info nextcloud.sync.networkjob libsync/abstractnetworkjob.cpp:364 ]: OCC::JsonApiJob created for "https://[REDACTED_SERVER_ADDRESS]" + "ocs/v1.php/cloud/user" "OCC::UserInfo" 2025-04-16 17:04:25:834 [ info nextcloud.sync.credentials.webflow gui/creds/webflowcredentials.cpp:406 ]: request finished 2025-04-16 17:04:25:834 [ info nextcloud.sync.networkjob.jsonapi libsync/networkjobs.cpp:969 ]: JsonApiJob of QUrl("https://[REDACTED_SERVER_ADDRESS]/ocs/v1.php/cloud/user?format=json") FINISHED WITH STATUS "OK" 2025-04-16 17:04:25:835 [ info nextcloud.sync.accessmanager libsync/accessmanager.cpp:75 ]: 2 "" "https://[REDACTED_SERVER_ADDRESS]/remote.php/dav/avatars/[REDACTED_USERNAME]/128.png" has X-Request-ID "33ac25e1-cddb-424c-8472-ff25eb813a79" 2025-04-16 17:04:25:835 [ info nextcloud.sync.networkjob libsync/abstractnetworkjob.cpp:364 ]: OCC::AvatarJob created for "https://[REDACTED_SERVER_ADDRESS]" + "" "OCC::UserInfo" 2025-04-16 17:04:25:934 [ info nextcloud.sync.credentials.webflow gui/creds/webflowcredentials.cpp:406 ]: request finished 2025-04-16 17:04:51:483 [ info nextcloud.gui.folder.manager gui/folderman.cpp:1009 ]: Etag poll timer timeout 2025-04-16 17:04:51:483 [ info nextcloud.gui.folder.manager gui/folderman.cpp:1013 ]: Folders to sync: 1 2025-04-16 17:04:51:483 [ info nextcloud.gui.folder.manager gui/folderman.cpp:1023 ]: Number of folders that don't use push notifications: 1 2025-04-16 17:04:51:483 [ info nextcloud.gui.folder.manager gui/folderman.cpp:1040 ]: Run etag job on folder OCC::Folder(0x12d875e00) 2025-04-16 17:04:51:483 [ info nextcloud.gui.folder.manager gui/folderman.cpp:1064 ]: Can not run etag job: Polltime not reached 2025-04-16 17:04:54:483 [ info nextcloud.sync.accessmanager libsync/accessmanager.cpp:75 ]: 2 "" "https://[REDACTED_SERVER_ADDRESS]/ocs/v1.php/cloud/user?format=json" has X-Request-ID "5192783a-f4d7-4316-a2e8-cb109532b011" 2025-04-16 17:04:54:484 [ info nextcloud.sync.networkjob libsync/abstractnetworkjob.cpp:364 ]: OCC::JsonApiJob created for "https://[REDACTED_SERVER_ADDRESS]" + "ocs/v1.php/cloud/user" "OCC::UserInfo" 2025-04-16 17:04:54:748 [ info nextcloud.sync.credentials.webflow gui/creds/webflowcredentials.cpp:406 ]: request finished 2025-04-16 17:04:54:748 [ info nextcloud.sync.networkjob.jsonapi libsync/networkjobs.cpp:969 ]: JsonApiJob of QUrl("https://[REDACTED_SERVER_ADDRESS]/ocs/v1.php/cloud/user?format=json") FINISHED WITH STATUS "OK" 2025-04-16 17:04:54:969 [ info nextcloud.gui.mac.fileprovider.settingscontroller gui/macOS/fileprovidersettingscontroller_mac.mm:167 ]: Signalling file provider domain "[REDACTED_USERNAME]@[REDACTED_SERVER_ADDRESS]" 2025-04-16 17:04:54:971 [ warning nextcloud.gui.macfileproviderutils gui/macOS/fileproviderutils_mac.mm:63 ]: No matching item domain for identifier "[REDACTED_USERNAME]@[REDACTED_SERVER_ADDRESS]" 2025-04-16 17:04:54:972 [ info nextcloud.gui.mac.fileprovider.settingscontroller gui/macOS/fileprovidersettingscontroller_mac.mm:179 ]: Successfully signalled file provider domain 2025-04-16 17:04:55:484 [ info nextcloud.sync.accessmanager libsync/accessmanager.cpp:75 ]: 2 "" "https://[REDACTED_SERVER_ADDRESS]/ocs/v1.php/cloud/user?format=json" has X-Request-ID "a56f94f5-319f-4dc3-9ef8-13db36bcff62" 2025-04-16 17:04:55:484 [ info nextcloud.sync.networkjob libsync/abstractnetworkjob.cpp:364 ]: OCC::JsonApiJob created for "https://[REDACTED_SERVER_ADDRESS]" + "ocs/v1.php/cloud/user" "OCC::UserInfo" 2025-04-16 17:04:55:520 [ info nextcloud.gui.mac.fileprovider.settingscontroller gui/macOS/fileprovidersettingscontroller_mac.mm:167 ]: Signalling file provider domain "[REDACTED_USERNAME]@[REDACTED_SERVER_ADDRESS]" 2025-04-16 17:04:55:521 [ warning nextcloud.gui.macfileproviderutils gui/macOS/fileproviderutils_mac.mm:63 ]: No matching item domain for identifier "[REDACTED_USERNAME]@[REDACTED_SERVER_ADDRESS]" 2025-04-16 17:04:55:522 [ info nextcloud.gui.mac.fileprovider.settingscontroller gui/macOS/fileprovidersettingscontroller_mac.mm:179 ]: Successfully signalled file provider domain 2025-04-16 17:04:55:605 [ info nextcloud.sync.credentials.webflow gui/creds/webflowcredentials.cpp:406 ]: request finished 2025-04-16 17:04:55:605 [ info nextcloud.sync.networkjob.jsonapi libsync/networkjobs.cpp:969 ]: JsonApiJob of QUrl("https://[REDACTED_SERVER_ADDRESS]/ocs/v1.php/cloud/user?format=json") FINISHED WITH STATUS "OK" 2025-04-16 17:04:55:606 [ info nextcloud.sync.accessmanager libsync/accessmanager.cpp:75 ]: 2 "" "https://[REDACTED_SERVER_ADDRESS]/remote.php/dav/avatars/[REDACTED_USERNAME]/128.png" has X-Request-ID "74d0182d-95ae-49d6-a4a1-7ef4fc5e97c3" 2025-04-16 17:04:55:606 [ info nextcloud.sync.networkjob libsync/abstractnetworkjob.cpp:364 ]: OCC::AvatarJob created for "https://[REDACTED_SERVER_ADDRESS]" + "" "OCC::UserInfo" 2025-04-16 17:04:55:736 [ info nextcloud.gui.mac.fileprovider.settingscontroller gui/macOS/fileprovidersettingscontroller_mac.mm:167 ]: Signalling file provider domain "[REDACTED_USERNAME]@[REDACTED_SERVER_ADDRESS]" 2025-04-16 17:04:55:738 [ warning nextcloud.gui.macfileproviderutils gui/macOS/fileproviderutils_mac.mm:63 ]: No matching item domain for identifier "[REDACTED_USERNAME]@[REDACTED_SERVER_ADDRESS]"

[Unfaehig]

Hey guys,

so i also run into the issue, while trying to migrate to another domain name. So with my old domain it seems to work fine. However the new domain use special chars *non ASCII". There is a spcial method called Punycode to input the domain name for compatibility reasons. However i see that the URL in the nextcloud.cfg is always saved as undecoded URL, also the logs use the non Punycode version. So i guess in my case it might be related to this special chars in the domain.

So lets take this example hellò.com gets in Punycode is xn--hell-oqa.com however in nextcloud.cfg it will always shown as hellò.com So my guess is that the underlying Apple API expects the URL as xn--hell-oqa.com. It is currently just a guess, because i haven't found a good log entry, however it would explain why it works with my old domain without flaws, but not with the new one.

[sjg2203]

@Unfaehig, it might be the issue when having a domain name but I am using the IP address, no special characters or else here. Still not working even with 3.16.3 for me with the latest macOS 15.4…

Hey guys,

so i also run into the issue, while trying to migrate to another domain name. So with my old domain it seems to work fine. However the new domain use special chars *non ASCII". There is a spcial method called Punycode to input the domain name for compatibility reasons. However i see that the URL in the nextcloud.cfg is always saved as undecoded URL, also the logs use the non Punycode version. So i guess in my case it might be related to this special chars in the domain.

So lets take this example hellò.com gets in Punycode is xn--hell-oqa.com however in nextcloud.cfg it will always shown as hellò.com So my guess is that the underlying Apple API expects the URL as xn--hell-oqa.com. It is currently just a guess, because i haven't found a good log entry, however it would explain why it works with my old domain without flaws, but not with the new one.

[buiapp]

Just for update: Still the same for me in 3.16.4.

[JoshVelvet]

Having the same issue with macOS 15.4.1 and NextCloud VFS 3.16.4. Had it working before, shuffled my NextCloud hosting around and now having the issue with both my domain and IP address with Virtual Files in Finder showing the same as the original bug report. Will make do for now, but would be nice to get a fix as using Virtual Files is a deal breaker for me.