3 hours ago, RaidPC said:

Is the NextCloud desktop app stand-alone like the Android app for Nextcloud? or it just a shortcut to running it from the browser?

It live-syncs files to the folder you selected on your machine, that's the whole point of it. Apps are just convenient links that will open a browser.

Edited July 13, 2025Jul 13 by Kilrah

I had an AI help me with the creation of various User Scripts. That worked except for one thing. This command was supposed to clean up unused Docker networks, but it also deleted br0, probably other networks:

# Clean up Docker networks
log "Remove unused Docker networks..."
docker network prune -f >> "$LOGFILE" 2>&1 || check_success "Error cleaning up Docker networks"

I was able to fix everything, all Docker are running well again but unfortunately my lsio-Nextcloud container is no longer accessible. Now I don't know where to start because the error could be anywhere: unRAID network, Nextcloud, NPM (jc21 variant)....

There are warnings in the Nextcloud console, but they have been there before:
Linuxserver.io version: 31.0.7-ls383
Build-date: 2025-07-10T09:40:52+00:00
───────────────────────────────────────
    
using keys found in /config/keys
**** The following active confs have different version dates than the samples that are shipped. ****
**** This may be due to user customization or an update to the samples. ****
**** You should compare the following files to the samples in the same folder and update them. ****
**** Use the link at the top of the file to view the changelog. ****
┌────────────┬────────────┬────────────────────────────────────────────────────────────────────────┐
│  old date  │  new date  │ path                                                                   │
├────────────┼────────────┼────────────────────────────────────────────────────────────────────────┤
│ 2024-05-27 │ 2024-12-17 │ /config/nginx/nginx.conf                                               │
│ 2024-06-24 │ 2024-07-16 │ /config/nginx/site-confs/default.conf                                  │
│ 2023-08-13 │ 2024-12-06 │ /config/nginx/ssl.conf                                                 │
└────────────┴────────────┴────────────────────────────────────────────────────────────────────────┘
After completing the web-based installer, restart the Nextcloud container to apply default memory caching and transactional file locking configurations.
Alternatively, you can apply your own configurations by editing /config/www/nextcloud/config/config.php following the documentation:
https://docs.nextcloud.com/server/latest/admin_manual/configuration_server/caching_configuration.html
https://docs.nextcloud.com/server/latest/admin_manual/configuration_files/files_locking_transactional.html
[custom-init] No custom files found, skipping...
[ls.io-init] done.

Here is the content of my network.cfg file:

# Generated settings:
IFNAME[0]="br0"
BONDNAME[0]="bond0"
BONDING_MIIMON[0]="100"
BRNAME[0]="br0"
BRSTP[0]="no"
BRFD[0]="0"
DHCP_KEEPRESOLV="yes"
DNS_SERVER1="9.9.9.9"
DNS_SERVER2="149.112.112.112"
DNS_SERVER3="1.1.1.1"
DHCP6_KEEPRESOLV="yes"
DNS6_SERVER1="2620:fe::fe"
DNS6_SERVER2="2620:fe::9"
DESCRIPTION[0]="Primary"
BONDING_MODE[0]="1"
BONDNICS[0]="eth0 eth1"
BRNICS[0]="bond0"
PROTOCOL[0]="ipv4"
USE_DHCP[0]="no"
IPADDR[0]="192.168.178.28"
NETMASK[0]="255.255.255.0"
GATEWAY[0]="192.168.178.1"
METRIC[0]="1"
USE_DHCP6[0]="yes"
SYSNICS="1"

That was certainly a very stupid mistake, but maybe someone can help me get the Nextcloud Docker up and running again.

Thank you very much.

2025-07-14_diagnostics_tower.zip

I just received a Nextcloud message that 2 apps have updates available. Seems that Nextcloud is running fine (occ maintenance:repair ended with out any error) - unfortunately without me ☹️

