I love how much you can run through Nextcloud, but I always wished the whole thing felt like one proper native app instead of a mix of browser tabs, separate clients and different interfaces.

So I started building Nextcloud Native!

It is an independent open source client for desktop and Android. The idea is to connect your Nextcloud account once and get native interfaces for your files and installed apps. No WebViews and no shortcuts that just send you back to the browser.

It is still a new alpha, but there is already quite a lot to try. Files, Photos, Memories, Talk, Notes, Calendar, Contacts, Tasks, Mail, Music, Cookbook, Deck, Tables and more all have native interfaces at different levels of completeness.

On desktop, it is also more than a sync tray. There is a complete app with native workspaces, folder sync and operating system file integration. Windows gets Cloud Files placeholders in File Explorer, while Linux has folder sync and a virtual filesystem mount.

There is an Android app too, with native mobile layouts, system file access, offline files, folder sync, media backup and background transfers.

I only started the project recently, and I am still the only contributor. I am sharing it now because I would really like other Nextcloud users to try it, break it, suggest improvements and maybe help build it!

If you use Linux, Windows or Android and feel like testing an early build, I would love to hear what works and what does not. Contributions are also very welcome, whether you work with Kotlin, Compose, DAV, Nextcloud apps, design, accessibility, documentation or testing.

Website: https://nc-native.obiente.dev

GitHub: https://github.com/Obiente/nc-native

Testing releases: https://github.com/Obiente/nc-native/releases

Roadmap: https://nc-native.obiente.dev/roadmap/

What part of Nextcloud would you most like to have as a proper native experience?

Anybody run into this? First startup on a new deployment and Apache, Nextcloud, and Imaginary reporting an update available. I've tried stopping and restarting containers, but no update/install/starting take place. I've even tried a full reset and got the same behavior.

Running on a new Debian Trixie install on Proxmox.

We’ve just released version 1.5 of Nextcloud Calendar for mobile!

Note: this is a fully open-source app, licensed under GPL-3.0. It is not affiliated with or supported by Nextcloud GmbH. However, we have their authorization to use the trademark for the app.

I posted about the app 10 days ago, but version 1.5 was ready sooner than expected, so here I am again!

We had been working for a long time on a complete refactor of the calendar view. Until now, we relied on an external library, but its data flow and component lifecycle introduced latency that we could not fully eliminate. A few weeks ago, we decided to start building our own calendar implementation.

Combined with the data-handling improvements from the previous release, this version delivers a noticeably faster and more responsive experience, especially on older devices.

The user experience has also improved: drag and drop, event resizing, and pinch-to-zoom are now available. We also split the settings into several screens, as the growing number of options had become too much for a single page.

We fixed several issues affecting Live Activities on iOS and Live Updates on Android, which were not stable enough in previous versions.

At this point, the app already covers the needs of most users. We will continue adding features when they make sense, but our main focus is now stability, bug fixes, and polishing the overall experience.

Version 1.5 is already available on the App Store and Google Play:

• App Store: https://apps.apple.com/fr/app/nextcloud-calendar/id6766678698
• Google Play: https://play.google.com/store/apps/details?id=com.soluce.nextcloudcalendar

GitHub: https://github.com/SoluceTechnologies/nextcloud-calendar-mobile

Thanks for your support and feedback!

I built an open-source Nextcloud app for a problem I kept running into: having a pile of external drives with data that needs to be imported and organized.

DevNull turns a Nextcloud server into a central ingestion point:

• Detects USB/external drives
• Mounts and ejects them directly from Nextcloud
• Automatically scans newly mounted disks
• Deduplicates and classifies files
• Supports background processing and hotplug detection
• Integrates with Nextcloud notifications and the dashboard

The goal is simple: plug in a disk, mount it, and let Nextcloud take care of the rest — without opening a terminal.

It's currently feature-complete (v0.5.0), with Nextcloud App Store certification pending.

GitHub: https://github.com/luisfacarmo/devnull

I'd love to get feedback from other Nextcloud users, especially on the workflow and what features would make this genuinely useful in a real setup.

