# Webserver on ipv6 **URL:** https://dietpi.com/forum/t/webserver-on-ipv6/5243 **Category:** Troubleshooting **Created:** [26 April 2021 20:13 UTC](https://dietpi.com/forum/t/webserver-on-ipv6/5243 "2021-04-26T20:13:16Z") **Posts on this page:** 1 **Showing post:** 12
### Author: ![trigrhappy](https://dietpi.com/forum/user_avatar/dietpi.com/trigrhappy/32/3898_2.png) [@trigrhappy](https://dietpi.com/forum/u/trigrhappy) #### Post date: [27 April 2021 17:53 UTC](https://dietpi.com/forum/t/webserver-on-ipv6/5243/12 "2021-04-27T17:53:45Z")
fwiw I’ve tried running “ss -tulpn | grep lighttpd” in a separate terminal while letsencrypt states that it’s listening for the https request… and it never appears to open port 443 to ipv6 traffic. EDIT: It seems to be the same problem shown here: [https://dietpi.com/forum/t/lets-encrypt-for-ipv6-only-websites/4334/1](https://dietpi.com/forum/t/lets-encrypt-for-ipv6-only-websites/4334/1) I manually edited the ssl conf in /etc/lighttpd/conf-enabled/ to “[::]:443” similar to the post above and restarted. It opened port 443. I ran letsencrypt, and it errored out at the end. I ran it again and it said the certificate already existed and was current for a long time. I chose not to overwrite… and my website is now accessible over ipv6. Looks like it actually succeeded in creating the certificate the first time despite the error. If I can do anything to help fix this bug, please let me know. --- _[View the full topic](https://dietpi.com/forum/t/webserver-on-ipv6/5243)._