jc21
jc21
> @jc21 develop branch dont have your commit,Is it flushed by other commit? I'm not sure what "commit" you're talking about? This PR is not mine and is not merged...
For some reason, CI doesn't want to build this PR. Perhaps rebasing it in your fork might help?
The build failed CI due to recent major postgres releases. If you want to rebase now, hopefully it should pass.
In case you missed it, the plugins json file has moved [here](https://github.com/NginxProxyManager/nginx-proxy-manager/blob/develop/backend/certbot/dns-plugins.json).
Can you confirm this build is working as expected? Can we also find another person to confirm this build is working?
This is a beautiful example of a well written PR comment :) Thanks for looking into this - NPM was originally written with the concept that it would be the...
See [this file](https://github.com/NginxProxyManager/nginx-proxy-manager/blob/develop/backend/templates/proxy_host.conf#L34) which has the default location `/`. That then includes [this file](https://github.com/NginxProxyManager/nginx-proxy-manager/blob/develop/docker/rootfs/etc/nginx/conf.d/include/proxy.conf#L4) which sets the header on that level. In order to override this, you'll have to define...
I'm not adding Go in the image just for this. Certbot is the current mechanism for DNS providers, and there isn't a PyPi certbot plugin for iv64 specifically.
Thanks. I just added a new translation for `redirection-host.forward-http-code`, can you add that in? I guess it can be a copy of the value for `column.http-code`
> column.http-code translates to "Access" Yeah I fixed that one on the develop branch yesterday.