root@1f0afe4aa82f:/# occ app:update --all
richdocuments new version available: 8.7.2
richdocuments updated
previewgenerator new version available: 5.9.0
previewgenerator updated

Edited July 15, 2025Jul 15 by EdgarWallace

1 hour ago, EdgarWallace said:

but it also deleted br0

A reboot should fix that.

17 minutes ago, EdgarWallace said:

unfortunately without me

What does that mean? That log shows they were updated normally

Edited July 15, 2025Jul 15 by Kilrah

Thanks @Kilrah

I reboot several times, restarted Docker etc.

I attached the report that came via occ support:report. Under <details><summary>network</summary> I see some issues.....

occ-support-report.txt

Edited July 15, 2025Jul 15 by EdgarWallace

On 7/14/2025 at 3:14 AM, RaidPC said:

Is the NextCloud desktop app stand-alone like the Android app for Nextcloud? or it just a shortcut to running it from the browser?

Gecko: Think of it as both. The app handles file and folder syncing and sharing authorisation. The app also contains, what is effectively, links to the app you want to use, which directs you to the browser based app. I personally never use it that way. Might as well just log in and use the apps. Browser based logins are pretty persistent.

Right now, every time I open in the systray the Nextcloud app, it pops up a window stating "All synced!" with a list of recent activities below it.

If I click on my icon on the right side top, it states I can "log out." among set status or remove account. This gives me the impression I am connected to my Nextcloud server.

But when I click on one of the listed apps at the top right corner, it brings up my browser and acks me to login.

Gecko: Its normal. Its effectively a link to the browser based app that you select. If you're not logged in online already, then you'll be asked to log in.

Based on this link where someone brought up the same thing, I am led to believe this is not normal. I quote below.

"I want to use an app password for my desktop-clients.

The issue is that the desktop-client is not asking for password by itself but is opening a browser windows to log in and to approve access. That is not what I want.

How can I force the desktop client to

1. ask by itself for pw

2. use then provided app pw

Geck0: Log into the browser based Nextcloud of the user account you want to sync. Go to the account's Settings / Security.

At the bottom, enter an app name, such as "Windows 11 client" (whatever is a good description} and push create.

Copy the device password.

On your Nextcloud client app: Log out and log back in using the device password instead.

I suggest joining the Nextcloud forum for these sorts of queries. This forum is mainly for Nextcloud docker issues related to unRaid.

On 7/14/2025 at 3:14 AM, RaidPC said:

On 7/14/2025 at 3:14 AM, RaidPC said:

Nextcloud community

Desktop client app password

Is there a specific reason why you want to use a manually generated App Password instead of the standard login via Login Flow? I’m asking because Login Flow is actually the preferred way of connect...

3 hours ago, Kilrah said:

A reboot should fix that.

What does that mean? That log shows they were updated normally

Sorry @Kilrah , I wasn't very precise there. I can't access the Nextcloud WebUI. The same goes for all apps with Nextcloud access.

You have been MOST helpful. I appreciate all your help!

Going forward I am not sure where should look. I took the advice I kept getting and secured a domain name with Duckdns so I can get Nextcloud to run under HTTPS. So I follow a ton of videos to get there. Nginx Proxy Manager, then Binhex-Offical-Pihole (that is working well) and thought with my free domain name I could glue all these pieces together.

LOL! BUT it appears from all these self-hosting videos with SSL, I now need something that apparently Duckdns does not offer. The ability to create "A Record" or "CNAME." Again, I just want this to run strictly internally.

If I do need more capabilities that Duckdns's domain name, any video or website you could recommend so I can put all this together. :-)

2 hours ago, RaidPC said:

You have been MOST helpful. I appreciate all your help!

Going forward I am not sure where should look. I took the advice I kept getting and secured a domain name with Duckdns so I can get Nextcloud to run under HTTPS. So I follow a ton of videos to get there. Nginx Proxy Manager, then Binhex-Offical-Pihole (that is working well) and thought with my free domain name I could glue all these pieces together.

