Replies: 2 comments
-
Tough to say -- there could be lots of things going wrong here and I don't have any experience with Caddy. The error at least sounds like the IP address you have configured Caddy is either wrong or not responding for some reason. Are you able to access Baby Buddy directly from the same IP you're using in the |
Beta Was this translation helpful? Give feedback.
0 replies
-
This caddy directive worked for me:
Can't tell if it's the scheme or that I'm referring a public IP. Also I struggled with timeouts from Caddy - forgot to open Port in the firewall. Maybe this helps you. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm trying to deploy babybuddy over my https://subdomain.domain.com using caddy, but it doesn't seem to work. What kind of env variables should I set?
caddy entry
Caddyfile
Browser returns
This site can’t be reached
subdomain.domain.com took too long to respond.
Beta Was this translation helpful? Give feedback.
All reactions