> DATE: Sun Jun 12 21:17 CDT 2022

UPDATE (Sat Jul 09 17:59 CDT 2022) (Revised Thu Sep 01 19:27 CDT 2022)

I figured out what was wrong with my capsule load/connect times. It turns out that when I updated my router, my IPv6 settings were not up to par. Even though everything was working about as well as could be, several clients (including this server) were changing their IPv6 addresses once they expired. I couldn't figure out how to make the router assign those addresses via DHCP (static addressing in all but name), so I just removed the AAAA records from my domain. Now, I could go directly to the devices and make the IPs static, but as some of them are headless Raspberry Pis, a static configuration would become nuisance should my home network network experience a significant configuration change (i.e. a new router that uses an atypical subnet by default).

So in short, diohsc was trying to connect via IPv6 first (using a nonexistent IPv6 address) whereas Amfora was attempting to connect via IPv4 first. The IPv4 side of my network is configured correctly with port forwarding, so when connecting over IPv4, I observed the expected behavior.

Interesting Capsule Behavior

I noticed something interesting this weekend. It turns out that my capsule loads quite slowly in diohsc but is just as snappy as most other capsules I browse to in diohsc, Amfora, and Lagrange when I open it in the latter two browsers. I don't really know why this is. Overall the Agate server is great, so I'm hard-pressed to blame it for this. Given that I've been running this capsule for almost a year and a half, it's possible that the improvements to Agate since my initial launch have resulted in some sort of configuration mismatch that a more advanced browser like diohsc would be sensitive to.

My hypothetical solution is to have a fresh start with the same TLS keys, but we'll see. I have to research this a bit before I do that. I also have a strange directory structure (due to my ignorance setting up Agate for the first time) that I'd like to keep since I rsync from my laptop to this server. It's not much of a pain to work out the new path, but I just would rather not bother. Things work a little too nicely as they are to warrant change.

Anyways, if anyone is reading this and has a well-informed theory, feel free to send me an email. It could be a good opportunity to learn something. Although, don't expect me to reply promptly. I kind of try to ignore my emails.

Email: samuel.scott@posteo.net