starred/nginx-proxy-manager-NginxProxyManager

Fork 0

mirror of https://github.com/NginxProxyManager/nginx-proxy-manager.git synced 2026-04-25 01:15:51 +03:00

[GH-ISSUE #1295] Feature Request: Servercow.de #1040

New issue

Open

opened 2026-02-26 06:35:31 +03:00 by kerem · 6 comments

kerem commented

2026-02-26 06:35:31 +03:00

Owner

Originally created by @dschense on GitHub (Aug 7, 2021).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1295

What provider would you like to see added to NPM?

Have you checked if a certbot plugin exists?
would be cool if this could be integrated:
https://github.com/jhartlep/servercow-dns-api

Originally created by @dschense on GitHub (Aug 7, 2021). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1295 **What provider would you like to see added to NPM?**  **Have you checked if a certbot plugin exists?** would be cool if this could be integrated: https://github.com/jhartlep/servercow-dns-api

kerem added the

stale

dns provider request

no certbot plugin available

labels

2026-02-26 06:35:31 +03:00

kerem commented

2026-02-26 06:35:32 +03:00

Author

Owner

@chaptergy commented on GitHub (Aug 8, 2021):

Unfortunately the DNS challenge within nginx proxy manager is only available for certbot dns plugins. Servercow does not have a plugin for this. Using the acme.sh script is a very significant deviation from certbot and would require a just as significant amount of work. It also would require support for two separate DNS challenge mechanisms instead of just one. So I don't think it is very likely to be implemented for now, unless a certbot plugin is published.

The v3 rewrite of NPM will use acme.sh instead of certbot, but it is still fairly far away.

@chaptergy commented on GitHub (Aug 8, 2021): Unfortunately the DNS challenge within nginx proxy manager is only available for [certbot dns plugins](https://certbot.eff.org/docs/using.html#dns-plugins). Servercow does not have a plugin for this. Using the acme.sh script is a very significant deviation from certbot and would require a just as significant amount of work. It also would require support for two separate DNS challenge mechanisms instead of just one. So I don't think it is very likely to be implemented for now, unless a certbot plugin is published. The v3 rewrite of NPM will use acme.sh instead of certbot, but it is still fairly far away.

kerem commented

2026-02-26 06:35:32 +03:00

Author

Owner

@KGBist2000 commented on GitHub (Jun 21, 2022):

Hey @chaptergy,
could you confirm to integrate the acme.sh support for the V3.0 ?

i have also the same issue with servercow. Addtional benefit of acmee.sh is, that by using other targets like synolgy the acme deploy-hook can be parallel used on side to the proxy-manager.

@KGBist2000 commented on GitHub (Jun 21, 2022): Hey @chaptergy, could you confirm to integrate the acme.sh support for the V3.0 ? i have also the same issue with servercow. Addtional benefit of acmee.sh is, that by using other targets like synolgy the acme deploy-hook can be parallel used on side to the proxy-manager.

kerem commented

2026-02-26 06:35:32 +03:00

Author

Owner

@dschense commented on GitHub (Jun 8, 2023):

I had opened this feature request some time ago.
It's a pity that so far no possibility has been added to use servercow with the npm.

Maybe you can try again to include servercow.
There is an official acme.sh script for the provider Servercow:

https://github.com/acmesh-official/acme.sh/blob/master/dnsapi/dns_servercow.sh

@dschense commented on GitHub (Jun 8, 2023): I had opened this feature request some time ago. It's a pity that so far no possibility has been added to use servercow with the npm. Maybe you can try again to include servercow. There is an official acme.sh script for the provider Servercow: https://github.com/acmesh-official/acme.sh/blob/master/dnsapi/dns_servercow.sh

kerem commented

2026-02-26 06:35:32 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Mar 7, 2024):

Issue is now considered stale. If you want to keep it open, please comment 👍

@github-actions[bot] commented on GitHub (Mar 7, 2024): Issue is now considered stale. If you want to keep it open, please comment :+1:

kerem commented

2026-02-26 06:35:32 +03:00

Author

Owner

@phil-bot commented on GitHub (Jan 25, 2025):

Hello folks,

is there anything new to report on this matter?

@phil-bot commented on GitHub (Jan 25, 2025): Hello folks, is there anything new to report on this matter?

kerem commented

2026-02-26 06:35:32 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Aug 20, 2025):

Issue is now considered stale. If you want to keep it open, please comment 👍

@github-actions[bot] commented on GitHub (Aug 20, 2025): Issue is now considered stale. If you want to keep it open, please comment :+1:

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/nginx-proxy-manager-NginxProxyManager#1040

No description provided.

Rows
Columns