LOL! BUT it appears from all these self-hosting videos with SSL, I now need something that apparently Duckdns does not offer. The ability to create "A Record" or "CNAME." Again, I just want this to run strictly internally.

If I do need more capabilities that Duckdns's domain name, any video or website you could recommend so I can put all this together. :-)

Ive never used DUCKDNS, but they do support CNAME. There's plenty of videos on how to set up a CNAME. DUCKDNS would have some decent FAQ. Its beyond the scope of this thread.

Make sure you have a decent firewall, like opnSense, with nginx reverse proxy (it does support others). Pihole is not meant for this.

I think there is a lot you need to read up on.

DNS

Firewalling

Reverse proxy

ACME SSL (also supported in opnSense).

Happy reading.

I hope this is okay to post a new question here.

I've been running my NextCloud instance on my Unraid server for about 5 or so years now. I use duckdns.org for my domain service. A few weeks ago, suddenly I was unable to access my NextCloud service. I tried to access it using the IP address locally, as well as using the domain URL. Nothing. So I tried to access DuckDNS.org. to see if something had happened to my account there. I can't even get access to that service anymore.

I've tried accessing from outside my own internet and I get the same results. I've reached out to my ISP, but they claim nothing is wrong at this point, however they are still investigating.

I'm really curious if there is more troubleshooting that I can perform to help diagnose the problem. I've been using Unraid for quite a dew years, but I am by no means an expert. I can follow directions very well though.

Any suggestions for how I might proceed would be greatly appreciated.

Thanks.

/Don

Edited July 16, 2025Jul 16 by dius

51 minutes ago, dius said:

I hope this is okay to post a new question here.

I've been running my NextCloud instance on my Unraid server for about 5 or so years now. I use duckdns.org for my domain service. A few weeks ago, suddenly I was unable to access my NextCloud service. I tried to access it using the IP address locally, as well as using the domain URL. Nothing. So I tried to access DuckDNS.org. to see if something had happened to my account there. I can't even get access to that service anymore.

I've tried accessing from outside my own internet and I get the same results. I've reached out to my ISP, but they claim nothing is wrong at this point, however they are still investigating.

I'm really curious if there is more troubleshooting that I can perform to help diagnose the problem. I've been using Unraid for quite a dew years, but I am by no means an expert. I can follow directions very well though.

Any suggestions for how I might proceed would be greatly appreciated.

Thanks.

/Don

This is unrelated to Nextcloud, but its clearly a DNS issue. I'll try to give some basic help, but there's a change in your network's DNS.

When you say you tried to accesss Duck outside of the network, was this with your phone or your laptop

13 hours ago, dius said:

I hope this is okay to post a new question here.

I've been running my NextCloud instance on my Unraid server for about 5 or so years now. I use duckdns.org for my domain service. A few weeks ago, suddenly I was unable to access my NextCloud service. I tried to access it using the IP address locally, as well as using the domain URL. Nothing. So I tried to access DuckDNS.org. to see if something had happened to my account there. I can't even get access to that service anymore.

I've tried accessing from outside my own internet and I get the same results. I've reached out to my ISP, but they claim nothing is wrong at this point, however they are still investigating.

I'm really curious if there is more troubleshooting that I can perform to help diagnose the problem. I've been using Unraid for quite a dew years, but I am by no means an expert. I can follow directions very well though.

Any suggestions for how I might proceed would be greatly appreciated.

Thanks.

/Don

Maybe move this to unRaid's Networking section. NC is impacted by this, but its not related to it. Message me afterwards and I'll try to respond. You're also missing out on help from people that are network strong but don't use NC.

On 6/17/2025 at 7:31 PM, DrSiva2022 said:

@cosmicrelish , Almost in the same boat... I am on 27.0.2. Last time i updated to 27.0.2 from a lower version , it totally went sideways and had to reinstall , reupload everything. I have now set the version fixed to prevent any auto-updates. Now my backups at almost 2TB. I have all folders neatly created , i dont want to mess things up. The system is working just fine , but at the same time , i dont want to be behind the main version too far.

