Closed scoop96 closed 1 month ago
If i switch to webcron and execute the my-domain.com/cron.php, the message that pops out is this one
I updated to latest nextcloud version 29.0.0
And the cron is still a problem plus this error regarding well-known.
In nginx proxy manager is configured with this (as requiered in the documentation):
location /.well-known/carddav {
return 301 $scheme://$host/remote.php/dav;
}
location /.well-known/caldav {
return 301 $scheme://$host/remote.php/dav;
}
location /.well-known/webfinger {
return 301 $scheme://$host/index.php/.well-known/webfinger;
}
location /.well-known/nodeinfo {
return 301 $scheme://$host/index.php/.well-known/nodeinfo;
}
Hi @scoop96 - Please post your queries over at the Help Forum - https://help.nextcloud.com
This channel is solely for reporting bugs in the image itself and these are configuration matters.
P.S. For the cron matters, you can see our config examples in this repository for the ways we suggest running cron.
At the end i will attach the docker-compose files.![image](https://github.com/nextcloud/docker/assets/19154725/10bf8235-a010-4305-81cf-01d1b8dc75d3)
I installed and configured nextcloud, after everything is fixed i go to continue setting it up, first the cron job. I already had a kuma, so i configured it to connect to my domain.com/cron.php but the output (even when appears as working in kuma is still the same) this is weird, the logs (Even with level swiched to DEBUG) not showing any info.
OS: ubuntu Docker with Nginx proxy manager, and cloudflare DNS
configurations made in nextcloud
.htcaccess
file added these lines:config/config.php
added these linesnextcloud docker compose
kuma config