Adds Hetzner Cloud to available plugins

[potatojuicemachine]

This MR adds Hetzner Cloud as a certbot dns provider because hetzner is moving from dns console to cloud.
Closes #4802

[potatojuicemachine]

I fail to understand why my PR can't be built. Can anyone help me with this?
Additionally I am unable to get the dev environment up and running as the scripts always fail with an error message related do postgres and unrelated (afaik) to my changes.
It as been multiple hours of failing and any help would be appreciated.

[renanmedina]

@potatojuicemachine I also got the postgres error, its because the setup is using :latest tag of postgres which is always not advisable. (seems the latest tag does some new checks and dont get the container up and running)

I fixed that by just commenting out the connection in the docker-compose.dev file to use the sqlite version.

that way it ignores the postgres container and let you work normally.

I'm not sure how the ci in jenkins is implemented currently, but if it's also using postgres in there, it should be the reason why its failing for everyone (it failed to me in my PR)

[potatojuicemachine]

@renanmedina I think it could be this issue. At least I had the same with postgres in a different context https://forums.docker.com/t/mysterious-docker-issue-with-postgres/149898/3

[potatojuicemachine]

I tested the built container and I was able to get a certificate from hetzner cloud.

[sopex]

Maybe PR it against the react branch, since 2.13 is based on that, and it's close to going live.

[potatojuicemachine]

@sopex I am not sure what the correct way to contribute is :) I changed the base

[sopex]

@jc21 Can we test this in 2.13? Thank you a lot!

[nginxproxymanagerci]

Docker Image for build 5 is available on DockerHub:

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

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!