[GH-ISSUE #2290] Problem in setting up minio to work through a nginx-proxy-manager #1628

New issue

Closed

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

kerem commented 2026-02-26 07:31:49 +03:00

Owner

Copy link

Originally created by @Adigezalov on GitHub (Sep 25, 2022).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2290

Hi.
I need help installing minio through a nginx-proxy-manager.
I'm not a professional devops so this question makes me panic.
I installed nginx-proxy-manager and minio in docker containers.
Set up all the necessary urls.
Now I have url console.DOMAIN.com that enters the console, and url minio.DOMAIN.com can connect to api minio to send files.
Through the console everything works fine.
But the problem is that when sending a file from the frontend, minio gives me the following error: MinIO API responded with message=The request signature we calculated does not match the signature you provided. Check your key and signing method.
I understand that this means that somewhere my nginx-proxy has lost some headers.
But I don’t understand which ones and how to install them exactly in the nginx-proxy-manager.

Originally created by @Adigezalov on GitHub (Sep 25, 2022). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2290 Hi. I need help installing minio through a nginx-proxy-manager. I'm not a professional devops so this question makes me panic. I installed nginx-proxy-manager and minio in docker containers. Set up all the necessary urls. Now I have url console.DOMAIN.com that enters the console, and url minio.DOMAIN.com can connect to api minio to send files. Through the console everything works fine. But the problem is that when sending a file from the frontend, minio gives me the following error: MinIO API responded with message=The request signature we calculated does not match the signature you provided. Check your key and signing method. I understand that this means that somewhere my nginx-proxy has lost some headers. But I don’t understand which ones and how to install them exactly in the nginx-proxy-manager.

kerem 2026-02-26 07:31:49 +03:00

• closed this issue
• added the
  stale
  label

kerem commented 2026-02-26 07:31:50 +03:00

Author

Owner

Copy link

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

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

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

kerem commented 2026-02-26 07:31:50 +03:00

Author

Owner

Copy link

@wudingjian commented on GitHub (Mar 19, 2024):

如果你需要部署对象存储的网站是https，需要在Nginx Proxy Manager 中进行反代，并在路由器进行端口映射。例如：端口映射到99，那你的endpoint就变成了https://域名:99

# Allow special characters in headers
   ignore_invalid_headers off;
   # Allow any size file to be uploaded.
   # Set to a value such as 1000m; to restrict file size to a specific value
   client_max_body_size 0;
   # Disable buffering
   proxy_buffering off;
   proxy_request_buffering off;

   location / {
      proxy_set_header Host $http_host;
      proxy_set_header X-Real-IP $remote_addr;
      proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
      proxy_set_header X-Forwarded-Proto $scheme;

      proxy_connect_timeout 300;
      # Default is HTTP/1, keepalive is only enabled in HTTP/1.1
      proxy_http_version 1.1;
      proxy_set_header Connection "";
      chunked_transfer_encoding off;

      proxy_pass http://minio:9000;
      }

---

详解两个坑的解决方案

---

1、Nginx Proxy Manager 无法反向代理

官网Issues上这类问题很多:https://github.com/NginxProxyManager/nginx-proxy-manager/issues?q=minio

具体解方法：详见官方文档：https://www.minio.org.cn/docs/minio/linux/integrations/setup-nginx-proxy-with-minio.html

（1）api服务端反向代理配置如下：

注意：
Scheme* 要改成 https (如果没有放置TLS证书请用http)
Forward Hostname / IP* minio 是容器的名称
Forward Port * 99 是容器的内部端口，注意区分，不是映射到主机的端口9080

# Allow special characters in headers
   ignore_invalid_headers off;
   # Allow any size file to be uploaded.
   # Set to a value such as 1000m; to restrict file size to a specific value
   client_max_body_size 0;
   # Disable buffering
   proxy_buffering off;
   proxy_request_buffering off;

   location / {
      proxy_set_header Host $http_host;
      proxy_set_header X-Real-IP $remote_addr;
      proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
      proxy_set_header X-Forwarded-Proto $scheme;

      proxy_connect_timeout 300;
      # Default is HTTP/1, keepalive is only enabled in HTTP/1.1
      proxy_http_version 1.1;
      proxy_set_header Connection "";
      chunked_transfer_encoding off;

      proxy_pass https://minio:99;
      }

注意：
https://minio:99 # 要改成 https (如果没有放置TLS证书请用http)，99 是容器内部端口

管理端服务端反向代理配置如下：

注意：
Scheme* 要改成 https 如果没有放置TLS证书请用http
Forward Hostname / IP* minio 是容器的名称
Forward Port * 9090 是容器的内部端口

复制下列代码：

location / {
      proxy_set_header Host $http_host;
      proxy_set_header X-Real-IP $remote_addr;
      proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
      proxy_set_header X-Forwarded-Proto $scheme;
      proxy_set_header X-NginX-Proxy true;

      # This is necessary to pass the correct IP to be hashed
      real_ip_header X-Real-IP;

      proxy_connect_timeout 300;

      # To support websockets in MinIO versions released after January 2023
      proxy_http_version 1.1;
      proxy_set_header Upgrade $http_upgrade;
      proxy_set_header Connection "upgrade";
      # Some environments may encounter CORS errors (Kubernetes + Nginx Ingress)
      # Uncomment the following line to set the Origin request to an empty string
      # proxy_set_header Origin '';

      chunked_transfer_encoding off;

      proxy_pass https://minio:9090;
}

注意：
https://minio:9090 # 要改成 https （如果没有放置TLS证书请用http），9090 是容器内部端口

如果不加这段代码，会出现如下情况(坑点，原因不明)

会一直打圈，不能显示列表

2、共享文件外部域分享，显示为内部域ip(127.0.0.1:端口) （大坑）

经阅读官方文档：https://www.minio.org.cn/docs/minio/linux/integrations/setup-nginx-proxy-with-minio.html

对于个人的私有化布署，不太友好，官方文档也没说清楚

（1）需要设置两个变量：

您还必须为MinIO部署设置以下环境变量：

将 MINIO_SERVER_URL 设置为MinIO服务器的代理主机FQDN（ https://minio.example.net ）

将 MINIO_BROWSER_REDIRECT_URL 设置为代理主机的 FQDN (https://example.net/minio/ui)

（2）修改 docker-compose.yml内容如下：

version: "3.7"
services:
  minio:
    image: minio/minio
    container_name: minio
    command: server --address ":9000"  --console-address ":9090"   /data  # 指定服务端口和管理端口
    ports:
      - 9080:9000 # :前面的自行定义，服务端口：API: http://IP:9080
      - 9090:9090 # :前面的自行定义，管理端口：http://IP:9090
    volumes:
      - ./data:/data  # 数据目录
      - ./config:/root/.minio   #  TLS 密钥和证书存放在  ./config/certs
    environment:
      - MINIO_ROOT_USER=admin  # 用户名，自行修改
      - MINIO_ROOT_PASSWORD=password  # 密码，自行修改
      - MINIO_SERVER_URL=https://api.example.com:99 # 自行修改成自已的域名# 反向代理的服务域名，用于文件分享外部url,":99" 是反向代理后公网访问端口
      - MINIO_BROWSER_REDIRECT_URL=https://s3.example.com:99 # 自行修改成自已的域名#  反向代理的登录域名,":99" 是反向代理后公网访问端口
    restart: unless-stopped  # 总是重启容器

（3）运行容器：

docker-compose up -d

（4）无法登录管理页面

（5）找原因

官网Issues上这类问题很多

大多数并没有给我带来帮助：https://github.com/minio/minio/issues?q=MINIO_ROOT_USER

有一篇提问提到这个问题：

minio启动后，会主动验证~ MINIO_SERVER_URL=https://api.example.com:99 ~的可通性

面临两个问题：
A.反向代理后方，无证书
B.反向代理后方，内部如何域名解析到127.0.0.1

对于个人单机单点的私有化布署，不太友好，官方文档也没说清楚

最终还是在官方文档上找到了方法

先解决证书问题：

官方文档详见：https://www.minio.org.cn/docs/minio/linux/operations/network-encryption.html

使用 MinIO 的 certgen 工具来生成自签名的TLS证书的方法，详见：https://www.cnblogs.com/hahaha111122222/p/15984957.html

下载地址：https://github.com/minio/certgen/releases/tag/v0.0.2

下载certgen-windows-amd64.exe 放到任意文件夹，例如：.\desktop\1

certgen -ca -host "主机IP,minio容器运行IP,两个域名,hostname"
实际执行的生成证书的命令：

./certgen-windows-amd64.exe -ca -host "127.0.0.1,192.168.30.2,172.18.0.22,api.example.com,s3.example.com,minio"

显示：

2022/03/09 14:10:58 wrote public.crt
2022/03/09 14:10:58 wrote private.key
如图：

解释一下ip和域名：

127.0.0.1 主机环回地址
192.168.30.2 主机ip
172.18.0.22 容器内ip
api.example.com 服务域名
s3.example.com 管理域我
minio hostname

复制public.crt private.key 到 主机的./config 映射目录下

反向代理后面的域名解析到127.0.0.1

可以在docker-compose中增加dns记录解决

    extra_hosts:
        api.example.com : 127.0.0.1 # 自行修改服务域名
        s3.example.com : 127.0.0.1 # 自行修改服务域名

解决容器内部无法访问到99端口的问题

家庭网络环境中，路由器会转发端口
例如：
A路由器外部公网端口：99 #运营商限制不能使用80 没办法只能用99代替
B反向代理端口：80/443
C主机端口：9080 # 详见docker-compose 的配置
D容器内部端口：9000

访问的传递是 A->B->C->D

在容器内部，无法使用99端口

这就需要将容器服务端口与外部端口统一使用 “:99”

综上修改后的docker-compos.yml如下：

version: "3.7"
services:
  minio:
    image: minio/minio
    container_name: minio
    command: server --address ":99"  --console-address ":9090"   /data  # 指定服务端口和管理端口
    ports:
      - 9080:99 # :前面的自行定义，服务端口：API: http://IP:9080
      - 9090:9090 # :前面的自行定义，管理端口：http://IP:9090
    extra_hosts:
        api.example.com : 127.0.0.1 # 自行修改服务域名
        s3.example.com : 127.0.0.1 # 自行修改服务域名      
    volumes:
      - ./data:/data  # 数据目录
      - ./config:/root/.minio   #  TLS 密钥和证书存放在  ./config/certs
    environment:
      - MINIO_ROOT_USER=admin  # 用户名，自行修改
      - MINIO_ROOT_PASSWORD=password  # 密码，自行修改
      - MINIO_SERVER_URL=https://api.example.com:99 # 自行修改成自已的域名# 反向代理的服务域名，用于文件分享外部url,":99" 是反向代理后公网访问端口
      - MINIO_BROWSER_REDIRECT_URL=https://s3.example.com:99 # 自行修改成自已的域名#  反向代理的登录域名,":99" 是反向代理后公网访问端口
      - MINIO_STS_DURATION=168h # 文件分享外部url 最大时长 7天，超过7天无效，永久分享的方法：Buckets（存储块）Access Policy设为 public，链接文件名后面“？及以后的代码”删除。比较危险，通过Buckets路径，可以看到所有文件的目录。
    restart: unless-stopped  # 总是重启容器

运行容器：

docker-compose up -d

完美解决

------------完毕------------

<!-- gh-comment-id:2007546092 --> @wudingjian commented on GitHub (Mar 19, 2024): 如果你需要部署对象存储的网站是https，需要在Nginx Proxy Manager 中进行反代，并在路由器进行端口映射。例如：端口映射到99，那你的endpoint就变成了https://域名:99    ``` nginx # Allow special characters in headers ignore_invalid_headers off; # Allow any size file to be uploaded. # Set to a value such as 1000m; to restrict file size to a specific value client_max_body_size 0; # Disable buffering proxy_buffering off; proxy_request_buffering off; location / { proxy_set_header Host $http_host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; proxy_connect_timeout 300; # Default is HTTP/1, keepalive is only enabled in HTTP/1.1 proxy_http_version 1.1; proxy_set_header Connection ""; chunked_transfer_encoding off; proxy_pass http://minio:9000; } ``` ------------ > > > > # **详解两个坑的解决方案** > > > ------------ ## 1、Nginx Proxy Manager 无法反向代理 官网Issues上这类问题很多:https://github.com/NginxProxyManager/nginx-proxy-manager/issues?q=minio  具体解方法：详见官方文档：https://www.minio.org.cn/docs/minio/linux/integrations/setup-nginx-proxy-with-minio.html  ### （1）api服务端反向代理配置如下：  > 注意： > Scheme* **要改成 https** (如果没有放置TLS证书请用http) > Forward Hostname / IP* **minio 是容器的名称** > Forward Port * 99 **是容器的内部端口，注意区分，不是映射到主机的端口9080**   ``` nginx # Allow special characters in headers ignore_invalid_headers off; # Allow any size file to be uploaded. # Set to a value such as 1000m; to restrict file size to a specific value client_max_body_size 0; # Disable buffering proxy_buffering off; proxy_request_buffering off; location / { proxy_set_header Host $http_host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; proxy_connect_timeout 300; # Default is HTTP/1, keepalive is only enabled in HTTP/1.1 proxy_http_version 1.1; proxy_set_header Connection ""; chunked_transfer_encoding off; proxy_pass https://minio:99; } ``` > 注意： > https://minio:99 **# 要改成 https (如果没有放置TLS证书请用http)，99 是容器内部端口** ### 管理端服务端反向代理配置如下：  > 注意： > Scheme* **要改成 https** 如果没有放置TLS证书请用http > Forward Hostname / IP* **minio 是容器的名称** > Forward Port * 9090 **是容器的内部端口**   复制下列代码： ``` nginx location / { proxy_set_header Host $http_host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; proxy_set_header X-NginX-Proxy true; # This is necessary to pass the correct IP to be hashed real_ip_header X-Real-IP; proxy_connect_timeout 300; # To support websockets in MinIO versions released after January 2023 proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; # Some environments may encounter CORS errors (Kubernetes + Nginx Ingress) # Uncomment the following line to set the Origin request to an empty string # proxy_set_header Origin ''; chunked_transfer_encoding off; proxy_pass https://minio:9090; } ``` > 注意： > https://minio:9090 **# 要改成 https （如果没有放置TLS证书请用http），9090 是容器内部端口** > **如果不加这段代码，会出现如下情况(坑点，原因不明)**  > **会一直打圈，不能显示列表** ## 2、共享文件外部域分享，显示为内部域ip(127.0.0.1:端口) **（大坑）**  经阅读官方文档：https://www.minio.org.cn/docs/minio/linux/integrations/setup-nginx-proxy-with-minio.html > 对于个人的私有化布署，不太友好，官方文档也没说清楚 ### （1）需要设置两个变量： 您还必须为MinIO部署设置以下环境变量： ~~~ 将 MINIO_SERVER_URL 设置为MinIO服务器的代理主机FQDN（ https://minio.example.net ） 将 MINIO_BROWSER_REDIRECT_URL 设置为代理主机的 FQDN (https://example.net/minio/ui) ~~~ ### （2）修改 docker-compose.yml内容如下： ``` docker version: "3.7" services: minio: image: minio/minio container_name: minio command: server --address ":9000" --console-address ":9090" /data # 指定服务端口和管理端口 ports: - 9080:9000 # :前面的自行定义，服务端口：API: http://IP:9080 - 9090:9090 # :前面的自行定义，管理端口：http://IP:9090 volumes: - ./data:/data # 数据目录 - ./config:/root/.minio # TLS 密钥和证书存放在 ./config/certs environment: - MINIO_ROOT_USER=admin # 用户名，自行修改 - MINIO_ROOT_PASSWORD=password # 密码，自行修改 - MINIO_SERVER_URL=https://api.example.com:99 # 自行修改成自已的域名# 反向代理的服务域名，用于文件分享外部url,":99" 是反向代理后公网访问端口 - MINIO_BROWSER_REDIRECT_URL=https://s3.example.com:99 # 自行修改成自已的域名# 反向代理的登录域名,":99" 是反向代理后公网访问端口 restart: unless-stopped # 总是重启容器 ``` ### （3）运行容器： ``` docker docker-compose up -d ``` ### （4）无法登录管理页面  ### （5）找原因 #### 官网Issues上这类问题很多  大多数并没有给我带来帮助：https://github.com/minio/minio/issues?q=MINIO_ROOT_USER 有一篇提问提到这个问题： minio启动后，会主动验证~ MINIO_SERVER_URL=https://api.example.com:99 ~的可通性 面临两个问题： A.反向代理后方，无证书 B.反向代理后方，内部如何域名解析到127.0.0.1 > 对于个人单机单点的私有化布署，不太友好，官方文档也没说清楚 #### 最终还是在官方文档上找到了方法 ##### 先解决证书问题： 官方文档详见：https://www.minio.org.cn/docs/minio/linux/operations/network-encryption.html   使用 MinIO 的 certgen 工具来生成自签名的TLS证书的方法，详见：https://www.cnblogs.com/hahaha111122222/p/15984957.html 下载地址：https://github.com/minio/certgen/releases/tag/v0.0.2  下载certgen-windows-amd64.exe 放到任意文件夹，例如：.\desktop\1  > certgen -ca -host "主机IP,minio容器运行IP,两个域名,hostname" > 实际执行的生成证书的命令： ~~~ docker ./certgen-windows-amd64.exe -ca -host "127.0.0.1,192.168.30.2,172.18.0.22,api.example.com,s3.example.com,minio" ~~~ > 显示： 2022/03/09 14:10:58 wrote public.crt 2022/03/09 14:10:58 wrote private.key 如图：  解释一下ip和域名： 127.0.0.1 主机环回地址 192.168.30.2 主机ip 172.18.0.22 容器内ip api.example.com 服务域名 s3.example.com 管理域我 minio hostname 复制public.crt private.key 到 主机的./config 映射目录下  #### 反向代理后面的域名解析到127.0.0.1 可以在docker-compose中增加dns记录解决 ~~~ docker extra_hosts: api.example.com : 127.0.0.1 # 自行修改服务域名 s3.example.com : 127.0.0.1 # 自行修改服务域名 ~~~ #### 解决容器内部无法访问到99端口的问题 家庭网络环境中，路由器会转发端口 例如： A路由器外部公网端口：99 #运营商限制不能使用80 没办法只能用99代替 B反向代理端口：80/443 C主机端口：9080 # 详见docker-compose 的配置 D容器内部端口：9000 访问的传递是 A->B->C->D 在容器内部，无法使用99端口 这就需要将容器服务端口与外部端口统一使用 “:99” #### 综上修改后的docker-compos.yml如下： ``` docker version: "3.7" services: minio: image: minio/minio container_name: minio command: server --address ":99" --console-address ":9090" /data # 指定服务端口和管理端口 ports: - 9080:99 # :前面的自行定义，服务端口：API: http://IP:9080 - 9090:9090 # :前面的自行定义，管理端口：http://IP:9090 extra_hosts: api.example.com : 127.0.0.1 # 自行修改服务域名 s3.example.com : 127.0.0.1 # 自行修改服务域名 volumes: - ./data:/data # 数据目录 - ./config:/root/.minio # TLS 密钥和证书存放在 ./config/certs environment: - MINIO_ROOT_USER=admin # 用户名，自行修改 - MINIO_ROOT_PASSWORD=password # 密码，自行修改 - MINIO_SERVER_URL=https://api.example.com:99 # 自行修改成自已的域名# 反向代理的服务域名，用于文件分享外部url,":99" 是反向代理后公网访问端口 - MINIO_BROWSER_REDIRECT_URL=https://s3.example.com:99 # 自行修改成自已的域名# 反向代理的登录域名,":99" 是反向代理后公网访问端口 - MINIO_STS_DURATION=168h # 文件分享外部url 最大时长 7天，超过7天无效，永久分享的方法：Buckets（存储块）Access Policy设为 public，链接文件名后面“？及以后的代码”删除。比较危险，通过Buckets路径，可以看到所有文件的目录。 restart: unless-stopped # 总是重启容器 ``` ###### 运行容器： ``` docker docker-compose up -d ``` # 完美解决  ------------完毕------------

kerem commented 2026-02-26 07:31:50 +03:00

Author

Owner

Copy link

@github-actions[bot] commented on GitHub (Nov 21, 2024):

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

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

kerem commented 2026-02-26 07:31:50 +03:00

Author

Owner

Copy link

@github-actions[bot] commented on GitHub (Dec 3, 2025):

Issue was closed due to inactivity.

<!-- gh-comment-id:3604737128 --> @github-actions[bot] commented on GitHub (Dec 3, 2025): Issue was closed due to inactivity.

Sign in to join this conversation.

No Branch/Tag specified

Branches Tags

develop

dependabot/npm_and_yarn/backend/liquidjs-10.25.7

dependabot/npm_and_yarn/frontend/prod-minor-updates-2a16bf3987

dependabot/npm_and_yarn/frontend/dev-patch-updates-754666cf41

dependabot/npm_and_yarn/backend/basic-ftp-5.3.0

dependabot/npm_and_yarn/test/follow-redirects-1.16.0

dependabot/npm_and_yarn/test/axios-1.15.0

dependabot/npm_and_yarn/frontend/lodash-4.18.1

dependabot/npm_and_yarn/backend/lodash-4.18.1

dependabot/npm_and_yarn/test/lodash-4.18.1

dependabot/npm_and_yarn/frontend/vite-7.3.2

dependabot/npm_and_yarn/backend/prod-minor-updates-5ec19a7f21

dependabot/npm_and_yarn/frontend/lodash-es-4.18.1

dependabot/npm_and_yarn/frontend/happy-dom-20.8.9

dependabot/npm_and_yarn/backend/path-to-regexp-8.4.0

dependabot/npm_and_yarn/frontend/picomatch-4.0.4

dependabot/npm_and_yarn/backend/picomatch-2.3.2

dependabot/npm_and_yarn/frontend/yaml-1.10.3

dependabot/npm_and_yarn/test/flatted-3.4.2

dependabot/npm_and_yarn/test/tar-7.5.11

dependabot/npm_and_yarn/frontend/immutable-5.1.5

master

dependabot/npm_and_yarn/test/glob-10.5.0

dependabot/npm_and_yarn/frontend/mdast-util-to-hast-13.2.1

dependabot/npm_and_yarn/test/form-data-4.0.4

v3-abandoned

bump-freedns

openidc

ssl-passthrough-hosts

static-content

v2.14.0

v2.13.7

v2.13.6

v2.13.5

v2.13.4

v2.13.3

v2.13.2

v2.13.1

v2.13.0

v2.12.6

v2.12.5

v2.12.4

v2.12.3

v2.12.2

v2.12.1

v2.12.0

v2.11.3

v2.11.2

v2.11.1

v2.11.0

v2.10.4

v2.10.3

v2.10.2

v2.10.1

v2.10.0

v2.9.22

v2.9.21

v2.9.20

v2.9.19

v2.9.18

v2.9.17

v2.9.16

v2.9.15

v2.9.14

v2.9.13

v2.9.12

v2.9.11

v2.9.10

v2.9.9

v2.9.8

v2.9.7

v2.9.6

v2.9.5

v2.9.4

v2.9.3

v2.9.2

v2.9.1

v2.9.0

v2.8.1

v2.8.0

v2.7.3

v2.7.2

v2.7.1

v2.7.0

v2.6.2

v2.6.1

v2.6.0

v2.5.0

v2.4.0

v2.3.1

v2.3.0

v2.2.4

v2.2.3

v2.2.2

v2.2.1

v2.2.0

v2.1.2

v2.1.1

v2.1.0

2.0.14

2.0.13

2.0.12

2.0.11

2.0.10

2.0.9

2.0.8

2.0.7

2.0.6

2.0.5

2.0.4

2.0.3

2.0.2

2.0.0

v2.0.0

1.1.2

1.1.1

1.0.1

Labels

Clear labels   

awaiting feedback

  

bug

  

cannot reproduce

  

dns provider request

  

duplicate

  

enhancement

  

enhancement

  

enhancement

  

good first issue

  

help wanted

  

invalid

  

need more info

  

no certbot plugin available

  

product-support

  

pull-request

Mirrored from GitHub Pull Request

  

question

  

stale

  

troll

  

upstream issue

  

v2

  

v2

  

v2

  

v3

  

wontfix

No labels

awaiting feedback

bug

cannot reproduce

dns provider request

duplicate

enhancement

enhancement

enhancement

good first issue

help wanted

invalid

need more info

no certbot plugin available

product-support

pull-request

question

stale

troll

upstream issue

v2

v2

v2

v3

wontfix

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

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#1628

No description provided.