Hello, I have been trying to setup Nextcloud on docker for the last two weeks and can’t really get it to work. I am using OMV6 as my OS and deployed Nextcloud using docker compose. I am only using Nextcloud locally behind a fire wall. I only want http2 and ssl to work. The official Docker example compose file was the only way I found so far to get both working. Even though I think the proxy is overkill and I have never used nginx before. My compose file looks like this and is based on the official example found here: [Example] docker/.examples/docker-compose/with-nginx-proxy/mariadb/fpm at master · nextcloud/docker · GitHub)
In the nextcloud overview I am getting the folowing warnings:
Your web server is not properly set up to resolve "/.well-known/webfinger". Further information can be found in the documentation ↗.
Your web server is not properly set up to resolve "/.well-known/nodeinfo". Further information can be found in the documentation ↗.
Your web server is not properly set up to resolve "/.well-known/caldav". Further information can be found in the documentation ↗.
Your web server is not properly set up to resolve "/.well-known/carddav". Further information can be found in the documentation ↗.
As far as I can tell WebDAV on Windows is also not working.
The webserver config should be correct, I think. I don’t know if I have to change something at the proxy and where.
Also, if it would be easier to just ditch the proxy, I would be ok with that. I would also be ok with using apache instead of nginx.
I found them somewhere in the Nextcloud documentation. But I think the documentation was wrong. It contained $host instead of $http_host. I think thats an error in the documentation because $host doesn’t work.
Anyways. The experience (even without the proxy) was… frustrating to say the least…
I would like to a have a final attempt with the aio image. (This is going to be my 3. time starting over again).
All I want is:
Memories to work which requires:
Preview pre generator
http/2 or http/3
Calander and contact sync to phone
Windows Client to:
Be reliable (no Bad Gateway or Forbidden errors)
Fast (near linespeed for uploads and downloads)
The problem I have with the aio is that it requires a valid cert for no apparent reason. I already have a cert for my Nextcloud but that is signed by a CA that I created. That CA has been added to my phone, PC and laptop. Thus they trust it. I don’t want to buy a valid cert or use Let’s Encrypt since my Nextcloud is only going to run local anyways.
Is there a way to use my custom cert signed by my CA? The documentation says no but I don’t get why and wonder how a company would deal with this because I think they would also rather use their local CA instead of setting up a proxy to use Let’s Encrypt like the documentation recommends.