What about updates? It updates. Yes, custom apps will migrate fine. I would suggest taking a step back and learning some things about docker and nextcloud in docker from the doc. It will help you immensely. Nextcloud is one of the tougher apps to understand and learn, esp in “docker”.
Quoting for emphasis. @Lev, Nextcloud is big, and it’s flexible, and because of that, it’s complicated. There are lots of moving pieces that depend on each other. I really think it’s something worth running in its own VM, or VM-like environment (jail/sandbox).
Leave alone nextcloud, I’m struggling to install jc21/nginx-proxy-manager conainer, it freezes app page 
And a better source for nextcloud help is the nextcloud forum. Including installation issues.
Don’t tell me sandbox - I’ll die configuring this thing…
no, if I’ll have ability to compose docker with an additional packages - that’s ok. This machine isn’t strong enough to host VMs
You’ll be able to use docker compose in the very next version, Electric Eel, if no rush, I’d simply do nothing and wait for that. Far easier than potentially converting twice. Unless you have some urgent rush. So many are worrying about not getting updates with Truecharts apps. Always chasing updates.
Yeah, definitely good idea to just wait.
I’ll be able to just compose the dockerfile the way I want. I think that this kubernetes is also quite slow.
It can be, depends on your system. On my system, it averages well under 1% cpu usage. But on slower systems than mine, can be for sure. Docker compose will greatly simplify things for many who are more familiar with it.
Hello,
I continued experimenting.
I finally solved the strict-transport-security (max-age) warning, though not sure if applies to all cases.
I just edited the list of trusted domains in the config.php file, located in the NextCloud pod.
I deleted all trusted domains, except My NextCloud domain and the localhost. My NextCloud domain as “0” and localhost as 1. Excluding the local host generated a different warning. I think that having the NextCloud domain as the first option would solve the issue without deleting the rest of the trusted domains, but did not want to expend more time.
‘trusted_domains’ =>
array (
0 => ‘xx.xxxxxx.com’,
1 => ‘localhost’,
),
This eliminated the warning. 
I hope this helps others
I tried to do this but when restarting the APP it replaced the 127.0.0.1 and nextcloud trusted domains. I can’t get it to just be as below
‘trusted_domains’ =>
array (
0 => ‘xx.xxxxxx.com’,
1 => ‘localhost’,
),
Correct, the trusted domains are replaced for the default list every time the app is restarted or updated. I adjust the config.php file every time. I do not know how to make the change persistent.
Is the path to the config.php in the container, on a hostpath in the app config? If not, certainly gone each time.
Are changes to the config.php read in real time (so I don’t need to restart)?
Thanks
so I guess this is something I can configure in the Nextcloud APP config
I’ll look into this.
Otherwise, the NC documentation says to modify the Apache config by adding this section. Is this possible as well/instead?
<VirtualHost *:443>
ServerName cloud.nextcloud.com
Header always set Strict-Transport-Security “max-age=15552000; includeSubDomains”
*it requires mod_headers enabled
The reason why I am interested in HSTS is that it is needed for camera and microphone to work in the Talk NC plugin
PaulMcG1970
Changes are indeed real time, but probably have to restart nextcloud. Not sure about that. The key point is you have to have a hostpath setup. Do you? That is in the app config. This is the way docker works. I do not get the messages and did not modify the Apache config. However, I am using Caddy instead as a reverse proxy to nextcloud so that handles it instead so not surprising.
It might help if you post the entire app config. Otherwise just guessing.I do not actually use the app, I use the docker container. But, it should be the same idea as the same underlying container. Are you using a reverse proxy?
What version of Scale are you on? If Eel, you can do from the command line:
docker inspect ix-nextcloud-nextcloud-1
and post the results alternatively to screen capturing the app config.
i have same issue
not solve the issue
i not using nginx or proxy reveres , just using cloudflared tunnel
still don’t know how to find Apache VirtualHost file if follow the nextcloud guide
how to fix it??
thanks before
App Version: v31.0.7
Version:v2.0.10
Source: github.com/nextcloud/docker
Train: stable
Truenas version 25.04.1
Hi Paul, I just check my NextCloud instance, and the Strict-Transport Security error is back. I tried what I did before, but it is not working anymore. So, the solution was temporary. I will explore for solutions the weekend. I will write in case I found something. I hope somebody come with an idea or find a solution in the meantime.
I have left NC with this error as I decided not to use the Talk function with cameras.
I am using cloudflare tunnels too and not using a reverse proxy.
No solution for this issue?