Can't seem to get Caddy setup for my server and it's ports

Help
7

Just to clarify, there are two options (and it seems like you decided for the latter by now):

  1. Update how Cloudflare reaches your server in the SSL/TLS → Overview sidebar and select Full (strict) and have your DNS entry’s Proxy status set to Proxied (orange cloud icon)
  2. Disable Cloudflare Proxy by having your DNS entry’s Proxy status set to DNS Only (gray cloud icon)

Your lexiverse.vip (A record) resolves correctly to your server and Caddy serves the index.html in /usr/share/caddy, as expected by your Caddyfile.
Both sonarr.lexiverse.vip and tautulli.lexiverse.vip, however, are CNAMEs and point to Porkbun’s redirect service, which by itself redirects to http://lexiverse.vip:

❯ dog lexiverse.vip
A lexiverse.vip. 2m05s   76.71.143.112

❯ dog sonarr.lexiverse.vip
CNAME sonarr.lexiverse.vip. 3m14s   "pixie.porkbun.com."
    A pixie.porkbun.com.    1m00s   44.227.65.245
    A pixie.porkbun.com.    1m00s   44.227.76.166

❯ dog tautulli.lexiverse.vip
CNAME tautulli.lexiverse.vip. 5m00s   "pixie.porkbun.com."
    A pixie.porkbun.com.      1m00s   44.227.65.245
    A pixie.porkbun.com.      1m00s   44.227.76.166

# http/307 and `Location: http://lexiverse.vip`
❯ curl sonarr.lexiverse.vip -I
HTTP/1.1 307 Temporary Redirect
Server: openresty
Date: Sun, 31 Jul 2022 04:54:12 GMT
Content-Type: text/html; charset=utf-8
Content-Length: 168
Connection: keep-alive
Location: http://lexiverse.vip
X-Frame-Options: sameorigin

You will have to remove those CNAMEs and instead create A records similar to the one in lexiverse.vip.
Or you could keep that CNAMEs, but enter lexiverse.vip instead of pixie.porkbun.com.

That DNS chance may or may not take a while until it is propagated (no longer cached).

I am I won’t be able to reply for a while as it’s getting late for me.
Maybe that points you in the right direction, though. Or someone else will jump in to respond while I am asleep :innocent:

2 Likes