-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: AH01276: Cannot serve directory: No matching DirectoryIndex (v24) #33454
Comments
I ran into the same issue. It is fair to say only one major to the next is valid to upgrade. But then an upgrade should not be attempted, leaving the data corrupted! |
This comment was marked as resolved.
This comment was marked as resolved.
I hit the same issue today after upgrading the container from 25.0.7.1 to 26.0.3.2.
This instance was migrated from ownCloud 10.11.0 to Nextcloud 25.0.6 a couple of months ago, then migrated to Docker with the Nextcloud Docker image 25.0.7. |
Strange. Before the upgrade, I checked the version with the browser at https://nextcloud.example.tld/apps/dashboard/. It turns out that after the upgrade, this URL does not work anymore (I was trying to refresh the page). Once I tried to access https://nextcloud.example.tld/, I've been redirected to https://nextcloud.example.tld/index.php/apps/dashboard/ which is a different URL but works perfectly well. |
Hi @Maxcodesthings - I'm sorry to see you ran into this problem. This is/was an issue with the official community NC Docker image, not with NC Server. The correct repository for this is https://github.com/nextcloud/docker not here. From the looks of it, this was probably addressed in nextcloud/docker#2018. Unfortunately since you're already in the situation, it can be a bit of a mess to untangle (but from the looks of it it is possible). See the issues referenced in the above PR for some approaches that have worked for other people, as well as more recent comments in nextcloud/docker#2015 like nextcloud/docker#2015 (comment) |
Closing since this is a docker image issue - see/follow-up as needed in nextcloud/docker#2015. |
Bug description
Nextcloud Upgrade to version 24 (tried latest and stable) results in::
AH01276: Cannot serve directory /var/www/html/apps/files/: No matching DirectoryIndex (index.php,index.html) found, and server-generated directory index forbidden by Options directive
I have looked over the internet for this issue, and I seem to be the only one. I stepped on some pretty url fix but that did not work. This is docker afterall it should be easier than this to upgrade.
Full log:
Edit: I notice that i went from major version 22 to 24, however the upgrade proceeded and downgrading is not possible. I get
Can't start Nextcloud because the version of the data (24.0.3.2) is higher than the docker image version (23.0.7.2) and downgrading is not supported. Are you sure you have pulled the newest image version?
So since this is not allowed my installation gets bricked? Why does the upgrade proceed if its not allowed to upgrade multiple major versions?
Ive tried forcing the upgrade to continue in the container as well:
Edit2: I have decided to try a fresh installation so i just renamed my volumes and pointed at stable image using this docker-compose:
There is now no data in the volumes as i renamed them they are new volumes however the error i get is the same:
Steps to reproduce
1.Install older version of nextcloud, I came from version 22
2. docker stop nextcloud
3. docker rm nextcloud
4. docker pull nextcloud:stable
5. docker-compose up -d
6. Experience error in log
Expected behavior
The error to not exist. I did not alter the .htaccess or any config file, i dont know why this would be happening.
Installation method
Official Docker image
Operating system
Debian/Ubuntu
PHP engine version
No response
Web server
No response
Database engine version
No response
Is this bug present after an update or on a fresh install?
Updated to a major version (ex. 22.2.3 to 23.0.1)
Are you using the Nextcloud Server Encryption module?
Encryption is Disabled
What user-backends are you using?
Configuration report
List of activated Apps
Nextcloud Signing status
No response
Nextcloud Logs
No response
Additional info
No response
The text was updated successfully, but these errors were encountered: