Proxy Settings "Nginx Proxy Manager" web UI #112

Haecky · 2023-08-17T22:22:49Z

I need settings for "Nginx Proxy Manager" web UI

how do you secure the login?

Please help

routerino · 2023-08-22T23:44:54Z

As I do not actively use nginx proxy manager, and given the lack of supporting detail, I don't have an answer for you.

Information about security can be found in SECURITY.MD

ithakaa · 2023-08-25T12:32:42Z

I need settings for "Nginx Proxy Manager" web UI

how do you secure the login?

Please help

I have a working install

du724931566 · 2023-09-13T09:14:14Z

also need settings for "Nginx Proxy Manager" web UI, please
thanks a lot

ithakaa · 2023-09-14T07:45:03Z

Sorry for the late reply

Do the usual stuff for a host entry, leave custom locations empty, and then replace <server_ip> and add the below to the advanced section of Nginx Proxy Manager for the host

proxy_buffer_size   128k;
proxy_buffers   4 256k;
proxy_busy_buffers_size   256k; 
proxy_ssl_server_name on;
location /web/ {
    proxy_set_header        Host                $http_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;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection \"upgrade\";
    proxy_redirect http:// https://;
    proxy_pass http://<server_ip>:8090/web/;
}
location / {
    proxy_set_header        Host                $http_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;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection \"upgrade\";
    add_header Strict-Transport-Security "max-age=15552000; includeSubDomains" always;
    proxy_redirect http:// https://;
    proxy_buffering off;
    proxy_intercept_errors  on;
    proxy_http_version      1.1;
    proxy_pass http://<server_ip>:8088/;
  }

du724931566 · 2023-09-19T04:29:47Z

Sorry for the late reply

Do the usual stuff for a host entry, leave custom locations empty, and then replace <server_ip> and add the below to the advanced section of Nginx Proxy Manager for the host

proxy_buffer_size   128k;
proxy_buffers   4 256k;
proxy_busy_buffers_size   256k; 
proxy_ssl_server_name on;
location /web/ {
    proxy_set_header        Host                $http_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;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection \"upgrade\";
    proxy_redirect http:// https://;
    proxy_pass http://<server_ip>:8090/web/;
}
location / {
    proxy_set_header        Host                $http_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;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection \"upgrade\";
    add_header Strict-Transport-Security "max-age=15552000; includeSubDomains" always;
    proxy_redirect http:// https://;
    proxy_buffering off;
    proxy_intercept_errors  on;
    proxy_http_version      1.1;
    proxy_pass http://<server_ip>:8088/;
  }

excuse me,i have try several times to put this into Custom Nginx Configuration
but it warming : Please note, that any add_header or set_header directives added here will not be used by nginx. You will have to add a custom location '/' and add the header in the custom config there.

the both proxy_pass settings had been changed to my container ip and port

the container is running ,web up, but the api test failed
i dont konw what should i do now, so plagued
i used Nginx Proxy Manager
Looking forward to your help

ithakaa · 2023-09-19T05:01:01Z

Do you have a properly working NPM with an SSL CRT you are using with other applications ?

appleimperio · 2023-09-28T01:31:40Z

@ithakaa I try your config and I'm getting the error "Client sent an HTTP request to an HTTPS server." but I think It's because in the

