I've tried several different methods to forcing to https and have zero luck doing so:
I thought that it was something to do with the originally generated certificate, so I tried redoing it and ended up with this problem:
Even though my domain IS on the internet:
http://freezepeach.xyz https://freezepeach.xyz compare, and of course testing becomes a bear once the browser locks on that https works it ignores typing http manually, though just typing or linking the domain as it is is what people are doing, giving them a broken site.
You requested a certificate for www.freezepeach.xyz without having a corresponding entry in DNS. Either do not request www.freezepeach.xyz or put www.freezepeach.xyz in DNS.
@HopeStillFlies, that’s an unfamiliar problem to me. It looks like it might be related to this issue:
Do you have a GitHub account that you could use to participate in that discussion and describe your situation?
My intuition is that it might have something to do with a problem that the client has in changing Apache configurations twice in two slightly different ways, but I’m not certain of that.