in case of problems with my nextcloud instance under ispconfig and the recomodations not to run nextcloud under ispconfig I think I install Docker an put Nextcloud in docker. But Docker and Ispconfig uses 8080 as WEB Port. What do you recomand how to solve this?
I've run Nextcloud (and before that ownCloud) for years under ISPConfig without issue. It runs as a normal site. What problems have you encountered?
me too, but now NC says php 8.2 will not be supported in future release. so I changed to 8.3 and NC did not run any more. When I ask why in the forum, many responses came that it is not good to run NC und ISPConfig, better use a docker instance or a seperate server. I use NC mostly for auto upload pictures from my Smartphone as a Backup and my contacts. we are Jusr two useres.
Yes - I, and many others, have issues with their support policies and aggressive releases. Wished I stayed on ownCloud since stability is imho the first requirement of databases - particularly synchronised databases. Hence, like many, my servers live within the Debian lifecycle - unlike Nextcloud. I bump along on the last supported verson of NC (updating from 29 to 30 last month) on Bookworm. Trixie should be with us in a couple of months and that has native php8.4. I'll spin up a VM later this week and see if it is happy with my NC instance. Trixie has been rock solid on some of my disktops for some months so the supported server version should be good. I note ISPConfig now supports Trixie/Testing so if that doesn't work I may take a serious look at reverting to ownCloud as I use it only as a database and don't use any of the apps. The declared policy of NC is to leave its roots as a shared database to become an 'Office' product to compete with Office 365 and Google Apps. Which is at odds with my requirements.
