nextcloud / nextcloud/nextcloud-docker-dev

Page not found after running docker compose up on rancher desktop

Open
#322 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
PHP
Stars
190
Forks
103
Avg merge
4h 36m
Merged PRs (30d)
1

Description

Hi :)

I cloned the repository, ran ./bootstrap.sh groupfolders inside the repository and started everything with docker compose up -d nextcloud. Everything looks fine so far. I got no errors and can see all container up and running.

When I try to access nextcloud.local, I get a 404 Page not found. Starting nextcloud 2 with docker compose up -d nextcloud2 I get the same issue using nextcloud.local and/or nextcloud2.local. When I then use nextcloud2.local:8211, I get an login screen. I assume its because a port is exposed for nextcloud2. The PORTBASE is defined as 821 in the .env file. The DOCKER_SUBNET in .env is 192.168.21.0/24.

I haven't modified any config file in the repo.

If the content of any of the files is needed for further analysis or any other information, please say what is needed and I will post it :)

As I am not that deep into Docker Compose and Rancher Desktop, I can't find a solution to make it work. Also asking ChatGPT hasn't helped me.

What can I do or what do I have to change in the config files to make it work?

P.S. Using the standalone version (run --rm -p 8080:80 ghcr.io/juliushaertl/nextcloud-dev-php83:latest) works fine.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with bootstrap.sh groupfolders, the docker compose commands for nextcloud and nextcloud2, and the PORTBASE and DOCKER_SUBNET values in .env. Compare the compose setup with the standalone command that works, then reproduce the 404 at nextcloud.local and the login screen at nextcloud2.local:8211. Done means the compose services are reachable at the documented hostnames without requiring an unexpected port.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker-compose, php
Domain
devops, infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.