Replies: 3 comments
-
Hello @pro-sumer, thanks for the clear writeup of the steps you've taken so far. They make sense to me, but right off the bat I cannot say what is going wrong. One suggestion I have is to temporarily comment out
from the Caddyfile and replace it with something like
and make sure the certificate provisioning alone works, with Healthchecks removed from the mix.
The "DNS only" setting is the simpler one and I would start with that: with this setting Cloudflare is acting as a DNS service only, clients connect directly to your server, and your server is terminating TLS. Once this works, and once you know you do want Cloudflare's protection or some of their other features, you can enable the proxying.
The Healthchecks container does not expose any ports to the host by default. In the walkthrough, the caddy container was accessing Healthchecks through docker's internal networking (I'm not sure how this works in detail, and perhaps I'm using wrong terminology). |
Beta Was this translation helpful? Give feedback.
-
Good suggestion! That should indeed help discovering where the problem resides. After doing that I do see "Hello, world!" in a browser when visiting In fact, after reverting to the setup I posted above, I am now greeted by the Healthchecks web UI when surfing to the same URL! I will continue following your walkthrough tonight. Hopefully I can report success soon?! |
Beta Was this translation helpful? Give feedback.
-
Success! Got a very basic instance running on my OCI. More to be done later, but very happy so far. Thank you for creating and open-sourcing this! |
Beta Was this translation helpful? Give feedback.
-
Currently I'm running a Mastodon instance on the free tier of Oracle Cloud Infrastructure, using the setup from @faevourite. The Compute VM is mostly idle, so I was hoping I could follow your walkthrough to run Healthchecks on OCI as well. Since that Mastodon setup is already using Docker and Caddy I was hoping this should even be possible for a (partial) noob like me. Unfortunately I did not succeed, but I'm willing to learn, so I hope somebody can give me some advice on how to continue.
I'm failing pretty early in your walkthrough. This is what I have done so far:
hc.prosumer.dev
to the IP address of my OCI Compute VM (using dnscontrol and Cloudflare name servers)Caddyfile
docker-compose.yaml
Addition to
Caddyfile
:(for reference; it already contained a.o. this, which works for the Mastodon instance:)
Addition to
docker-compose.yaml
:However, when I try to access
hc.prosumer.dev
in a browser, Cloudflare shows error code 526 (Invalid SSL certificate).It does not seem to matter whether I use "Proxied" or "DNS only" for the A record; both options result in error 526.
I don't know whether this is relevant but I noticed that
docker container ls
lists3000/tcp, 4000/tcp
under thePORTS
column for "web", "streaming", and "sidekiq", but nothing at all for "hc" (shouldn't that have8000/tcp
?).What am I doing wrong? What am I missing?
Advice for a novice is very welcome!
Beta Was this translation helpful? Give feedback.
All reactions