Lots of errors pouring into the log file that seem to be harmless. The site is working fine.
Not sure what I am doing wrong to get all these errors? The logs get quite large after a day or so…
1. Caddy version (caddy version):
v2.4.6 h1:HGkGICFGvyrodcqOOclHKfvJC0qTU7vny/7FhYp9hNw=
2. How I run Caddy:
a. System environment:
Ubuntu 20.04.3 LTS (aka focal)
systemd 245 (245.4-4ubuntu3.14)
Running on a DigitalOcean droplet
INBOUND:
ICMP
HTTP (80)
HTTPS (443)
OUTBOUND:
ICMP
TCP (all ports)
UDP (all ports)
b. Command:
sudo cp myCaddyfile /etc/caddy/Caddyfile
sudo systemctl reload caddy.service
c. Service/unit/compose file:
caddy.service
# caddy.service
#
# For using Caddy with a config file.
#
# Make sure the ExecStart and ExecReload commands are correct
# for your installation.
#
# See https://caddyserver.com/docs/install for instructions.
#
# WARNING: This service does not use the --resume flag, so if you
# use the API to make changes, they will be overwritten by the
# Caddyfile next time the service is restarted. If you intend to
# use Caddy's API to configure it, add the --resume flag to the
# `caddy run` command or use the caddy-api.service file instead.
[Unit]
Description=Caddy
Documentation=https://caddyserver.com/docs/
After=network.target network-online.target
Requires=network-online.target
[Service]
Type=notify
User=caddy
Group=caddy
ExecStart=/usr/bin/caddy run --environ --config /etc/caddy/Caddyfile
ExecReload=/usr/bin/caddy reload --config /etc/caddy/Caddyfile
TimeoutStopSec=5s
LimitNOFILE=1048576
LimitNPROC=512
PrivateTmp=true
ProtectSystem=full
AmbientCapabilities=CAP_NET_BIND_SERVICE
[Install]
WantedBy=multi-user.target
d. My complete Caddyfile or JSON config:
Caddyfile
# 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.
# :80
# 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:3000
# 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
http://meris.xyz {
redir https://www.meris.xyz{uri} permanent
}
(meris_rproxy) {
handle {
encode gzip
reverse_proxy {
to 0.0.0.0:{srv_port}
header_up ext-host {meris_host}
header_up host {host}
header_up origin {origin}
}
}
}
# handle direct DNS queries
www.meris.xyz {
# send all ddp requests to shared server @admin.test.meris.xyz
map {host} {meris_port} {srv_port} {meris_host} {
# "stest.meris.xyz" 5880 4880 "stest.meris.xyz"
# "stage.meris.xyz" 5280 4280 "stage.meris.xyz"
"www.meris.xyz" 5080 4080 "www.meris.xyz"
}
import meris_rproxy
# all queries logged to stderr by default
}
# =============
# ADMIN Routing
# =============
admin.meris.xyz {
map {host} {srv_port} {meris_host} {
# "admin.stest.meris.xyz" 5880 "admin.stest.meris.xyz"
# "admin.stage.meris.xyz" 5280 "admin.stage.meris.xyz"
"admin.meris.xyz" 5080 "admin.meris.xyz"
}
import meris_rproxy
}
# MINIO
https://b.meris.xyz, https://blob.meris.xyz {
reverse_proxy {
to 0.0.0.0:9000
header_up X-Forwarded-Proto {scheme}
header_up X-Forwarded-Host {host}
header_up Host {host}
health_uri /minio/health/ready
}
}
3. The problem I’m having:
tls.issuance.acme is pouring out errors.
Many of the errors are for domains not listed in my Caddyfile except within comments and one domain is not in the file at all.
Here is a sampling of them:
Error samples
# this looks right
Jan 4 21:26:13 ubuntu-s-1vcpu-1gb-amd-nyc1-01 caddy[1369]: {"level":"info","ts":1641349573.679473,"logger":"http","msg":"enabling automatic TLS certificate management","domains":["b.meris.xyz","blob.meris.xyz","www.meris.xyz","admin.meris.xyz"]}
# only used as http://
Jan 4 21:26:32 ubuntu-s-1vcpu-1gb-amd-nyc1-01 caddy[1369]: {"level":"error","ts":1641349592.0677156,"logger":"tls.issuance.acme","msg":"looking up info for HTTP challenge","host":"meris.xyz","error":"no information found to solve challenge for identifier: meris.xyz"}
# OK these should be challenged
Jan 4 21:26:34 ubuntu-s-1vcpu-1gb-amd-nyc1-01 caddy[1369]: {"level":"error","ts":1641349594.1415145,"logger":"tls.issuance.acme","msg":"looking up info for HTTP challenge","host":"www.meris.xyz","error":"no information found to solve challenge for identifier: www.meris.xyz"}
Jan 4 21:26:39 ubuntu-s-1vcpu-1gb-amd-nyc1-01 caddy[1369]: {"level":"error","ts":1641349599.2948058,"logger":"tls.issuance.acme","msg":"looking up info for HTTP challenge","host":"admin.meris.xyz","error":"no information found to solve challenge for identifier: admin.meris.xyz"}
Jan 4 21:26:34 ubuntu-s-1vcpu-1gb-amd-nyc1-01 caddy[1369]: {"level":"error","ts":1641349594.106386,"logger":"tls.issuance.acme","msg":"looking up info for HTTP challenge","host":"b.meris.xyz","error":"no information found to solve challenge for identifier: b.meris.xyz"}
# whoa! These domains are mentioned behind comments
# whey are they being challenged?
Jan 4 21:26:32 ubuntu-s-1vcpu-1gb-amd-nyc1-01 caddy[1369]: {"level":"error","ts":1641349592.856338,"logger":"tls.issuance.acme","msg":"looking up info for HTTP challenge","host":"admin.stest.meris.xyz","error":"no information found to solve challenge for identifier: admin.stest.meris.xyz"}
Jan 4 21:26:39 ubuntu-s-1vcpu-1gb-amd-nyc1-01 caddy[1369]: {"level":"error","ts":1641349599.3018298,"logger":"tls.issuance.acme","msg":"looking up info for HTTP challenge","host":"admin.stage.meris.xyz","error":"no information found to solve challenge for identifier: admin.stage.meris.xyz"}
Jan 4 21:26:42 ubuntu-s-1vcpu-1gb-amd-nyc1-01 caddy[1369]: {"level":"error","ts":1641349602.25449,"logger":"tls.issuance.acme","msg":"looking up info for HTTP challenge","host":"stest.meris.xyz","error":"no information found to solve challenge for identifier: stest.meris.xyz"}
Jan 4 21:26:47 ubuntu-s-1vcpu-1gb-amd-nyc1-01 caddy[1369]: {"level":"error","ts":1641349607.1742175,"logger":"tls.issuance.acme","msg":"looking up info for HTTP challenge","host":"stage.meris.xyz","error":"no information found to solve challenge for identifier: stage.meris.xyz"}
# whoa! whoa! this domain is not even in my Caddyfile
# I had it in previous Caddyfiles but have since
# reloaded and then I stopped the service and restarted
# then I rebooted. This old name is still haning around
Jan 4 21:26:34 ubuntu-s-1vcpu-1gb-amd-nyc1-01 caddy[1369]: {"level":"error","ts":1641349594.112324,"logger":"tls.issuance.acme","msg":"looking up info for HTTP challenge","host":"bconsole.meris.xyz","error":"no information found to solve challenge for identifier: bconsole.meris.xyz"}
4. Error messages and/or full log output:
Note: tried to use debug directive but it failed
Jan 4 21:22:04 ubuntu-s-1vcpu-1gb-amd-nyc1-01 caddy[1771]: reload: adapting config using caddyfile: /etc/caddy/Caddyfile:45: unrecognized directive: debug
5 minutes of logs
Jan 4 21:26:13 ubuntu-s-1vcpu-1gb-amd-nyc1-01 caddy[1978]: {"level":"info","ts":1641349573.6682084,"msg":"using provided configuration","config_file":"/etc/caddy/Caddyfile","config_adapter":""}
Jan 4 21:26:13 ubuntu-s-1vcpu-1gb-amd-nyc1-01 caddy[1978]: 2022/01/04 21:26:13 [WARNING] Unnecessary header_up ('X-Forwarded-Proto' field): the reverse proxy's default behavior is to pass headers to the upstream
Jan 4 21:26:13 ubuntu-s-1vcpu-1gb-amd-nyc1-01 caddy[1978]: {"level":"warn","ts":1641349573.672293,"msg":"input is not formatted with 'caddy fmt'","adapter":"caddyfile","file":"/etc/caddy/Caddyfile","line":27}
Jan 4 21:26:13 ubuntu-s-1vcpu-1gb-amd-nyc1-01 caddy[1369]: {"level":"info","ts":1641349573.6735933,"logger":"admin.api","msg":"received request","method":"POST","host":"localhost:2019","uri":"/load","remote_addr":"127.0.0.1:43844","headers":{"Accept-Encoding":["gzip"],"Content-Length":["1913"],"Content-Type":["application/json"],"Origin":["localhost:2019"],"User-Agent":["Go-http-client/1.1"]}}
Jan 4 21:26:13 ubuntu-s-1vcpu-1gb-amd-nyc1-01 caddy[1369]: {"level":"info","ts":1641349573.676234,"logger":"admin","msg":"admin endpoint started","address":"tcp/localhost:2019","enforce_origin":false,"origins":["localhost:2019","[::1]:2019","127.0.0.1:2019"]}
Jan 4 21:26:13 ubuntu-s-1vcpu-1gb-amd-nyc1-01 caddy[1369]: {"level":"info","ts":1641349573.6768236,"logger":"http","msg":"server is listening only on the HTTPS port but has no TLS connection policies; adding one to enable TLS","server_name":"srv0","https_port":443}
Jan 4 21:26:13 ubuntu-s-1vcpu-1gb-amd-nyc1-01 caddy[1369]: {"level":"info","ts":1641349573.6771376,"logger":"http","msg":"enabling automatic HTTP->HTTPS redirects","server_name":"srv0"}
Jan 4 21:26:13 ubuntu-s-1vcpu-1gb-amd-nyc1-01 caddy[1369]: {"level":"info","ts":1641349573.6773958,"logger":"http","msg":"server is listening only on the HTTP port, so no automatic HTTPS will be applied to this server","server_name":"srv1","http_port":80}
Jan 4 21:26:13 ubuntu-s-1vcpu-1gb-amd-nyc1-01 caddy[1369]: {"level":"info","ts":1641349573.679473,"logger":"http","msg":"enabling automatic TLS certificate management","domains":["b.meris.xyz","blob.meris.xyz","www.meris.xyz","admin.meris.xyz"]}
Jan 4 21:26:13 ubuntu-s-1vcpu-1gb-amd-nyc1-01 caddy[1369]: {"level":"info","ts":1641349573.6845386,"logger":"tls.cache.maintenance","msg":"started background certificate maintenance","cache":"0xc0000f4a10"}
Jan 4 21:26:13 ubuntu-s-1vcpu-1gb-amd-nyc1-01 caddy[1369]: {"level":"info","ts":1641349573.6854987,"logger":"tls.cache.maintenance","msg":"stopped background certificate maintenance","cache":"0xc0000f4540"}
Jan 4 21:26:13 ubuntu-s-1vcpu-1gb-amd-nyc1-01 caddy[1369]: {"level":"info","ts":1641349573.6865418,"msg":"autosaved config (load with --resume flag)","file":"/var/lib/caddy/.config/caddy/autosave.json"}
Jan 4 21:26:13 ubuntu-s-1vcpu-1gb-amd-nyc1-01 caddy[1369]: {"level":"info","ts":1641349573.6879818,"logger":"admin.api","msg":"load complete"}
Jan 4 21:26:13 ubuntu-s-1vcpu-1gb-amd-nyc1-01 caddy[1369]: {"level":"info","ts":1641349573.6998959,"logger":"admin","msg":"stopped previous server","address":"tcp/localhost:2019"}
Jan 4 21:26:32 ubuntu-s-1vcpu-1gb-amd-nyc1-01 caddy[1369]: {"level":"error","ts":1641349592.0677156,"logger":"tls.issuance.acme","msg":"looking up info for HTTP challenge","host":"meris.xyz","error":"no information found to solve challenge for identifier: meris.xyz"}
Jan 4 21:26:32 ubuntu-s-1vcpu-1gb-amd-nyc1-01 caddy[1369]: {"level":"error","ts":1641349592.0679114,"logger":"tls.issuance.acme","msg":"looking up info for HTTP challenge","host":"meris.xyz","error":"no information found to solve challenge for identifier: meris.xyz"}
Jan 4 21:26:32 ubuntu-s-1vcpu-1gb-amd-nyc1-01 caddy[1369]: {"level":"error","ts":1641349592.856338,"logger":"tls.issuance.acme","msg":"looking up info for HTTP challenge","host":"admin.stest.meris.xyz","error":"no information found to solve challenge for identifier: admin.stest.meris.xyz"}
Jan 4 21:26:32 ubuntu-s-1vcpu-1gb-amd-nyc1-01 caddy[1369]: {"level":"error","ts":1641349592.856437,"logger":"tls.issuance.acme","msg":"looking up info for HTTP challenge","host":"admin.stest.meris.xyz","error":"no information found to solve challenge for identifier: admin.stest.meris.xyz"}
Jan 4 21:26:34 ubuntu-s-1vcpu-1gb-amd-nyc1-01 caddy[1369]: {"level":"error","ts":1641349594.1062756,"logger":"tls.issuance.acme","msg":"looking up info for HTTP challenge","host":"b.meris.xyz","error":"no information found to solve challenge for identifier: b.meris.xyz"}
Jan 4 21:26:34 ubuntu-s-1vcpu-1gb-amd-nyc1-01 caddy[1369]: {"level":"error","ts":1641349594.106386,"logger":"tls.issuance.acme","msg":"looking up info for HTTP challenge","host":"b.meris.xyz","error":"no information found to solve challenge for identifier: b.meris.xyz"}
Jan 4 21:26:34 ubuntu-s-1vcpu-1gb-amd-nyc1-01 caddy[1369]: {"level":"error","ts":1641349594.112324,"logger":"tls.issuance.acme","msg":"looking up info for HTTP challenge","host":"bconsole.meris.xyz","error":"no information found to solve challenge for identifier: bconsole.meris.xyz"}
Jan 4 21:26:34 ubuntu-s-1vcpu-1gb-amd-nyc1-01 caddy[1369]: {"level":"error","ts":1641349594.1129026,"logger":"tls.issuance.acme","msg":"looking up info for HTTP challenge","host":"bconsole.meris.xyz","error":"no information found to solve challenge for identifier: bconsole.meris.xyz"}
Jan 4 21:26:34 ubuntu-s-1vcpu-1gb-amd-nyc1-01 caddy[1369]: {"level":"error","ts":1641349594.1345665,"logger":"tls.issuance.acme","msg":"looking up info for HTTP challenge","host":"b.meris.xyz","error":"no information found to solve challenge for identifier: b.meris.xyz"}
Jan 4 21:26:34 ubuntu-s-1vcpu-1gb-amd-nyc1-01 caddy[1369]: {"level":"error","ts":1641349594.1351318,"logger":"tls.issuance.acme","msg":"looking up info for HTTP challenge","host":"b.meris.xyz","error":"no information found to solve challenge for identifier: b.meris.xyz"}
Jan 4 21:26:34 ubuntu-s-1vcpu-1gb-amd-nyc1-01 caddy[1369]: {"level":"error","ts":1641349594.1415145,"logger":"tls.issuance.acme","msg":"looking up info for HTTP challenge","host":"www.meris.xyz","error":"no information found to solve challenge for identifier: www.meris.xyz"}
Jan 4 21:26:34 ubuntu-s-1vcpu-1gb-amd-nyc1-01 caddy[1369]: {"level":"error","ts":1641349594.142327,"logger":"tls.issuance.acme","msg":"looking up info for HTTP challenge","host":"www.meris.xyz","error":"no information found to solve challenge for identifier: www.meris.xyz"}
Jan 4 21:26:34 ubuntu-s-1vcpu-1gb-amd-nyc1-01 caddy[1369]: {"level":"error","ts":1641349594.1703396,"logger":"tls.issuance.acme","msg":"looking up info for HTTP challenge","host":"www.meris.xyz","error":"no information found to solve challenge for identifier: www.meris.xyz"}
Jan 4 21:26:34 ubuntu-s-1vcpu-1gb-amd-nyc1-01 caddy[1369]: {"level":"error","ts":1641349594.1708992,"logger":"tls.issuance.acme","msg":"looking up info for HTTP challenge","host":"www.meris.xyz","error":"no information found to solve challenge for identifier: www.meris.xyz"}
Jan 4 21:26:39 ubuntu-s-1vcpu-1gb-amd-nyc1-01 caddy[1369]: {"level":"error","ts":1641349599.2640316,"logger":"tls.issuance.acme","msg":"looking up info for HTTP challenge","host":"admin.meris.xyz","error":"no information found to solve challenge for identifier: admin.meris.xyz"}
Jan 4 21:26:39 ubuntu-s-1vcpu-1gb-amd-nyc1-01 caddy[1369]: {"level":"error","ts":1641349599.2641172,"logger":"tls.issuance.acme","msg":"looking up info for HTTP challenge","host":"admin.meris.xyz","error":"no information found to solve challenge for identifier: admin.meris.xyz"}
Jan 4 21:26:39 ubuntu-s-1vcpu-1gb-amd-nyc1-01 caddy[1369]: {"level":"error","ts":1641349599.2942057,"logger":"tls.issuance.acme","msg":"looking up info for HTTP challenge","host":"admin.meris.xyz","error":"no information found to solve challenge for identifier: admin.meris.xyz"}
Jan 4 21:26:39 ubuntu-s-1vcpu-1gb-amd-nyc1-01 caddy[1369]: {"level":"error","ts":1641349599.2948058,"logger":"tls.issuance.acme","msg":"looking up info for HTTP challenge","host":"admin.meris.xyz","error":"no information found to solve challenge for identifier: admin.meris.xyz"}
Jan 4 21:26:39 ubuntu-s-1vcpu-1gb-amd-nyc1-01 caddy[1369]: {"level":"error","ts":1641349599.3018298,"logger":"tls.issuance.acme","msg":"looking up info for HTTP challenge","host":"admin.stage.meris.xyz","error":"no information found to solve challenge for identifier: admin.stage.meris.xyz"}
Jan 4 21:26:39 ubuntu-s-1vcpu-1gb-amd-nyc1-01 caddy[1369]: {"level":"error","ts":1641349599.3019164,"logger":"tls.issuance.acme","msg":"looking up info for HTTP challenge","host":"admin.stage.meris.xyz","error":"no information found to solve challenge for identifier: admin.stage.meris.xyz"}
Jan 4 21:26:40 ubuntu-s-1vcpu-1gb-amd-nyc1-01 caddy[1369]: {"level":"error","ts":1641349600.1123993,"logger":"tls.issuance.acme","msg":"looking up info for HTTP challenge","host":"meris.xyz","error":"no information found to solve challenge for identifier: meris.xyz"}
Jan 4 21:26:40 ubuntu-s-1vcpu-1gb-amd-nyc1-01 caddy[1369]: {"level":"error","ts":1641349600.1124938,"logger":"tls.issuance.acme","msg":"looking up info for HTTP challenge","host":"meris.xyz","error":"no information found to solve challenge for identifier: meris.xyz"}
Jan 4 21:26:42 ubuntu-s-1vcpu-1gb-amd-nyc1-01 caddy[1369]: {"level":"error","ts":1641349602.25449,"logger":"tls.issuance.acme","msg":"looking up info for HTTP challenge","host":"stest.meris.xyz","error":"no information found to solve challenge for identifier: stest.meris.xyz"}
Jan 4 21:26:42 ubuntu-s-1vcpu-1gb-amd-nyc1-01 caddy[1369]: {"level":"error","ts":1641349602.254576,"logger":"tls.issuance.acme","msg":"looking up info for HTTP challenge","host":"stest.meris.xyz","error":"no information found to solve challenge for identifier: stest.meris.xyz"}
Jan 4 21:26:47 ubuntu-s-1vcpu-1gb-amd-nyc1-01 caddy[1369]: {"level":"error","ts":1641349607.1740549,"logger":"tls.issuance.acme","msg":"looking up info for HTTP challenge","host":"stage.meris.xyz","error":"no information found to solve challenge for identifier: stage.meris.xyz"}
Jan 4 21:26:47 ubuntu-s-1vcpu-1gb-amd-nyc1-01 caddy[1369]: {"level":"error","ts":1641349607.1742175,"logger":"tls.issuance.acme","msg":"looking up info for HTTP challenge","host":"stage.meris.xyz","error":"no information found to solve challenge for identifier: stage.meris.xyz"}
Jan 4 21:27:35 ubuntu-s-1vcpu-1gb-amd-nyc1-01 caddy[1369]: {"level":"error","ts":1641349655.8039985,"logger":"tls.issuance.acme","msg":"looking up info for HTTP challenge","host":"meris.xyz","error":"no information found to solve challenge for identifier: meris.xyz"}
Jan 4 21:27:35 ubuntu-s-1vcpu-1gb-amd-nyc1-01 caddy[1369]: {"level":"error","ts":1641349655.8041055,"logger":"tls.issuance.acme","msg":"looking up info for HTTP challenge","host":"meris.xyz","error":"no information found to solve challenge for identifier: meris.xyz"}
5. What I already tried:
- Trimmed down the Caddyfile to its basics. I have been trying to reuse a single Caddyfile so I got rid of all of the unused stuff for this server.
- In addition to executing the
systemctl reload caddy.serviceI have tried
systemctl stop caddy.service
systemctl start caddy.service
Finally tried:
sudo reboot
I still keep getting the errors
