Hi!
I need some help with installing Nextcloud using Docker Compose.
Nextcloud installs successfully and is accessible at http://ip:8080, but I would like it to be available at http://ip/Nextcloud.
I tried changing the Apache configuration, and in that case, Nextcloud does open at the desired address (ip/Nextcloud), but then the files stop working or become inaccessible (e.g., errors when loading or opening them).
Has anyone faced a similar issue or can advise how to properly configure the /Nextcloud path when accessing through a web server?
you started a topic in development category. This category is intended for active developers of the core or apps in the Nextcloud ecosystem.
From the description in your topic, it is not clear if you are seeking help and advice about a concrete problem you have or you want to actually develop the corresponding solution.
Please specify explicitly the required information to help you best. These are:
What you want to achieve
What you have done so far
What is failing
What you expect from the forum community
Without additional information the community members cannot help you in an efficient manner. Please keep in mind that the help here in the forum are mostly based on work of volunteers and thus it is just fair to reduce the burden on them.
If you accidentally posted in the category, just give a hint and a moderator can move the corresponding category.
Thank you for your message. Yes, I did mistakenly post in the wrong category — sorry for the inconvenience.
My issue is that I’m trying to change the default Nextcloud URL from the root path to http://IP/nextcloud, but I’m encountering an error when uploading files.
I would appreciate any help or advice on how to properly configure the URL path.
However, the problem with file uploads remains. Currently, it tries to upload files using the WebDAV URL: http://192.168.31.14/nextcloud/remote.php/dav/files/Mexanik385
But I need it to upload files using: http://192.168.31.14:8081/remote.php/dav/files/Mexanik385
Or somehow adjust the accessibility of this file URL for the new path.
If you have any suggestions on how to fix this WebDAV path issue or how to properly configure file upload to work with the /nextcloud subpath, I would really appreciate it!
nobody knows as you didn’t provide further details.
as Nextcloud suggest the right IP i assume there is something outside like reverse proxy etc..
I would look into the logs of you apachereverseproxy and docker logs (docker compose logs nextcloud) also review nextcloud.log- as your webdav test shows as Nextcloud error the request must reach the system and you could see what is missing - proxy headers, etc..