You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file describes a setup that cannot be donne with the current (v2.12.1) version of NGM.
Steps to reproduce
The 2nd part of the example, to setup the port for federation, shows to setup a proxy host with a specific port. This feature is not currently functioning. Here is a screenshot showing the error message that hostname cannot have port specifications
To reproduce, use a domain name with a ":" inside of it to have the match pattern show the error.
Trying to add a 2nd proxy host without the source port to add the advanced section (listen 8448 ssl http2;) is also impossible since there is already a proxy host for the domain.
Possible avenues to fix
There is a new streams section in NGM that can redirect TCP and UDP traffic. The possible problem is that this doesn't help with SSL certificates which are handled by NGM on port 80 and 443 for HTTP and HTTPS. I am not knowledgeable enough to know if federation needs the certificates or how to have NGM make this work since I believe federation uses HTTPS.
Also, there is a section to add configs to nginx descibed here: https://nginxproxymanager.com/advanced-config/#custom-nginx-configurations
A possible alternative would be to add the config manually for the federation port though I am unsure how you could link it with the SSL certificates generation.
The text was updated successfully, but these errors were encountered:
dullin
changed the title
Nginx Proxy Manager fronting example is not compatible with current NGM feature set.
Nginx Proxy Manager fronting example is not compatible with current NGM features
Oct 28, 2024
Problem description
An example file to have NGM (Nginx Proxy Manager) is currenlty available here : https://github.com/spantaleev/matrix-docker-ansible-deploy/tree/master/examples/reverse-proxies/nginx-proxy-manager
This file describes a setup that cannot be donne with the current (v2.12.1) version of NGM.
Steps to reproduce
The 2nd part of the example, to setup the port for federation, shows to setup a proxy host with a specific port. This feature is not currently functioning. Here is a screenshot showing the error message that hostname cannot have port specifications
To reproduce, use a domain name with a ":" inside of it to have the match pattern show the error.
Trying to add a 2nd proxy host without the source port to add the advanced section (listen 8448 ssl http2;) is also impossible since there is already a proxy host for the domain.
Possible avenues to fix
There is a new streams section in NGM that can redirect TCP and UDP traffic. The possible problem is that this doesn't help with SSL certificates which are handled by NGM on port 80 and 443 for HTTP and HTTPS. I am not knowledgeable enough to know if federation needs the certificates or how to have NGM make this work since I believe federation uses HTTPS.
Also, there is a section to add configs to nginx descibed here: https://nginxproxymanager.com/advanced-config/#custom-nginx-configurations
A possible alternative would be to add the config manually for the federation port though I am unsure how you could link it with the SSL certificates generation.
The text was updated successfully, but these errors were encountered: