Time Nick Message 12:00 rubenwardy ContentDB is down because the letsencrypt failed. The error is a timeout when accessing .well-known, but I can access it fine from my laptop and my other VPS... 12:05 sfan5 messed up ipv6? 12:12 rubenwardy perhaps, I've not changed anything 12:13 rubenwardy ah yes, that's the issue 12:19 rubenwardy ipv6 sucks, I've never had a good experience with it 12:22 sfan5 it's additional stuff you have to learn because it's different 12:22 sfan5 yet there's no inherent advantage to setting it up 12:22 rubenwardy Could I just remove the AAAA records from my DNS? 12:23 rubenwardy hmm, I'd also need to disable the interface on the machine 12:23 rubenwardy so it doesn't communicate back over ipv6 12:23 sfan5 just removing the record suffices 12:23 sfan5 but maybe I can help you fix ipv6 instead 12:25 rubenwardy perhaps, this isn't the first time it's broken 12:26 rubenwardy the AAAA seems to match the `ip addr`, so it's probably nginx or a binding issue 12:27 sfan5 check `ss -6ln` or `netstat -6ln` 12:28 rubenwardy I see port 80 and 443 there 12:28 rubenwardy in the former 12:29 sfan5 should be working then, but I can't reach content.minetest.net over ipv6 12:29 sfan5 firewall? 12:30 rubenwardy I use ufw, Nginx Full is allowed for ipv6 12:32 sfan5 it doesn't respond to pings over ipv6 either.. 12:32 sfan5 what about outgoing connections? does `curl -6 ip.sb` work? 12:33 rubenwardy I get "couldn't connect to server" 12:35 sfan5 then ipv6 connectivity is broken entirely 12:35 sfan5 you can either try to follow https://docs.ovh.com/gb/en/dedicated/network-ipv6/ or just remove the AAAA record from your dns 19:16 Jordach sfan5, quickly rebasing first_person_attach 19:20 Jordach yep, seems to be working fine post rebase 19:21 Jordach pushed