[GH-ISSUE #840] Dockerized Nextcloud + nginx-proxy-manager: "#" in folder name triggers error viewing jpg in nextcloud webinterface #713

New issue

Closed

opened 2026-02-26 06:34:06 +03:00 by kerem · 1 comment

kerem commented

2026-02-26 06:34:06 +03:00

Owner

Originally created by @chrnaum on GitHub (Jan 24, 2021).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/840

Checklist

Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image? → Yes.
Are you sure you're not using someone else's docker image? →Yes
What version of Nginx Proxy Manager is reported on the login page? → v2.7.3

Bug:

In nextcloud web-interface, click on a jpg inside a folder named "#Text", message "Error loading name.jpg" instead of jpg is shown.
If "#" is removed from folder name, jpg is displayed without problem.
If nextcloud is used without nginx-proxy-manager as reverse proxy, bug does not appear
Browsers tested: Chrome, Edge
nextcloud config.php is configured with "'enable_previews' => false," because of RPI4 performance

Setting:

Using Nextcloud 20.0.5 behind nginx-proxy-manager 2.7.3 both inside docker (5:20.10.2~~3-0~~debian-buster)
nginx-proxy-manager as proxy host with ssl certificate, force ssl, http/2, hsts, hsts subdomains, block common exploits, websockts support
Custom Nginx Configuration for nextcloud:
location /.well-known/carddav {return 301 $scheme://$host/remote.php/dav;}
location /.well-known/caldav {return 301 $scheme://$host/remote.php/dav;}
client_max_body_size 0;
proxy_max_temp_file_size 0;

Operating System

RPI4 B 8GB with Raspberry PI OS lite 32 bit + OMV5 + docker

Originally created by @chrnaum on GitHub (Jan 24, 2021). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/840 **Checklist** - Have you pulled and found the error with `jc21/nginx-proxy-manager:latest` docker image? → Yes. - Are you sure you're not using someone else's docker image? →Yes - What version of Nginx Proxy Manager is reported on the login page? → v2.7.3 Bug: - In nextcloud web-interface, click on a jpg inside a folder named "#Text", message "Error loading name.jpg" instead of jpg is shown. - If "#" is removed from folder name, jpg is displayed without problem. - If nextcloud is used without nginx-proxy-manager as reverse proxy, bug does not appear - Browsers tested: Chrome, Edge - nextcloud config.php is configured with "'enable_previews' => false," because of RPI4 performance Setting: - Using Nextcloud 20.0.5 behind nginx-proxy-manager 2.7.3 both inside docker (5:20.10.2~3-0~debian-buster) - nginx-proxy-manager as proxy host with ssl certificate, force ssl, http/2, hsts, hsts subdomains, block common exploits, websockts support - Custom Nginx Configuration for nextcloud: location /.well-known/carddav {return 301 $scheme://$host/remote.php/dav;} location /.well-known/caldav {return 301 $scheme://$host/remote.php/dav;} client_max_body_size 0; proxy_max_temp_file_size 0; **Operating System** - RPI4 B 8GB with Raspberry PI OS lite 32 bit + OMV5 + docker

kerem

2026-02-26 06:34:06 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-26 06:34:06 +03:00

Author

Owner

@chaptergy commented on GitHub (May 12, 2021):

Usually anchors (so everything after a # in an url) is not sent to the web server and stays in the browser. Maybe Nginx discards this information if it receives a # in the requested url? But this definitely sounds line a general nginx problem, not an NPM problem. NPM is just a frontend which generates configurations for nginx, so you will most likely have more luck searching in help forums for nginx.

@chaptergy commented on GitHub (May 12, 2021): Usually anchors (so everything after a `#` in an url) is not sent to the web server and stays in the browser. Maybe Nginx discards this information if it receives a `#` in the requested url? But this definitely sounds line a general nginx problem, not an NPM problem. NPM is just a frontend which generates configurations for nginx, so you will most likely have more luck searching in help forums for nginx.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/nginx-proxy-manager-NginxProxyManager#713

No description provided.

Rows
Columns