Closed DevMude closed 4 months ago
Hi @DevMude,
Thanks for reporting this! I have created an internal task for our team to update the bncert tool. We will post any update here. I will add the on-hold tag as well.
@DevMude while we are working on our bncert-tool, I just wanted to clarify that Let's Encrypt officially supports IPv6, so in case you (or anyone else in our community) are in a hurry, you should be able to generate your own SSL certificates for IPv6-based domains using official Let's Encrypt tools. After that, you can configure your web-server to use the newly generated certificates as described in the guide below
HI @DevMude,
Just a quick note to let you know we have created a new PR with the required changes in the bncert-tool at https://github.com/bitnami/bncert/pull/17
Hi @DevMude,
Just a quick note to let you know we have released a new bncert-tool asset (version 2.0.0) including support for IPv6-based domains. The tool should detect there is a new version and ask you to auto-update it from current version. Alternatively, you can download it from the link below
https://downloads.bitnami.com/files/bncert/latest/bncert-linux-x64.run
Let us know if it works for you now. Hope it helps!
This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.
Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.
Describe your suggestion as much as you can
As stated in the documentation:
AWS is introducing a new charge for IPv4 addresses. This will amount to $3.60/mo per public IPv4 address in use.
Would save users lots of $$$ to have the bncert-tool support IPv6.