1Panel-dev / 1Panel-dev/1Panel

[Bug] Unable to Add Multiple IP Addresses When Issuing an IP Certificate

Open
#11,917 1 comment 0 reactions 1 assignee View on GitHub

@wanghe-fit2cloud is already working on this.

Since Feb 20, 2026.

type: feature-request
Dominant language
Go
Stars
37k
Forks
3.4k
Avg merge
9h 16m
Merged PRs (30d)
105

Description

1Panel Version

v2.1.0

Please describe your needs or suggestions for improvements

When applying for an IP-based TLS certificate in 1Panel, the system currently does not support issuing a single certificate that covers both IPv4 and IPv6 addresses at the same time.

If an IPv4 address is used, the certificate can be issued successfully.
If an IPv6 address is used, the certificate can also be issued successfully.

However, when attempting to include both IPv4 and IPv6 addresses in one certificate request, the UI only provides a single input field after selecting IP Certificate.

Image

This prevents issuing a single certificate for dual-stack servers (IPv4 + IPv6) and forces users to maintain multiple certificates for the same service.

Please describe the solution you suggest

After selecting IP Certificate, the interface should allow adding multiple IP addresses, such as:

  • one or more IPv4 addresses
  • one or more IPv6 addresses

These IPs should be included in the certificate as Subject Alternative Names (SAN).

Consider allowing:

  • multiple IP input fields, or
  • a dynamic “Add IP Address” option

so users can include all required IP addresses in one IP-based certificate request.

Additional Information

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.