someone please help me figure out the best way to upgrade to latest version , without breaking things.

I really wish updating nextcloud was refined , rather than becoming too tiresome and problematic.

Sorry I can't be of any help. With everything I tried I ended up breaking the whole thing and just deleted all the app ata and the containers and started rom scratch

I am trying to address the hardening recommendations for my Nextcloud instance. I get these warnings on the Administration Setting Overview tab.

I've updated every config file I can locate that has the headers mentioned below, but all to no avail. I still get these warning.

Can anyone tell me exactly what config file I should be updating and where to find it?

Thanks in advance for any help you can provide.

11 minutes ago, dius said:

I am trying to address the hardening recommendations for my Nextcloud instance. I get these warnings on the Administration Setting Overview tab.

I've updated every config file I can locate that has the headers mentioned below, but all to no avail. I still get these warning.

Can anyone tell me exactly what config file I should be updating and where to find it?

Thanks in advance for any help you can provide.

These are set in your nginx conf settings. Ideally, you should be running a reverse proxy. In which case set them there, instead of in the nginx.conf file. You'll find them easy to set if you're using opnSense as the revese proxy, as it can be done in the GUI.

Edited July 22, 2025Jul 22 by Geck0

16 hours ago, Geck0 said:

These are set in your nginx conf settings. Ideally, you should be running a reverse proxy. In which case set them there, instead of in the nginx.conf file. You'll find them easy to set if you're using opnSense as the revese proxy, as it can be done in the GUI.

Thanks.

I've set them in both the Nextcloud config ssl.conf and in the Swag ssl.conf but I continue to get the same warnings. Is there another location perhaps?

4 hours ago, dius said:

Thanks.

I've set them in both the Nextcloud config ssl.conf and in the Swag ssl.conf but I continue to get the same warnings. Is there another location perhaps?

You can access it through your Nextcloud's appdata. The files that need adjusting are "default.conf" and "nginx.conf".

I generally leave default.conf alone and adjust nginx.conf, in fact I haven't adjusted mine in years. When you upgrade Nextcloud, it will keep those files, your config.php file, etc.

Its linked to its actual location inside Nextcloud's docker:

But, you don't need to go into the docker itself.

Since moving to opnSense (a few years ago), I set the majority of these settings in there. I suggest reading up on the different settings. There are some good books on ngxinx if you have a look online. I'm not an expert and used to know a lot more, but I've moved onto other thing. Again, I would recommend you introduce a reverse proxy into your eco-system, where ACME SSL can do the work for you for your certs and the nginx reverse proxy can manage your settings for Nextcloud and other hosted websites. It can also use different reverse proxy instead, like Traefik.

Its more secure than doing a port forward, etc.

In a port forward situation, your Nextcloud server can be exposed to a DDoS attack, which may affect your ability to manage your unRaid server. You would have to crash it to regain control. Although, I think in your message to me, you said you were using CloudFlare which will more than likely protect you from it.

Anyway, moving on, hope that helps. You're going to have to do a lot of Googling and reading on nginx syntax, etc. if you want to do this properly.

(Edit)

I just saw your DM that you use Swag, ignore opnSense comments, although I still think its best to have a reverse proxy to the internet on a different machine, for several reasons.

If you're using Swag, you can put those settings into Swag for SSL and Nextcloud and let it handle it.

Nextcloud <-----------HTTP<---------Swag (SSL and Nextcloud protocols)<----------HTTPS<--------CLOUD

Thats what I would do anyway. (Don't ask me about Swag, its popular, but I haven't implemented it. If I did, it would be for internal resolution).

Edited July 22, 2025Jul 22 by Geck0

Is there a list of valid repositories that can be used for the updating of the container?

I'm on lscr.io/linuxserver/nextcloud:28.0.3, tried lscr.io/linuxserver/nextcloud:28.0.9 but it said invalid.

