No information found to solve challenge for identifier

1. Caddy version (caddy version):

v2.4.5 h1:P1mRs6V2cMcagSPn+NWpD+OEYUYLIf6ecOa48cFGeUg=

2. How I run Caddy:

As a WinSW service:

<service>
  <id>caddy_windows_amd64</id>
  <!-- Display name of the service -->
  <name>Caddy Web Server (powered by WinSW)</name>
  <!-- Service description -->
  <description>Caddy Web Server (https://caddyserver.com/)</description>
  <executable>D:\Caddy\caddy_windows_amd64.exe</executable>
  <arguments>run</arguments>
  <log mode="roll-by-time">
    <pattern>yyyy-MM-dd</pattern>
  </log>
</service>

a. System environment:

Windows Server 2019 version 1809 build 17763.2268

d. My complete Caddyfile config:

{
auto_https disable_redirects
}

import D:\Caddy\Caddy_TODDS

d. My complete import Caddy_TODDS config:

todds.gselements.com:80 {
	redir https://todds.gselements.com{uri} 307
}
todds.gselements.com:443 {
	reverse_proxy http://localhost:8101
	header {
		Strict-Transport-Security max-age=31536000;
	}
}

toddsdemo.gselements.com:80 {
	redir https://toddsdemo.gselements.com{uri} 307
}
toddsdemo.gselements.com:443 {
	reverse_proxy http://localhost:8102
	header {
		Strict-Transport-Security max-age=31536000;
	}
}

3. The problem I’m having:

I am trying to understand why the caddy-service.err.log files are full of tls.issuance.acme errors.

4. Error messages and/or full log output:

{"level":"error","ts":1634987731.7556803,"logger":"tls.issuance.acme","msg":"looking up info for HTTP challenge","host":"toddsdemo.gselements.com","error":"no information found to solve challenge for identifier: toddsdemo.gselements.com"}
{"level":"error","ts":1634987761.1739097,"logger":"tls.issuance.acme","msg":"looking up info for HTTP challenge","host":"todds.gselements.com","error":"no information found to solve challenge for identifier: todds.gselements.com"}

5. What I already tried:

I have tried deleting the certificates in the local cache, and upon restarting they are successfully reissued. Functionally, I can’t find any issues with the 307 temporary redirects, but I am worried that something is miss-configured and causing these errors in the log. I am dealing with a situation where it is beneficial to have 307 redirects instead of 301 permanent redirects. Perhaps these errors in the log are just a side effect of that?

6. Links to relevant resources:

https://caddyserver.com/docs/caddyfile/directives/redir

1 Like

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