[GH-ISSUE #1054] Integration with internal ACME server #882

Open
opened 2026-02-26 06:34:47 +03:00 by kerem · 11 comments
Owner

Originally created by @ghost on GitHub (Apr 30, 2021).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1054

Hi team, first of all I want you to know that I like this project, and I use NPM as my proxy for internal SWARM Cluster.

However I need to know if it's possible to have NPM to automatic request certificates from an internal ACME server. I user the LABCA (https://github.com/hakwerk/labca) as my internal certificate authority. This system works similar Let's Encrypt.

Do you have a way to integrate NPM to this project.

Thanks.

Originally created by @ghost on GitHub (Apr 30, 2021). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1054 Hi team, first of all I want you to know that I like this project, and I use NPM as my proxy for internal SWARM Cluster. However I need to know if it's possible to have NPM to automatic request certificates from an internal ACME server. I user the LABCA (https://github.com/hakwerk/labca) as my internal certificate authority. This system works similar Let's Encrypt. Do you have a way to integrate NPM to this project. Thanks.
Author
Owner

@psharma04 commented on GitHub (May 3, 2021):

This would be great for using services like ZeroSSL and BuypassCA, both of which are free public ACME CAs.

<!-- gh-comment-id:830994875 --> @psharma04 commented on GitHub (May 3, 2021): This would be great for using services like ZeroSSL and BuypassCA, both of which are free public ACME CAs.
Author
Owner

@jc21 commented on GitHub (Jun 29, 2021):

Just stumbled across this again. I am planning to add configurable CA's to v3.

I was looking at step-ca myself.

<!-- gh-comment-id:870213956 --> @jc21 commented on GitHub (Jun 29, 2021): Just stumbled across this again. I am planning to add configurable CA's to v3. I was looking at [step-ca](https://smallstep.com/blog/private-acme-server/) myself.
Author
Owner

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

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

<!-- gh-comment-id:1989768167 --> @github-actions[bot] commented on GitHub (Mar 12, 2024): Issue is now considered stale. If you want to keep it open, please comment :+1:
Author
Owner

@RamonAbudAlcala commented on GitHub (Sep 26, 2024):

This seems like a great idea! I'd love to see this implemented. Here are some related issues #2347 #1884 #1054 #301

<!-- gh-comment-id:2377254532 --> @RamonAbudAlcala commented on GitHub (Sep 26, 2024): This seems like a great idea! I'd love to see this implemented. Here are some related issues #2347 #1884 #1054 #301
Author
Owner

@kali-777 commented on GitHub (Oct 22, 2024):

Just stumbled across this again. I am planning to add configurable CA's to v3.

I was looking at step-ca myself.

Thanks sounds promising! 👍
I have PrimeKey EJBCA-CE in my HOME-Lab, EJBCA-CE Docker would be awesome to able to use it via ACME internally on NPM 😎

<!-- gh-comment-id:2429084828 --> @kali-777 commented on GitHub (Oct 22, 2024): > Just stumbled across this again. I am planning to add configurable CA's to v3. > > I was looking at [step-ca](https://smallstep.com/blog/private-acme-server/) myself. Thanks sounds promising! 👍 I have PrimeKey EJBCA-CE in my HOME-Lab, [EJBCA-CE Docker](https://hub.docker.com/r/keyfactor/ejbca-ce) would be awesome to able to use it via ACME internally on NPM 😎
Author
Owner

@github-actions[bot] commented on GitHub (Apr 24, 2025):

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

<!-- gh-comment-id:2825985827 --> @github-actions[bot] commented on GitHub (Apr 24, 2025): Issue is now considered stale. If you want to keep it open, please comment :+1:
Author
Owner

@RamonAbudAlcala commented on GitHub (Apr 25, 2025):

bump so that issue is not closed. :)

<!-- gh-comment-id:2830345105 --> @RamonAbudAlcala commented on GitHub (Apr 25, 2025): bump so that issue is not closed. :)
Author
Owner

@danieltr3s commented on GitHub (Aug 15, 2025):

bump!

<!-- gh-comment-id:3192944445 --> @danieltr3s commented on GitHub (Aug 15, 2025): bump!
Author
Owner

@BulldozerPete commented on GitHub (Nov 28, 2025):

bump

<!-- gh-comment-id:3590611636 --> @BulldozerPete commented on GitHub (Nov 28, 2025): bump
Author
Owner

@fbushman commented on GitHub (Jan 4, 2026):

Bump from 2026!
I've been running step-ca for a while now in the homelab, but manually configuring each service to use it is a pain. Would love to have this in the web interface!

<!-- gh-comment-id:3708234357 --> @fbushman commented on GitHub (Jan 4, 2026): Bump from 2026! I've been running step-ca for a while now in the homelab, but manually configuring each service to use it is a pain. Would love to have this in the web interface!
Author
Owner

@demonbane commented on GitHub (Jan 4, 2026):

While we wait for official upstream support I've been just editing /etc/letsencrypt.ini and adding in my custom server and it works fine. Just add:

server = <directory url>
eab-kid = <kid>
eab-hmac-key = <key>

to the bottom and try again. If you want to make it persistent over container updates, just save it in your persistent storage and add a bind mount to your compose file:

volumes:
  - ./data:/data
  - ./letsencrypt:/etc/letsencrypt
  - ./letsencrypt.ini:/etc/letsencrypt.ini:ro
<!-- gh-comment-id:3708243469 --> @demonbane commented on GitHub (Jan 4, 2026): While we wait for official upstream support I've been just editing `/etc/letsencrypt.ini` and adding in my custom server and it works fine. Just add: ```ini server = <directory url> eab-kid = <kid> eab-hmac-key = <key> ``` to the bottom and try again. If you want to make it persistent over container updates, just save it in your persistent storage and add a bind mount to your compose file: ```yaml volumes: - ./data:/data - ./letsencrypt:/etc/letsencrypt - ./letsencrypt.ini:/etc/letsencrypt.ini:ro ```
Sign in to join this conversation.
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#882
No description provided.