If you have a proper IPv6 address in your DNS you must also have an IPv6 listen statement in your nginx. But, the opposite is not true. It is fine to have nginx IPv6 listen statement but no AAAA record in your DNS. You just won't have IPv6 support then because no one can learn your IPv6 address. IPv6 is recommended if your ISP supports it.
Now you just have to figure out why your port 443 is blocked. Looks "filtered" so probably a firewall or some other comms related config for this port. It is affecting IPv4 and v6 equally.
>nmap -4 -Pn -p80,443 iridiandesigns.uk
Starting Nmap 7.94 ( https://nmap.org ) at 2023-10-23 20:07 UTC
Nmap scan report for iridiandesigns.uk (149.100.158.178)
Host is up (0.17s latency).
Other addresses for iridiandesigns.uk (not scanned): 2a02:4780:c:e27c::1
PORT STATE SERVICE
80/tcp open http
443/tcp open https
Nmap done: 1 IP address (1 host up) scanned in 0.20 seconds
>nmap -6 -Pn -p80,443 iridiandesigns.uk
Starting Nmap 7.94 ( https://nmap.org ) at 2023-10-23 20:07 UTC
Nmap scan report for iridiandesigns.uk (2a02:4780:c:e27c::1)
Host is up (0.15s latency).
Other addresses for iridiandesigns.uk (not scanned): 149.100.158.178
PORT STATE SERVICE
80/tcp open http
443/tcp open https
Nmap done: 1 IP address (1 host up) scanned in 0.19 seconds
Thanks for checking Bruce5051, I just reinstalled the certs and everything looks to be working now as expected, I guess it was the misconfiguration of my nginx conf file.
Note to self: don't delete cert files willy-nilly....