I don’t know what I’m doing, I need help. I’m trying to setup my website so I can access it from port 443. I have the server equipment in my house, all guides I find say to contact my host but that’s me. I’m at the point where I think it’s cloudflares DNS. I am using the Kemp load balancer and a wildcard ssl from cloudflare. I followed a network chuck tutorial to set that up, the plex server just worked, I basically had no configuration on the plex server and SSL works on that no problem, why doesn’t it do the same for an ecommerce site? I figure it’s a configuration issue. My ISP blocks port 80 so none of the traditional guides work because everything assumes certbot will have access to port 80, so I found a way for certbot to just look for the dns txt file and that works, but certbot doesn’t setup any of the https configurations in apache2, since I don’t know what I’m doing I assume that’s where I’m making mistakes.
I can’t verify if this is my servers problem or cloudflare though. I always get a 520 error when I try to access my website, if I put plex in front of the domain i.e. plex.website.com that gets the ssl no problem, my website is on website.com though, that doesn’t work and gets the 520 error. It works fine from port 80 internally. I don’t even know where server logs are stored, everything says to check server logs but I’m so clueless I have no clue where they are. Would those be apache logs? I am getting incredibly frustrated trying to get this working, I’ve been trying for 4 months and have no clue what I’m doing. I don’t want to continue paying my host because it costs a lot of money and it’s so damn slow. I have a good server here with tons of ram and a fast enough connection to serve what I need, but I can’t figure this out. Where would I even begin to try and figure this out?
If I shut the vm server off that hosts the website entirely I get an error saying the authenticity could not be verified. Well… it can’t be verified because it should be getting no response at all from the server since it is off. It doesn’t time out at all, it goes to that screen immediately. Nobody can get into my server to look because my isp blocks 80 and 443 works because kemp works, but I don’t know what the ■■■■ I’m doing, the only reason that works is because the tutorial worked as expected.