-
-
Notifications
You must be signed in to change notification settings - Fork 128
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] WebInterface got 404 for apps installed on custom path #329
Comments
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid. |
Could you try executing this inside the container: rm -rf "/app/www/public/custom_apps"
ln -s "/config/www/nextcloud/custom_apps" "/app/www/public/custom_apps"
lsiown abc:abc "/config/www/nextcloud/custom_apps" "/app/www/public/custom_apps" |
Thanks for your reply. Would it be possible to provide a permanent solution in the next release? |
Sorry, I should have mentioned that was kind of a test to see if it fixed the problem. Another test (that actually might be a permanent fix) would be to add a location to location /custom_apps {
root /config/www/nextcloud/custom_apps;
# try_files $uri $uri/; # this line might need to be uncommented, or might need to be modified, but i'm not sure exactly yet
} I would add this directly above line 158 that reads I am not positive that this will work correctly, but if it does you shouldn't need the symlink, and this change will be persistent. If this doesn't work, the concept should still be correct, but we might need additional configuration lines inside the location braces. As for a permanent fix being included in the image, I know nextcloud docs mention |
I've got the same issue and unfortunately creating this entry in the As I currently understand the main issue is the possibility to create a custom apps folder and refer to it in the nextcloud config.php. The only valid location (without creating a symlink) for it is in the nextcloud server root which has moved now to /app/ (from /config/). |
It's also possible to make a volume on your container with the path |
Yes, that works, too. I wasn't really considering this because I somehow thought the folder gets deleted when I recreate the container (due to nextcloud installing again in the |
I'm going to mark this as resolved with the best recommendation being the volume at this point. |
I am OK with that. |
There is now documentation for a volume for custom apps https://github.com/linuxserver/docker-nextcloud#custom-app-directories |
Is there an existing issue for this?
Current Behavior
after the update from 26.0.2 to 27.0.0 all apps installed on a custom_apps location does not shown in Web Interface anymore. There are working as expected via other APIs like REST or DAV. So calender is still synchronizing with smartphone for instance.
The browser debugger shows that all requests are running into a 404 for apps that are installed on a other folder than /apps.
Expected Behavior
App are shown on Web Interface.
Steps To Reproduce
sudo docker exec -it nextcloud /bin/bash
notes
app for instance. if you try to hit the notes icon after a page reload you will see nothing.Workaround:
the current workaround I see but not checked yet is to move all my apps from custom_apps to apps folder.
Environment
CPU architecture
x86-64
Docker creation
sudo docker run -d \ --name=nextcloud \ -e PUID=1000 \ -e PGID=1000 \ -e TZ=Etc/UTC \ -p 443:443 \ --restart unless-stopped \ lscr.io/linuxserver/nextcloud:latest
The text was updated successfully, but these errors were encountered: