starred/nginx-proxy-manager-NginxProxyManager

Fork 0

mirror of https://github.com/NginxProxyManager/nginx-proxy-manager.git synced 2026-04-25 17:35:52 +03:00

[GH-ISSUE #533] nginx-proxy-manager not working with custom VH (for cryptpad) #452

New issue

Closed

opened 2026-02-26 06:32:54 +03:00 by kerem · 4 comments

kerem commented

2026-02-26 06:32:54 +03:00

Owner

Originally created by @BetterToAutomateTheWorld on GitHub (Jul 31, 2020).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/533

Hi,

First of all, thank you very much for nginx-proxy-manager, it's such a great tool !

What is troubling you?

Adapt the proper configuration for nginx-proxy-manager to be able to work with cryptpad docker container (it's not a cryptpad issue, it's a nginx configuration issue)

I want to get cryptpad container working with nginx-proxy-manager

Networking flow : FQDN port 80/443 > nginx-proxy-manager frontend > redirecting to 192.168.0.201:54926 > cryptpad container > running on 127.0.0.1:3000

More details about the issue

cryptpad is started and working.

curl :

curl -k https://192.168.0.201:54926
curl: (35) error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol

docker logs on the container :

FRESH MODE ENABLED
[2020-07-31T07:14:34.813Z] server available http://0.0.0.0:3000

But some issues are met from a template.js script :

In my web browser I've a white page instead of cryptpad.

Browser console error :

The Nginx configuration inside nginx-proxy-manager is pretty much a copy and paste of the cryptpad configuration with my values & adapted to nginx-proxy-manager way of working : https://pastebin.com/6Bg18Hjf
and the Nginx full VH is : https://pastebin.com/0xjdFzCB

I checked the 2 includes, include custom is empty, and include proxy contains :

  location / {                                                                                               
    add_header       X-Served-By $host;                                                                      
    proxy_set_header Host $host;                                                                             
    proxy_set_header X-Forwarded-Scheme $scheme;                                                             
    proxy_set_header X-Forwarded-Proto  $scheme;                                                             
    proxy_set_header X-Forwarded-For    $remote_addr;                                                        
    proxy_pass       $forward_scheme://$server:$port;                                                                   
  }

I even tried to simplify the Nginx config(manually, without GUI), but I've still an issue with the template.js* access, but it shouldn't be the case, i can see the proper config ...

If anyone can help, it would be really appreciated, it seems like I miss something which is overwriting some parameters in the VH, and crash the template.js script from cryptpad, which should be normally accessible and working... :(

Any help appreciated, thank you !

Originally created by @BetterToAutomateTheWorld on GitHub (Jul 31, 2020). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/533 Hi, First of all, thank you very much for nginx-proxy-manager, it's such a great tool ! ### What is troubling you? Adapt the proper configuration for nginx-proxy-manager to be able to work with cryptpad docker container (it's not a cryptpad issue, it's a nginx configuration issue) I want to get cryptpad container working with nginx-proxy-manager Networking flow : FQDN port 80/443 > nginx-proxy-manager frontend > redirecting to 192.168.0.201:54926 > cryptpad container > running on 127.0.0.1:3000 ### More details about the issue cryptpad is started and working. curl : ``` curl -k https://192.168.0.201:54926 curl: (35) error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol ``` docker logs on the container : ``` FRESH MODE ENABLED [2020-07-31T07:14:34.813Z] server available http://0.0.0.0:3000 ``` But some issues are met from a **template.js** script : ![image](https://user-images.githubusercontent.com/8619233/89044722-e3670e80-d339-11ea-9919-0136ab9c36f9.png) In my web browser I've a white page instead of cryptpad. Browser console error : ![image](https://user-images.githubusercontent.com/8619233/89044849-14474380-d33a-11ea-8ce1-ae9c83742faf.png) The Nginx configuration inside nginx-proxy-manager is pretty much a copy and paste of the cryptpad configuration with my values & adapted to nginx-proxy-manager way of working : https://pastebin.com/6Bg18Hjf and the Nginx full VH is : https://pastebin.com/0xjdFzCB I checked the 2 includes, include custom is empty, and include proxy contains : ``` location / { add_header X-Served-By $host; proxy_set_header Host $host; proxy_set_header X-Forwarded-Scheme $scheme; proxy_set_header X-Forwarded-Proto $scheme; proxy_set_header X-Forwarded-For $remote_addr; proxy_pass $forward_scheme://$server:$port; } ``` I even tried to simplify the Nginx config(manually, without GUI), but I've still an issue with the **template.js*** access, but it shouldn't be the case, i can see the proper config ... If anyone can help, it would be really appreciated, it seems like I miss something which is overwriting some parameters in the VH, and crash the **template.js** script from cryptpad, which should be normally accessible and working... :( Any help appreciated, thank you !

kerem

2026-02-26 06:32:54 +03:00

closed this issue
added the
stale

product-support
labels

kerem commented

2026-02-26 06:32:55 +03:00

Author

Owner

@Hajibey commented on GitHub (Jul 18, 2023):

Sorry to necrobump, but did you ever manage to make Cryptpad work with NPM?

@Hajibey commented on GitHub (Jul 18, 2023): Sorry to necrobump, but did you ever manage to make Cryptpad work with NPM?

kerem commented

2026-02-26 06:32:55 +03:00

Author

Owner

@binerf commented on GitHub (Jul 20, 2023):

On my side, I've created 2 hosts in NPM (declared in my DNS) pointing the same cryptpad container on port 3000.

In the cryptpad config.js file I've setup:

[...]
    httpUnsafeOrigin: "https://cryptpad_first.mydomain.com",
[...]
     httpSafeOrigin: "https://cryptpad_second.mydomain.com",
[...]
    httpAddress: '::',
[...]

And it works.

@binerf commented on GitHub (Jul 20, 2023): On my side, I've created 2 hosts in NPM (declared in my DNS) pointing the same cryptpad container on port 3000. In the cryptpad config.js file I've setup: ``` [...] httpUnsafeOrigin: "https://cryptpad_first.mydomain.com", [...] httpSafeOrigin: "https://cryptpad_second.mydomain.com", [...] httpAddress: '::', [...] ``` And it works.

kerem commented

2026-02-26 06:32:55 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Mar 27, 2024):

Issue is now considered stale. If you want to keep it open, please comment 👍

@github-actions[bot] commented on GitHub (Mar 27, 2024): Issue is now considered stale. If you want to keep it open, please comment :+1:

kerem commented

2026-02-26 06:32:55 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (May 6, 2025):

Issue was closed due to inactivity.

@github-actions[bot] commented on GitHub (May 6, 2025): Issue was closed due to inactivity.

kerem referenced this issue

2026-02-26 07:38:37 +03:00

[PR #452] [MERGED] Bump websocket-extensions from 0.1.3 to 0.1.4 in /docs #3248

kerem referenced this issue

2026-02-26 07:38:37 +03:00

[PR #454] [MERGED] v2.3.1 #3250

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#452

No description provided.

Rows
Columns