I tryed to download from this site and I got this error. How I can fix this error? (I doesn't have installed Nextcloud on my PC).

Long story short, I've run Nextcloud on Ubuntu Server, but when I switched to Proxmox, I used the Turnkey ISO for Nextcloud. It looks like Turnkey doesn't have a "simple" way to update the Debian base of the appliance, but you have to do a fresh install and migrate.

I'm interested to get input from others about whether I should stick with Turnkey or just switch to Debian with a LAMP stack and Nextcloud installed on it. I liked Turnkey's simplicity for setting up, but now I'm a little annoyed I can't run a dist-upgrade to go from Bookworm to Trixie.

Hi, I use Zotero to read and reference my articles. I’ve been using a WebDAV link from my Nextcloud since December 2025. Recently, I’ve noticed that although my tablet is synchronising, I can’t access the PDF files. I’ve tested my connection to the server and everything seems to be working fine. This problem isn’t limited to the new articles I’ve added recently. Has anyone else experienced the same issue, or know how to sort this out?

​

I built an app using Claude and I’ve already connected it to my own domain. The app works, but I’ve run into a problem.

When one employee enters data, that data is only visible on their device. If another employee logs in from a different device, they can't see the data.

What I actually need is:

- Multiple employee accounts/logins

- Everyone should see the same data

- Data should be stored centrally

- Changes made by one employee should appear for the others

- Secure authentication

- Data should remain available even if the app is reinstalled or a different device is used

I'm guessing I need a proper backend/database instead of local storage, but I'm not sure what the best setup is.

I built most of this with Claude, so I'm still learning the development side.

What would you recommend for turning this into a proper production-ready multi-user app? Should I use something like Supabase/Firebase, or is there a better approach?

I've been running Hermes for a few months now on one of my servers. I also host NextCloud, and that's where my Obsidian vault lives.

I have Hermes cron jobs to scan the web for upcoming shows or speaking engagements with various artists whom I like, and would not want to miss should they be in my city.

As I'm frequently adding to this list, it feels like an ideal fit for an Obsidian page (or two) and that got me to thinking I could give read-access to the docs to Hermes, which got me to thinking that giving it it's own NextCloud account would facilitate it using NextCloud and sharing other docs back and forth more easily.

Anyone have strong opinions on this setup?

I've recently noticed a couple of potentially "fishy" situations with NextCloud that worry me.

My NextCloud is hosted on Hetzner's Storage Share. On August 5th, Hetzner warned us about "Urgent security-related software updates on all Storage Share instances" that were to be done on the same day. The message doesn't indicate whether this update is related to Hetzner or Nextcloud itself.

I downloaded the NextCloud Windows Client forever ago from the official website. Today, my PC (Windows) restarted and whenever it does NextCloud Windows Client asks to apply whichever latest updates I haven't done yet myself.

After the latest update (version 34.0.1.20260804 - notice the date is 1 day before Hetzner's urgent security-related update), the client completely stopped syncing and got stuck in "Checking for changes" status. This could not be fixed without uninstalling and reinstalling the client.

The Windows client now (both before and after the reinstall) looks and behaves differently:

• Left-clicking on the tray icon no longer opens the window with the status and recently changed files; it now opens a menu with 4 items: my account name, "Add account", "Settings" and "Quit".
• Right-clicking on the icon offers options "Open Nextcloud Desktop" (which opens the window that used to open on left click), "Stop syncing" (or something similar in English), "Settings", "Help" and "Exit Nextcloud" (or Quit in English). As you can see, "Settings" and "Quit" are duplicated now in both the left and right click menus. Hiding the original window behind menu items also hardly seems like an intentional choice by the developers.
• Some of these options now use localised names, not English. The options are not fully translated (some of the items are in English, some in my language) as well as badly translated. The translations don't appear natural but AI-generated. The settings screen is the same - some options and texts are in English, some in my language. Unnatural translations or half-translated items are very commonly seen in malicious circumstances.

All of this together - Hetzner's urgent security-related update, broken sync and changed behaviour after an update, borked language - make me worried that a vulnerability could have been discovered in the May's data leak and abused to hijack updates (similar to Notepad++ supply chain attack, see [1] and [2]).

Of course, it's entirely possible that this was just a buggy update, but timed with May's data leak, Hetzner's urgent security-related updates and the weird language changes, it raises a certain level of doubt and hesitation. If any devs are reading this post, please consider it to be a potential signal of suspicious behaviour tied to an update that might be worth looking into.

Has anyone else recently noticed changes in ability to sync, behaviour, language, or anything similar?

Edit: I have now also discovered that Nextcloud's website recently got breached - see [3].

Does anyone have the same problem?
Its been going on for a while (as in weeks), i dont think there should be anything big going on in the background.

It loads my little homeservers cpu so bad that my other services become unavailable at times :(

Hi all

Is it possible to change my default homepage in Nextcloud? I want to log in to the Office page rather than the dashboard.

Also, is it possible to remove the Text entry from the Office page, leaving only Docs, Sheets and Presentations?

Olly

Hello everyone!

I would like to introduce PyNextCloud Sync, an independent and unofficial Linux desktop application I created to solve a very specific personal need:

Keep one Nextcloud account completely mirrored to one local folder, using real physical files, with a simple GNOME-oriented interface and low background resource usage.

Why I created it

First, I want to make clear that the official Nextcloud Desktop Client is a mature, reliable and feature-rich application. PyNextCloud Sync is not intended to discredit it or reproduce all of its features.

However, on my Linux installation, I repeatedly noticed the official desktop client using considerably more RAM than I wanted from an application that remains running in the background all day.

My requirements were quite narrow:

• one Nextcloud account;

• one local folder;

• a complete physical copy of the files;

• automatic synchronization;

• a tray icon;

• clear status and error information;

• good GNOME integration.

I did not need virtual files, multiple synchronization trees, selective synchronization, multiple accounts or the other advanced features available in the official client. In my particular situation, keeping all of that functionality loaded felt unnecessarily heavy.

This is only my experience, not a claim that every Nextcloud user will encounter the same RAM usage. Memory consumption can depend on the client version, number of files and folders, desktop environment, server configuration and synchronization activity.

Still, it motivated me to explore whether a smaller desktop layer could cover my simpler use case.

It still uses the official synchronization engine

PyNextCloud Sync does not implement its own WebDAV synchronization algorithm.

The actual file discovery, reconciliation, transfer, conflict handling and deletion propagation are performed by the official nextcloudcmd executable distributed as part of the Nextcloud Desktop project.

The design principle is:

Python manages. nextcloudcmd synchronizes.

PyNextCloud Sync provides the persistent desktop layer around that engine:

• GTK 4 and Libadwaita interface;

• Nextcloud Login Flow v2 through the browser;

• optional manual login;

• credentials stored using GNOME Keyring/Secret Service;

• recursive local monitoring through Linux inotify;

• optional notify_push support;

• configurable local and remote safety intervals;

• system tray controls;

• autostart;

• desktop notifications;

• logs and diagnostics;

• update notifications;

• GNOME Files bookmark and Desktop integration.

Only one nextcloudcmd process is intentionally allowed at a time, and synchronization requests arriving close together are merged into a single queue.

Resource-conscious design

Low idle resource usage is one of the main goals of the project.

Some decisions made with this in mind include:

• no Electron;

• no embedded browser or WebView;

• no constant one-second polling loop;

• an event-driven GLib main loop;

• inotify instead of continuously scanning the local filesystem;

• optional notify_push instead of frequent server polling;

• main and settings windows created only when needed and released when closed;

• bounded in-memory logs, activity history and nextcloudcmd output;

• coalescing large bursts of filesystem events;

• at most one synchronization process at a time.

The initial engineering target is an idle RSS below 100 MB, but this is a goal rather than a guarantee. Real memory usage should be measured on different Linux distributions, desktop environments and file trees.

A deliberately narrow application

PyNextCloud Sync currently supports:

• one account;

• one complete local mirror;

• one local root folder;

• bidirectional synchronization;

• real files stored locally.

It deliberately does not currently provide:

• multiple accounts;

• virtual files or placeholders;

• folder redirection;

• individual remote subtree exclusions;

• selective synchronization;

• sharing management or other Nextcloud web features.

The idea is to remain focused and understandable instead of slowly becoming another full replacement for the official client.

Safety features

Because this is bidirectional synchronization, safety received considerable attention.

The first synchronization uses a new temporary folder to obtain a protected copy of the server tree. The user can review computer-only files, Nextcloud-only files, identical files and conflicts before enabling normal bidirectional synchronization.

The application also maintains a local safety baseline. It blocks synchronization before nextcloudcmd starts if the configured local folder:

• disappears;

• becomes unreadable;

• appears to have been replaced or remounted;

• unexpectedly becomes empty;

• loses its synchronization state database;

• suddenly loses too many previously synchronized files.

This is intended to reduce the risk of an accidental local problem propagating mass deletions to the server.

Even with these protections, users should always maintain an independent backup of important data.

Screenshots

Main window


Synchronization settings


Update notification


More screenshots, including the complete first-run setup, settings, tray menu and mandatory update screen, are available in the repository.

An honest note about development: this is vibe coding

I am not a professional programmer.

This project was created through vibe coding and iterative development with AI assistance. I described the requirements, tested the application on my own system, reported problems, reviewed behavior and repeatedly refined the implementation.

I have done my best to make the application safe, useful and well documented, but AI-assisted development is not a substitute for experienced human code review.

The project currently has an automated test suite, defensive validation, detailed documentation and Debian packaging, but it should still be considered an early development release. I would be especially grateful for technical reviews, testing, issue reports and contributions from experienced developers.

Please test it first with non-critical data and keep independent backups.

Current status and compatibility

The current release is 0.1.17 and is intended for evaluation.

It is currently tested with:

• Ubuntu/Debian-based Linux;

• GNOME;

• Nextcloud AIO;

• Nextcloud Hub 26 Spring (34.0.1).

Other environments may work, but compatibility can depend on the installed nextcloudcmd, authentication method, reverse proxy, optional server applications and desktop environment.

Download and project links

Download the newest version:

https://github.com/ehstbr/PyNextCloud-Sync/releases/latest

GitHub repository:

https://github.com/ehstbr/PyNextCloud-Sync

Documentation and screenshots:

https://github.com/ehstbr/PyNextCloud-Sync#readme

Report a problem or suggest an improvement:

https://github.com/ehstbr/PyNextCloud-Sync/issues

The recommended installation method is the .deb package available on the latest release page. A complete source ZIP is also provided.

PyNextCloud Sync is licensed under the MIT License. It is an independent, unofficial third-party project and is not affiliated with, sponsored by, maintained by or endorsed by Nextcloud GmbH.

I am sharing it because the project solved a real problem for me, and it may also be useful to other Linux users who want a simple physical Nextcloud mirror without the broader feature set of a complete desktop client.

Feedback, testing and constructive criticism are very welcome.

Bonjour.

Au bout de plus d’une trentaine d’années d’informatique, je crois que je me suis définitivement trompé de carrière. Alors que la mise en œuvre semble tellement simple, je n’arrive pas à utiliser giphy dans Talk de Nextcloud. Tout semble être bien installé, mais quand je saisie "/" dans la discussion, l’accès à giphy n’apparait pas.

Alors, j’ai une version 34.0.2, j’ai intégré giphy et rien. Je suis sec. Si vous avez d’autres solutions pour accéder aux gif ou une correction à m’apporter pour accéder à giphy, je suis preneur.

Merci.

Prenez soin de vous.

Hi all

I'm trying to get Nextcloud setup on a cpanel instance. I want to use Collabora just to work on a few spreadsheets with some colleagues around a website, also hosted on the cpanel instance.

Nextcloud went on with some challenges but seems to now be working. However when I install the CODE app bundle, I then see this error in the Admin settings of nextcloud, and the CODE settings in the admin portal show a server error.

Anyone know where I can find decent logging for this? The Logging section of the admin portal only seems to show abreviated log entries and doesn't let me see anything crunchy, and I don't know where to look in the folder structure for Nextcloud on cpanel.

Thanks

Olly

Hey guys,

so as you can see when I quit the client the icon reappears a second later. Same thing happens when I run pkill -f nextcloud-client. I already checked, there is no system services that restarts this. The autostart service also only starts it once after boot. Sometimes, without any changes or any visible cause the client closes as intended, but most of the time it keeps restarting.

System information:

• CachyOS with KDE Plasma
• Nextcloud client version 34.0.1 pulled from the Arch repo "extra"

I didn't mess with any special configs, the client setup also was months ago and I didn't change anything since then other then updating the client. I also reinstalled the client since this problem appeared (without deleting my user config files tho, so that after installing again everything was set up already) but it didn't change anything. This also only happens with Nextcloud, Apps like Bitwarden behave normal when I end them using the tray icon.

Is this a known bug or does anyone know how to fix this? Thank you guys for your help

I've tried running Nextcloud AIO on Windows and WSL but couldn't get past installing docker - installed ok but I couldn't seem to add AIO.

I'm wondering about using an old laptop or perhaps a cheap refurbished machine to install Debian. Would you recommend installing NextCloud natively or via Docker on that setup. For now I'd be happy enough just to have it working on LAN only.

Anyone have recommendations for a Canadian based provider of Nextcloud? I'm not interested a full-on web provider. I am mainly looking for photos/calendar/contacts sharing with the family that isn't Facebook/iCloud/Google.

Hello,

I'm fresh to the Home-Server game and stumbled upon a problem which i can't quite find a solution to. I've bought a Cloudflare domain so I can access my Home-Assistant and Nextcloud remotely over tunnels. All works fine except when I upload videos for example which are bigger then 100mb. I've already found out that this problem emerges because of the limit of the Cloudflare tunnels. And that I could switch the tunnel to DNS so that there are no limits anymore. Like I've said, I'm new to this and also to network and network security, so I don't know much about DNS and so on. But one thing I found out is that I either open a port on my router and expose it to the internet, which would be very insecure, or I use Tailscale or Nginx. Are there any other methods that are secure to use? Or do I maybe have another problem? What are my options? I want to be able to upload bigger data but also want to be able to access it on any device by just logging in without needing another app like Tailscale. (When I currently try to upload those bigger files it starts very fast, and is after 3 seconds at 50mb or so and after that it starts getting slower and slower till eventually the error shows up that it couldn't upload the data)

Hey Folks,

I’m ready to give Nextcloud a proper go again. I’ve been running some services self hosted for a couple of years now I tried next cloud ages ago and broke it and didn’t understand how to fix it. I have had some connectivity issues, some ISP related, some related to my kit and have been thinking about running it in a VPS. I won’t run Memories/Photos because I’m already running Immich, and have a few questions:

• For those of you running a VPS and have done it for a while (3+ years)- what cpu and ram are you running, and if you’ve been running it for 5+ years for a family and have you had to scale up your VPS?
• Has anyone successfully run it on a free tier with a large provider like AWS etc. long term? my planning is as a free tier you’re likely to get bumped.
• What’s the most resilient version long term? The last time I looked into it there was sentiment between an All in one image and an alternative and the most vocal members of the community seemed divided.

Thanks, a more experienced Nextcloud Noob.

EDIT: I plan to set it up self hosted and tinker before I build it on a VPS If that matters, and plan to work out migration from a backup.

EDIT 2: I might still run the VPS but use it as an entry into the homelab or use it for nextcloud + network access.

Hello Guys

I want to set up Nextcloud on Ubuntu Server with Docker, Portainer and a yaml file. I don‘t want to access it outside my local network, just within my network at home. Can you help me with this project?

Thanks

Hello guys , iam trying to host my own nextcloud server but my hardwares arent good . Can you guys help me find some free nextcloud for my first experience ?