1. Caddy version (caddy version):
v2.3.0
2. How I run Caddy:
Ubuntu 20 server
I just installed it, it doesnt run like it said it would, followed instructions on the main caddy website
a. System environment:
Ubuntu 20 server on an RPI
b. Command:
caddy start
sudo systemctl start caddy
sudo systemctl disable caddy
sudo systemctl enable caddy
caddy stop
caddy start
ect
paste command here
c. Service/unit/compose file:
paste full file contents here
d. My complete Caddyfile or JSON config:
# The Caddyfile is an easy way to configure your Caddy web server.
#
# Unless the file starts with a global options block, the first
# uncommented line is always the address of your site.
#
# To use your own domain name (with automatic HTTPS), first make
# sure your domain's A/AAAA DNS records are properly pointed to
# this machine's public IP, then replace the line below with your
# domain name.
https://shinobi.kaveman.tech {
reverse_proxy localhost:8080
}
https://pihole.kaveman.tech {
reverse_proxy localhost:8081/admin/index.php
}
# Set this path to your site's directory.
root * /usr/share/caddy
# Enable the static file server.
file_server
# Another common task is to set up a reverse proxy:
# reverse_proxy localhost:8080
# Or serve a PHP site through php-fpm:
# php_fastcgi localhost:9000
# Refer to the Caddy docs for more information:
# https://caddyserver.com/docs/caddyfile
3. The problem Iām having:
After playing with config a lot I realized Caddy was not actually running in the first place. I noticed some error messages sugesting 443 was already occupied but the only app on that was Caddy, I saw some issues other people had related to systemd running one instance while you try to start caddy through CLI and so tried the systemctl stuff above. Overall the youtube tutorial I watched had this up and running in 5 mins lol, I am lost however. Nothing Iāve tried gives back the return that seems to be expected for other folks with similar issues.
4. Error messages and/or full log output:
ā caddy.service - Caddy
Loaded: loaded (/lib/systemd/system/caddy.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sat 2021-01-30 17:11:22 CST; 4s ago
Docs: Welcome ā Caddy Documentation
Process: 74355 ExecStart=/usr/bin/caddy run --environ --config /etc/caddy/Caddyfile (code=exited, status=1/FAILURE)
Main PID: 74355 (code=exited, status=1/FAILURE)
########################################################
kevin@RP1:/etc/caddy$ caddy start
2021/01/30 23:22:56.669 INFO using adjacent Caddyfile
run: adapting config using caddyfile: server listening on [:443] is configured for HTTPS and cannot natively multiplex HTTP and HTTPS: /usr/share/caddy (try specifying https:// in the address)
start: caddy process exited with error: exit status 1
5. What I already tried:
A ton of stuff that possibly fucked Caddy right up and I may be better off purging at this point I guess