v2.13.0 React UI

[jc21]

Almost complete, this PR is where I'm keeping the draft release notes as I work on them.

---

• 🚀 5 years overdue, a new React interface with updated Tabler UI
• ✌️ 5 years overdue, also, backend refactor from CommonJS to ESM
• 🥳 New setup wizard; no more default initial user (but keeps the env vars for advanced users)
• 🙈 Use biomejs for linting instead of eslint
• 👍 Refactor backend to async/await functions
• 🌎 Proper and complete translation support, see the documentation to contribute
• 🌗 Light/Dark mode
• 👾 Syntax highlighting for text inputs for Nginx/HTML etc
• ✅ Removed the Let's Encrypt email and TOS agreement from certificate requests

Upgrade path notes:

• No changes to Database
• No changes to Nginx/Openresty
• No changes to Nginx template engine
• Certbot is upgraded to v5 in the base image and this will flow through here, expect some DNS provider problems.

[lastsamurai26]

If I want to create a certificate that does not have its own plugin, I have to use dnsmulti, which uses the lego plugin, but I cannot use dnsmulti if I have not previously installed go in the container.
Now to the actual issue. Hetzner has changed the API, and the Hetzner plugin that comes with it cannot handle it, but Lego (certbot-dns-multi) has integrated the new API, albeit with version 4.27, but Nginx proxy manager only provides version 4.9, so the new API cannot be used.
It is just an info

I hope you understand what I mean, but I have now found a way to use the new version by editing the certbet-dns-plugins.json.

[jc21]

@sopex

From my POV the contrast is not enough and it's a bit tiresome to the eyes but it could just be me.

I tend to agree. Especially when viewing modal dialogs. I've just applied the Tabler theme, but can definitely be tweaked later.

@lastsamurai26 I would suggest creating a PR for this to test certbot-dns-multi 4.27.0. In the develop branch, just edit this file, then let CI build the image you can test with. As for Golang, you could extend the image with your own Dockerfile and have docker-compose build it.

# Dockerfile
FROM jc21/nginx-proxy-manager:latest
RUN apt-get update \
  && apt-get -y install golang \
  && apt-get clean \
  && rm -rf /var/lib/apt/lists/*

# docker-compose.yml
services:
  npm:
    build:
      context: .
      dockerfile: Dockerfile
# ...

[lastsamurai26]

@lastsamurai26 I would suggest creating a PR for this to test certbot-dns-multi 4.27.0. In the develop branch, just edit this file, then let CI build the image you can test with. As for Golang, you could extend the image with your own Dockerfile and have docker-compose build it.

I have already done this, but not with my own images (as far as json is concerned). Instead, I simply mounted the json manually in the container, which also worked (:.

I successfully installed golang using my own images.

certbot-dns-multi runs without any problems for me in version 4.27.0.

[sopex]

IMO. This last bunch of commits is much better interface-wise!

[lastsamurai26]

colours now much better (:
but i guess there a missing a phrase ?

redirect and redirect ?
i guess this should be Labeled like redirect URL and redirect HTML ?

[sopex]

Also when you rename an access list, you get an error even though it gets renamed successfully.

[lastsamurai26]

colours now much better (: but i guess there a missing a phrase ?

redirect and redirect ? i guess this should be Labeled like redirect URL and redirect HTML ?

:'( seams the phrase issue is persistent

Are you considering integrating http3, or has this been implemented for version 3?

i got issue in the logs
nginx: [warn] could not build optimal proxy_headers_hash, you should increase either proxy_headers_hash_max_size: 512 or proxy_headers_hash_bucket_size: 64; ignoring proxy_headers_hash_bucket_size
but it is not related to this case ;-) just as info

[jc21]

@lastsamurai26 I'm not seeing the same thing as you, using the latest docker image built. Might be cached in the browser?

[lastsamurai26]

I use this

FROM nginxproxymanager/nginx-proxy-manager-dev:pr-4785
RUN apt-get update \
	&& apt-get install -y --no-install-recommends wget curl python3-dev \
	&& apt-get clean \
	&& rm -rf /var/lib/apt/lists/*
RUN wget https://go.dev/dl/go1.24.5.linux-arm64.tar.gz
RUN tar -xzf go1.24.5.linux-arm64.tar.gz -C /usr/local && rm -f go1.24.5.linux-arm64.tar.gz
ENV PATH="/usr/local/go/bin:${PATH}"

this is my compose

---
services:
  app:
    build:
      context: .
      dockerfile: Dockerfile
    restart: unless-stopped
    hostname: proxymanager
    healthcheck:
      test: ["CMD", "/bin/check-health"]
      interval: 10s
      timeout: 3s
    ports:
      - '80:80' 
      - '443:443/tcp' 
    environment:
      DISABLE_IPV6: 'false'
    networks:
        proxy:
          ipv4_address: 172.18.1.254
    volumes:
      - /opt/containers/nginxproxy/data:/data
#      - /opt/containers/nginxproxy/themes/98-themepark:/etc/cont-init.d/98-themepark
      - /opt/containers/nginxproxy/letsencrypt:/etc/letsencrypt
      - /opt/containers/nginxproxy/templates/_hsts.conf:/app/templates/_hsts.conf:ro
      - /opt/containers/nginxproxy/templates/_location.conf:/app/templates/_location.conf:ro
      - /opt/containers/nginxproxy/custom_rotate/logrotate.nginx:/etc/logrotate.d/nginx-proxy-manager
      - /opt/containers/nginxproxy/certbot-dns-plugins.json:/app/global/certbot-dns-plugins.json
      - /etc/timezone:/etc/timezone:ro
      - /usr/share/zoneinfo:/usr/share/zoneinfo:ro
networks:
  proxy:
    external: true

it is the same :-(. in the settings i see redirect and redirect
Unfortunately, I have already tried three different browsers: Opera, Chrome, and Edge, each time in private window mode.

[artenais]

If I can ask an improvement it would be nice if domains levels are like folder-grouped, so if you host multiple domains the management will be easier.

[sopex]

@lastsamurai26 I also believe it's fixed.

[nginxproxymanagerci]

Docker Image for build 21 is available on DockerHub:

nginxproxymanager/nginx-proxy-manager-dev:pr-4785

Note

Ensure you backup your NPM instance before testing this image! Especially if there are database changes.
This is a different docker image namespace than the official image.

Warning

Changes and additions to DNS Providers require verification by at least 2 members of the community!