Install script not retrieving TLS cert

[jamf25]

So I have am trying to self host on my own metal at home. Port fwds in place, 80/443 reachable from internet sources dns lookups published and working but for some reason anytime I try to run the install.sh script on my self hosted hardware it will not complete the creation of the account in the final step and throws a curl: (35) error:0A00010B:SSL routines::wrong version number error. The docker logs -f caddy from a clean run are here

{"level":"info","ts":1737684701.316726,"logger":"http.log","msg":"server running","name":"remaining_auto_https_redirects","protocols":["h1","h2","h3"]}
{"level":"info","ts":1737684701.3168063,"logger":"http","msg":"enabling HTTP/3 listener","addr":":443"}
{"level":"info","ts":1737684701.3170195,"msg":"failed to sufficiently increase receive buffer size (was: 208 kiB, wanted: 7168 kiB, got: 416 kiB). See https://github.com/quic-go/quic-go/wiki/UDP-Buffer-Sizes for details."}
{"level":"info","ts":1737684701.3172107,"logger":"http.log","msg":"server running","name":"srv0","protocols":["h1","h2","h3"]}
{"level":"info","ts":1737684701.3172622,"logger":"http","msg":"enabling automatic TLS certificate management","domains":["*.example.com","example.com"]}
{"level":"info","ts":1737684701.3175092,"msg":"autosaved config (load with --resume flag)","file":"/config/caddy/autosave.json"}
{"level":"info","ts":1737684701.317562,"msg":"serving initial configuration"}
{"level":"info","ts":1737684701.3177493,"logger":"tls.cache.maintenance","msg":"started background certificate maintenance","cache":"0xc0003bb680"}
{"level":"info","ts":1737684701.336288,"logger":"tls","msg":"storage cleaning happened too recently; skipping for now","storage":"FileStorage:/data/caddy","instance":"bbb11069-f2ba-4808-9253-ab3d2dd2ac23","try_again":1737771101.3362844,"try_again_in":86399.999999521}
{"level":"info","ts":1737684701.336407,"logger":"tls","msg":"finished cleaning storage units"}

I'm no dev, so to me it looks like whatever this tls operation is should be doing something that it is not doing. I have proven this install script works flawlessly on an EC2 instance in AWS and pulls down the certs to /pds/caddy/data/caddy/certificates/ and everything works just fine. I've compared ufw/firewalld/iptables on both the EC2 and my home VM. The EC2 is ubuntu 22.04.5 and my home VM is 22.04.4. Haven't found anyone else with the same issue, so I feel like I'm just missing something super stupid. Happy to provide more info, or if this is a dumb question you can just close it. I'm out of ideas though. Worst case I can probably just run letsencrypt certbot and obtain a valid cert that way right?