34 minutes ago, jj_uk said:

Is there a list of valid repositories that can be used for the updating of the container?

I'm on lscr.io/linuxserver/nextcloud:28.0.3, tried lscr.io/linuxserver/nextcloud:28.0.9 but it said invalid.

Click on the Docker icon to bring up the menu, then click on "More Info" to go to the GitHub page for the Docker. From there, click on "Tags" to see all the available tags.

On 7/25/2025 at 11:27 PM, jj_uk said:

Is there a list of valid repositories that can be used for the updating of the container?

I'm on lscr.io/linuxserver/nextcloud:28.0.3, tried lscr.io/linuxserver/nextcloud:28.0.9 but it said invalid.

Hello,

have a similar problem, want to updatethe dcker image, but get this error:

TOTAL DATA PULLED: 0 B

Unable to find image 'lscr.io/linuxserver/nextcloud:28.0.4-ls309' locally
docker: Error response from daemon: Get "https://lscr.io/v2/": dial tcp 3.67.33.93:443: connect: connection refused.
See 'docker run --help'.

I tried t follow lademonkees path but didn't understand, how this will help. I found the tgged versions and then tried to update to the versions with 28.0.4-ls309 starting upwards (by changing configuration paremeter "Repository" to e.g. "lscr.io/linuxserver/nextcloud:28.0.4-ls309", but it seems, that the path to repo in the image is not the correct. What is my fault, how can i update the image?

Many thanks in advance.

Everyone else seeing this with todays update, too?

33 minutes ago, blaine07 said:

Everyone else seeing this with todays update, too?

Yes I'm seeing it. Everything seems to be working for now. I've no idea how to fix this warning. I'm hoping that a subsequent update will fix it ... :)

5 hours ago, kSmKcW9XJ1yCN2ejHX3s said:

Hello,

have a similar problem, want to updatethe dcker image, but get this error:

TOTAL DATA PULLED: 0 B

Unable to find image 'lscr.io/linuxserver/nextcloud:28.0.4-ls309' locally
docker: Error response from daemon: Get "https://lscr.io/v2/": dial tcp 3.67.33.93:443: connect: connection refused.
See 'docker run --help'.

I tried t follow lademonkees path but didn't understand, how this will help. I found the tgged versions and then tried to update to the versions with 28.0.4-ls309 starting upwards (by changing configuration paremeter "Repository" to e.g. "lscr.io/linuxserver/nextcloud:28.0.4-ls309", but it seems, that the path to repo in the image is not the correct. What is my fault, how can i update the image?

Many thanks in advance.

Go to Google and type "linixserver.io nextcloud" it will take you to the repository for linuxserver.io. Look for the latest version that you want abd copy abd paste the label into the dockers edit section.

Ie. Copy andd paste the title (lable) of the version, as per the image Ive attached. It would have been useful for you to copy and paste what you have in your dockers edit section, as its likely a pull issue with what you've edited. You may not want the latest version anyway, if you read above, two guys are reporting a problem.

Edited July 29, 2025Jul 29 by Geck0

14 hours ago, dius said:

Yes I'm seeing it. Everything seems to be working for now. I've no idea how to fix this warning. I'm hoping that a subsequent update will fix it ... :)

I do feel like we've seen this before and it WAS fixed in a update...been a long time though. Hmm

On 7/29/2025 at 9:55 PM, dius said:

Yes I'm seeing it. Everything seems to be working for now. I've no idea how to fix this warning. I'm hoping that a subsequent update will fix it ... :)

Any word on if the new version (just now published by linuxserver) has the same warning or not? I held off upgrading last week when I saw your post.

On 7/30/2025 at 6:20 AM, blaine07 said:

Everyone else seeing this with todays update, too?

I'm also seeing it after an update. My nextcloud instance whilst showing as starting is unable to be connected to so unfortunately it appears to have broken something. :(

I'm going to try and reboot the whole server and see if that helps at all.