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
- Operating system and version (e.g., Ubuntu 24.04):
Debian 12
- Web server and version (e.g, Apache 2.4.25):
latest of nextcloud
- Reverse proxy and version _(e.g. nginx 1.27.2)
FRP (Fast Reverse Proxy) and nginx 1.22.1
- PHP version (e.g, 8.3):
latest of nextcloud
- Is this the first time you’ve seen this error? (Yes / No):
No
- When did this problem seem to first start?
Ever since I started trying to set it up
- Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
AIO
- Are you using CloudfIare, mod_security, or similar? (Yes / No)
FRP (Fast Reverse Proxy)
Summary of the issue you are facing:
Hi, I’m trying to setup Nextcloud on my homeserver that I expose to the Internet using FRP (Fast Reverse Proxy) and a rented VPS. So far, that has worked just fine for all my services, except nextcloud.
I’m running my AIO using this command:
sudo docker run \
--init \
--sig-proxy=false \
--name nextcloud-aio-mastercontainer \
--restart always \
--publish 8080:8080 \
--env APACHE_PORT=11000 \
--env APACHE_IP_BINDING=0.0.0.0 \
--env APACHE_ADDITIONAL_NETWORK="" \
--env SKIP_DOMAIN_VALIDATION=true \
--volume nextcloud_aio_mastercontainer:/mnt/docker-aio-config \
--volume /var/run/docker.sock:/var/run/docker.sock:ro \
nextcloud/all-in-one:latest
and this is my config for FRP (frpc.toml):
[[proxies]]
name = "aio"
type = "http"
localPort = 8080
customDomains = ["<IPv4 Address of rented VPS>"]
[[proxies]]
name = "cloud_https2https"
type = "https"
customDomains = ["cloud.domain.org"]
[proxies.plugin]
type = "https2https"
localAddr = "127.0.0.1:443"
crtPath = "/etc/frp/cloud.crt"
keyPath = "/etc/frp/cloud.key"
hostHeaderRewrite = "cloud.domain.org"
requestHeaders.set.x-from-where = "frp"
Finally, this is my NGINX config:
server {
server_name "cloud.domain.org";
location / {
proxy_pass https://<IP>:<Port>;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
}
listen 443 ssl; # managed by Certbot
ssl_certificate /etc/letsencrypt/live/cloud.domain.org/fullchain.pem; # managed by Certbot
ssl_certificate_key /etc/letsencrypt/live/cloud.domain.org/privkey.pem; # managed by Certbot
include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot
}
server {
if ($host = cloud.domain.org) {
return 301 https://$host$request_uri;
} # managed by Certbot
server_name "cloud.domain.org";
listen 80;
return 404; # managed by Certbot
}
server {
server_name "<IP>";
location / {
proxy_pass https://<IP>:8080;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
}
}
When I try to access the AIO Webinterface using the IP of my VPS I get
The page you requested was not found.
Sorry, the page you are looking for is currently unavailable.
Please try again later.
The server is powered by frp.
Faithfully yours, frp.
and opening cloud.domain.org yields:
502 Bad Gateway
nginx/1.22.1
found several other users facing the same problem but could never find an actual solution just one person saying I would need a full manual installation, but never elaborated on what exactly to do.
Has anyone ever got this type of setup to work? FRP is really one of the only solutions that are actually viable since Cloudflare Tunnels don’t support all protocols I need and port forwarding is not an option.
Any help is appreciated.
Steps to replicate it (hint: details matter!):
- Run AIO & FRP
- Configure FRP using the correct Ports etc.
- Notice you cannot access Nextcloud
Log entries
Nextcloud
Please provide the log entries from your Nextcloud log that are generated during the time of problem (via the Copy raw option from Administration settings->Logging screen or from your nextcloud.log located in your data directory). Feel free to use a pastebin/gist service if necessary.
Not possible since nextcloud was never actually running
Web Browser
If the problem is related to the Web interface, open your browser inspector Console and Network tabs while refreshing (reloading) and reproducing the problem. Provide any relevant output/errors here that appear.
Can't access Nextcloud
Web server / Reverse Proxy
The output of your Apache/nginx/system log in /var/log/____:
N/A
Configuration
Nextcloud
The output of occ config:list system or similar is best, but, if not possible, the contents of your config.php file from /path/to/nextcloud is fine (make sure to remove any identifiable information!):
N/A
Apps
The output of occ app:list (if possible).
Tips for increasing the likelihood of a response
- Use the
preformatted textformatting option in the editor for all log entries and configuration output. - If screenshots are useful, feel free to include them.
- If possible, also include key error output in text form so it can be searched for.
- Try to edit log output only minimally (if at all) so that it can be ran through analyzers / formatters by those trying to help you.