1. Output of caddy version
:
v2.6.2 h1:wKoFIxpmOJLGl3QXoo6PNbYvGW4xLEgo32GPBEjWL8o=
2. How I run Caddy:
I am just running caddy as a test vanilla install , trying to configure the admin API options via JSON.
a. System environment:
CentOS Linux release 7.9.2009 (Core)
b. Command:
/usr/bin/caddy run --environ --config /etc/caddy/config.json
c. Service/unit/compose file:
Paste full file contents here.
Make sure backticks stay on their own lines,
and the post looks nice in the preview pane. -->
d. My complete Caddy config:
{
"admin": {
"identity": {
"identifiers": [
"127.0.0.1"
],
"issuers": [{
"module": "internal",
"ca": "",
"lifetime": 0,
"sign_with_root": false
}]
},
"remote": {
"listen": ":2021",
"access_control": [
{
"public_keys": [
"<redacted>"
]
}
]
}
}
}
3. The problem I’m having:
I’d like to know if its possible to configure caddy to have a “wildcard” identity > identifiers (i.e. “0.0.0.0” or “*”).
I am configuring caddy for a distributed network of servers and although I can just hard code all the public IPs of each of the servers in this section of the config JSON, it doesnt feel dynamic as I would have to update this portion every time a new server is added.
Is there a better way of doing this?
4. Error messages and/or full log output:
Paste logs/commands/output here.
USE THE PREVIEW PANE TO MAKE SURE IT LOOKS NICELY FORMATTED.