Caddy running in background, site not visible via curl or browser

Help
21

Ah wow, I don’t blame you.

I’d be super curious if you did the following exactly:

  1. Log into a brand new DigitalOcean droplet (either Debian or Ubuntu; I prefer Debian)
  2. Run the install commands provided by our documentation here: Install — Caddy Documentation
  3. Run sudo caddy add-package ... (your DNS plugin)
  4. Verify build with caddy list-modules, then run systemctl restart caddy
  5. Go to your server’s IP address in your browser and see if you get the “It works!” page

If you’ve already moved on from DO, no worries doing all this again. But I wonder if part of the problem is that third party tutorials are often over-complex or even wrong/outdated.

22

I’ve already moved on from Digital Ocean but if I ever create another droplet with them, I will certainly try this for you. I’m not sure what you mean by “your DNS plugin” in the third step, however.
Part of my problem was that one of the tutorials I used didn’t tell me to open allow an open port on 80 and 443. I agree though that a major part of the problem was outdated tutorials but I also don’t like the idea of having to restart a droplet (as was recommended here) as a work around for the machine-id issue.

23

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.