[GH-ISSUE #2066] SSL file .pri and .crt #1493

Closed
opened 2026-02-26 07:31:17 +03:00 by kerem · 4 comments
Owner

Originally created by @leonardooleg on GitHub (May 23, 2022).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2066

I have installed vDDoS Proxy Protection and I need .pri and .crt SSL files for it
Do they already exist somewhere, or do need to create them from another npm file?

Originally created by @leonardooleg on GitHub (May 23, 2022). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2066 I have installed vDDoS Proxy Protection and I need .pri and .crt SSL files for it Do they already exist somewhere, or do need to create them from another npm file?
kerem 2026-02-26 07:31:17 +03:00
  • closed this issue
  • added the
    stale
    label
Author
Owner

@leonardooleg commented on GitHub (May 24, 2022):

I found a solution.
Go to the SSL Certificates tab - download the archive for your domain.
Then just rename the desired files.

<!-- gh-comment-id:1135773181 --> @leonardooleg commented on GitHub (May 24, 2022): I found a solution. Go to the SSL Certificates tab - download the archive for your domain. Then just rename the desired files.
Author
Owner

@the1ts commented on GitHub (May 24, 2022):

Not ideal, but you probably have the certs on the docker host disk for NPM do that also for vDDOS, link the 2 locations (letsencrypt/live/npm-$number/), then I have a script in letsencrypt/renewal-hooks/deploy/ which restarts the second container after NPM updates the certs then the second container picks up the new certs and all is well.

<!-- gh-comment-id:1136057762 --> @the1ts commented on GitHub (May 24, 2022): Not ideal, but you probably have the certs on the docker host disk for NPM do that also for vDDOS, link the 2 locations (letsencrypt/live/npm-$number/), then I have a script in letsencrypt/renewal-hooks/deploy/ which restarts the second container after NPM updates the certs then the second container picks up the new certs and all is well.
Author
Owner

@github-actions[bot] commented on GitHub (Feb 16, 2024):

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

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

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

Issue was closed due to inactivity.

<!-- gh-comment-id:2767876877 --> @github-actions[bot] commented on GitHub (Apr 1, 2025): Issue was closed due to inactivity.
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#1493
No description provided.