Support intro
Sorry to hear you’re facing problems. 
The community help forum (help.nextcloud.com) is for home and non-enterprise users. Support is provided by other community members on a best effort / “as available” basis. All of those responding are volunteering their time to help you.
If you’re using Nextcloud in a business/critical setting, paid and SLA-based support services can be accessed via portal.nextcloud.com where Nextcloud engineers can help ensure your business keeps running smoothly.
Getting help
In order to help you as efficiently (and quickly!) as possible, please fill in as much of the below requested information as you can.
Before clicking submit: Please check if your query is already addressed via the following resources:
- Official documentation (searchable and regularly updated)
- How to topics and FAQs
- Forum search
(Utilizing these existing resources is typically faster. It also helps reduce the load on our generous volunteers while elevating the signal to noise ratio of the forums otherwise arising from the same queries being posted repeatedly).
Some or all of the below information will be requested if it isn’t supplied; for fastest response please provide as much as you can. 
The Basics
- Nextcloud Server version (e.g., 29.x.x):
- Latest AIO
- Operating system and version (e.g., Ubuntu 24.04):
- Ubuntu 24.04
- Web server and version (e.g, Apache 2.4.25):
- NA
- Reverse proxy and version _(e.g. nginx 1.27.2)
- Caddy 2.8.4
- PHP version (e.g, 8.3):
- 8.3.13
- Is this the first time you’ve seen this error? (Yes / No):
- Yes
- When did this problem seem to first start?
- During install
- Installation method (e.g. AIO, NCP, Bare Metal/Archive, etc.)
- Docker AIO
- Are you using Cloudflare, mod_security, or similar? (Yes / No)
- No
Summary of the issue you are facing:
I’m trying to install the Nextcloud AIO using the instructions for an existing reverse proxy (with Apache exposed via port 11000) and I can’t get it to start up properly. The master container starts without any apparent errors, but attempting to connect to the admin port serves up a 403 and triggers an error from the container:
[(13)Permission denied] [client: 172.17.0.1] [AH00035: access to / denied (filesystem path '/var/www/docker-aio/php') because search permissions are missing on a component of the path]
I suspect this is because I’m trying to run this behind a forward proxy as well (the host system accesses the internet through tinyproxy for some basic domain filtering purposes, and does not have direct internet access,) - the Docker daemon is configured to use the proxy and pulls down the master container without issue but there’s no other running containers when, as far as I’m aware, the master container should be spawning other containers by this point. Attempts to debug this myself have been fruitless because there’s no other error messages from the container and there seems to be literally no other instances of the access error anywhere on the internet for Nextcloud. Searching for advice about setting up behind a forward proxy turns nothing up either because the search results are completely full of various vague synonyms for reverse proxies instead.
Is there a way to configure the AIO to run with a forward proxy, or is this a completely unsupported configuration? Is this even the reason it’s breaking?
Steps to replicate it (hint: details matter!):
- Set up Docker on a system with indirect web access via a forward proxy
- Install the AIO container using the docker run command
- Attempt to connect to the container on port 8080
