-
Notifications
You must be signed in to change notification settings - Fork 5
Open
Description
A block like the following including the wildcard directive:
https://*.hugeblank.dev/ {
tls {
dns cloudflare zonetoken <token>
wildcard
}
...
}
errors:
Aug 18 07:21:51 cole systemd[1]: Started Casket HTTP/2 web server.
Aug 18 07:21:51 cole casket[14504]: [INFO] Casket version: 1.4.7
Aug 18 07:21:51 cole casket[14504]: /etc/casket/Casketfile:4 - Error during parsing: Cannot convert domain name '*.hugeblank.dev' to a valid wildcard: already has a wildcard label
Aug 18 07:21:51 cole systemd[1]: casket.service: Main process exited, code=exited, status=1/FAILURE
Aug 18 07:21:51 cole systemd[1]: casket.service: Failed with result 'exit-code'.
due to this check.
Both lem and I think this is dumb and it could stand to be removed.
An error also occurs using the wildcard directive on a domain like hugeblank.dev which lem believes can be worked around and removed. The block for that situation is:
https://hugeblank.dev/ {
tls {
dns cloudflare zonetoken <token>
wildcard
}
...
}
and the error that occurs is:
Aug 18 07:20:33 cole systemd[1]: Started Casket HTTP/2 web server.
Aug 18 07:20:33 cole casket[14427]: [INFO] Casket version: 1.4.7
Aug 18 07:20:33 cole casket[14427]: 1.7555268333892713e+09 info maintenance started background certificate maintenance {"cache": "0xc000040100"}
Aug 18 07:20:33 cole casket[14427]: /etc/casket/Casketfile:4 - Error during parsing: Cannot convert domain name 'hugeblank.dev' to a valid wildcard: too few labels
Aug 18 07:20:33 cole systemd[1]: casket.service: Main process exited, code=exited, status=1/FAILURE
Aug 18 07:20:33 cole systemd[1]: casket.service: Failed with result 'exit-code'.
Metadata
Metadata
Assignees
Labels
No labels