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]

Should DNS multi be updated, or how can I do this myself?

[jc21]

What is problematic is the color palette of links and status messages when you are not on dark mode.

I'm actually mainly using light mode and only remembering to check the dark mode at the last minute

Should DNS multi be updated, or how can I do this myself?

Could you elaborate on what you mean by "DNS multi"?

[sopex]

I'm actually mainly using light mode and only remembering to check the dark mode at the last minute

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

[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.

[nginxproxymanagerci]

Docker Image for build 18 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!

[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.