@matigo groovy. https definitely doesn’t work but I can live with that in this case.
@matigo The computers I'm testing from don't have IPv6.
I'm certain hub.10centuries.org is NOT being proxied correctly through CloudFlare based on the difference in IPs coming back. Otherwise, I would see exactly the same IP address for as I do for 10centuries.org, which is…different.
In fact, I can connect to http://www.phoneboy.info just fine. It redirects me to the same URL, just https where it fails. And you said you're not running HTTPS because of certificate issues.
Which means I'm fairly certain it's connecting directly to your server at your house and not going through CloudFlare.
@matigo Something's messed up in your DNS config in CloudFlare.
When I use CloudFlare's DNS server (1.1.1.1) and resolve 10centuries.org, I get four IPs (2 each of IPv4 and IPv6) that are clearly CloudFlare IPs.
When I try to resolve hub.10centuries.org, I get…a completely different result. And…it doesn't work.
@matigo I can use that, but it seems like what I'm resolving to locally is…your local IP, which might be 118.106.35.52. traceroute stops at a commufa.jp address, not something CloudFlare.
@matigo Is hub.10centuries.org behind CloudFlare? Because…it doesn't seem like it is. Is that what I should use in my CNAME?
@matigo are you doing https on hub.10centuries.org? It's answering on port 80 but not 443…
@matigo The main issue is that DNS for a root domain (in this case phoneboy.info) likes an A record only (not a CNAME). Cloudflare allows this because "magic" but I'm trying to move away from them.
Might be able to make redirects work, though. Can you assign www.phoneboy.info (which I can CNAME) to my main blog (the one at phoneboy.info)?