location /web/ {
    proxy_set_header        Host                $http_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;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection \"upgrade\";
    proxy_redirect http:// https://;
    proxy_pass http://<server_ip>:8090/web/;

the last line should be https. but even when I change it I get a withe screen no errors just when accessing the ui the other part works fine. Any idea what I'm doing wrong?

ithakaa · 2023-09-28T01:46:59Z

the last line should be https.

it works for me
are you using a valid ssl crt with NPM ?

appleimperio · 2023-09-28T01:51:48Z

Yes, I already have external clients running I just want to try the web-ui. Just to be clear the ports you use there. the location /web/ port is the one I have configured in Headscale-ui and the location / is the port I have configured for Headscale?

ithakaa · 2023-09-28T02:14:37Z

I've provided screenshots, might be easier this way, let me know how you go

https://github.com/ithakaa/headscale-ui-npm/blob/main/README.md

appleimperio · 2023-09-28T02:43:01Z

Thank you very much. Your installation is with docker?

ithakaa · 2023-09-28T02:50:05Z

Your installation is with docker?

yes

appleimperio · 2023-09-28T03:03:14Z

This is my compose

version: '3.5'
services:
  headscale:
    container_name: headscale
    image: headscale/headscale:latest
    restart: unless-stopped
    #ports:
    #  - 8011:8080
    volumes:
      - /srv/dev-disk-by-uuid-36ffb5ee-7f60-4aea-bc0c-45c47cfbd3f7/containersdata/headscale/config:/etc/headscale
      - /srv/dev-disk-by-uuid-36ffb5ee-7f60-4aea-bc0c-45c47cfbd3f7/containersdata/headscale/data:/var/lib/headscale
    command: headscale serve
    networks:
      nginxproxymanager_default:

  headscale-ui:
    image: ghcr.io/gurucomputing/headscale-ui:latest
    restart: unless-stopped
    container_name: headscale-ui
    #ports:
    #  - 8443:443 # Use the port of your choice, but map it to 443 on the container
    networks:
      nginxproxymanager_default:  

networks:
  nginxproxymanager_default:
    external: true

can you share your compose. that way I will have everything the same. Thanks

ithakaa · 2023-09-28T03:11:28Z

version: '3.6'
services:
  headscale:
    container_name: headscale
    image: headscale/headscale:latest
    command: headscale serve
    restart: unless-stopped
    ports:
      - '8089:9090'
      - '8088:8080'
    volumes:
      - ./data:/etc/headscale
      - ./config:/var/lib/headscale      
  headscale-ui:
    image: ghcr.io/gurucomputing/headscale-ui:latest
    restart: unless-stopped
    container_name: headscale-ui
    ports:
      - 8090:80

appleimperio · 2023-09-30T23:54:37Z

@ithakaa Thank for all your help. It was right since the beginning the whole problem was the Browser cache.

mackandelius · 2023-10-16T10:12:01Z

@ithakaa Hi, so I am using your NPM config and while it generally works fine, the server isn't available through https://:8080/ and just errors with SSL_ERROR_RX_RECORD_TOO_LONG, just removing the 8080 port makes it all work fine.

This is mostly an annoyance since I can technically always remove the port from the register urls, but is annoying, and might be breaking taildrop, but I am not sure yet. (the send to list is entirely empty).

You wouldn't have any ideas on why this is happening?
Some headscale config setting that I shouldn't have changed or something.

ithakaa · 2023-10-16T19:27:42Z

the server isn't available through https://:8080/ and just errors with SSL_ERROR_RX_RECORD_TOO_LONG, just removing the 8080 port makes it all work fine.

Are you getting the ssl error when registering nodes or when accessing the headscale ui?

mackandelius · 2023-10-17T22:21:46Z

I am getting that error when registering, but accessing the headscale UI I am pretty sure isn't something you should be doing with https://:8080/web, however it errors in the same way.

Using any port not in use of course gives an unable to connect error.

ithakaa · 2023-10-17T23:56:10Z

you need to register via http://server_ip:8080

mackandelius · 2023-10-18T17:08:56Z

Which is what doesn't work, to register I need to manually remove the port from the URL, otherwise I just get that SSL error.

appleimperio · 2023-10-18T19:59:21Z

@mackandelius if the address start with https you cannot use the port 8080. just use your domain. example https://mydomain.com/web

ithakaa · 2023-10-18T20:02:12Z

otherwise I just get that SSL error.

Are you using the headscale-ui docker image that includes headscale and headscale-ui?

mackandelius · 2023-10-20T06:04:12Z

@appleimperio that is what I am doing, but the app and program both direct you towards a url using the :8080 port, if this is expected behavior then that is clunky and not worth it.

mackandelius · 2023-10-20T06:06:43Z

@ithakaa sorry, forgot to mention that I am not, forgot the exact reasons now, but was actually just easier installing headsclae to the server directly, headscale-ui is running in docker.
Which means it might be that docker network I am missing.

ithakaa · 2023-10-20T06:11:04Z

headscale-ui is running in docker.

To be absolutely honest, I actually wouldn't even bother with headscale-ui

The headscale cli is super simple

mackandelius · 2023-10-20T20:42:52Z

Regardless, doesn't headscale require HTTPS at least partially?
Since lines in the config about setting up letsencrypt?

ithakaa · 2023-10-22T03:52:00Z

Regardless, doesn't headscale require HTTPS at least partially? Since lines in the config about setting up letsencrypt?

Sorry I can't be any further assistance, it seems you need to look into headscale a little more deeply before you start posting requests for help

zhzy0077 · 2024-01-10T03:50:16Z

For someone who also runs into the same issue as I did, I have to trun OFF the "Cache Assets" for the proxy host and things would work without any tricks.

It's actually because assets go to different location which doesn't recognize the /web path:

https://github.com/NginxProxyManager/nginx-proxy-manager/blob/develop/docker/rootfs/etc/nginx/conf.d/include/assets.conf

Haecky changed the title ~~Headscale-ui doesn't want to connect~~ Proxy Settings "Nginx Proxy Manager" web UI Aug 19, 2023

routerino added the question Further information is requested label Aug 22, 2023

routerino closed this as completed Oct 10, 2023

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Proxy Settings "Nginx Proxy Manager" web UI #112

Proxy Settings "Nginx Proxy Manager" web UI #112

Haecky commented Aug 17, 2023 •

edited

routerino commented Aug 22, 2023 •

edited

ithakaa commented Aug 25, 2023

du724931566 commented Sep 13, 2023

ithakaa commented Sep 14, 2023 •

edited

du724931566 commented Sep 19, 2023

ithakaa commented Sep 19, 2023

appleimperio commented Sep 28, 2023

ithakaa commented Sep 28, 2023

appleimperio commented Sep 28, 2023

ithakaa commented Sep 28, 2023 •

edited

appleimperio commented Sep 28, 2023

ithakaa commented Sep 28, 2023

appleimperio commented Sep 28, 2023

ithakaa commented Sep 28, 2023 •

edited

appleimperio commented Sep 30, 2023

mackandelius commented Oct 16, 2023

ithakaa commented Oct 16, 2023

mackandelius commented Oct 17, 2023 •

edited

ithakaa commented Oct 17, 2023

mackandelius commented Oct 18, 2023

appleimperio commented Oct 18, 2023

ithakaa commented Oct 18, 2023

mackandelius commented Oct 20, 2023

mackandelius commented Oct 20, 2023 •

edited

ithakaa commented Oct 20, 2023

mackandelius commented Oct 20, 2023

ithakaa commented Oct 22, 2023

zhzy0077 commented Jan 10, 2024

Proxy Settings "Nginx Proxy Manager" web UI #112

Proxy Settings "Nginx Proxy Manager" web UI #112

Comments

Haecky commented Aug 17, 2023 • edited

routerino commented Aug 22, 2023 • edited

ithakaa commented Aug 25, 2023

du724931566 commented Sep 13, 2023

ithakaa commented Sep 14, 2023 • edited

du724931566 commented Sep 19, 2023

ithakaa commented Sep 19, 2023

appleimperio commented Sep 28, 2023

ithakaa commented Sep 28, 2023

appleimperio commented Sep 28, 2023

ithakaa commented Sep 28, 2023 • edited

appleimperio commented Sep 28, 2023

ithakaa commented Sep 28, 2023

appleimperio commented Sep 28, 2023

ithakaa commented Sep 28, 2023 • edited

appleimperio commented Sep 30, 2023

mackandelius commented Oct 16, 2023

ithakaa commented Oct 16, 2023

mackandelius commented Oct 17, 2023 • edited

ithakaa commented Oct 17, 2023

mackandelius commented Oct 18, 2023

appleimperio commented Oct 18, 2023

ithakaa commented Oct 18, 2023

mackandelius commented Oct 20, 2023

mackandelius commented Oct 20, 2023 • edited

ithakaa commented Oct 20, 2023

mackandelius commented Oct 20, 2023

ithakaa commented Oct 22, 2023

zhzy0077 commented Jan 10, 2024

Haecky commented Aug 17, 2023 •

edited

routerino commented Aug 22, 2023 •

edited

ithakaa commented Sep 14, 2023 •

edited

ithakaa commented Sep 28, 2023 •

edited

ithakaa commented Sep 28, 2023 •

edited

mackandelius commented Oct 17, 2023 •

edited

mackandelius commented Oct 20, 2023 •

edited