Seems like someone is trying to navigate to your site with an invalid host name. Are you running on the latest version? There has been some improvements around this area that might resolve this.

Im running on image: getfider/fider:stable :)

is this still an issue @Antonio78318 ?

Yes it's still

Try using getfider/fider:main, it probably won't solve it, but at least it'll give you the hostname that is causing that error

Hi, I'm getting the same errors:

fider-app-1  | ERROR [2022-09-19T07:57:38Z] [WEB] Error Trace:
fider-app-1  | - failed to get certificate for 96.48.53.105 (app/pkg/web/ssl.go:164)
fider-app-1  | - 400 urn:ietf:params:acme:error:rejectedIdentifier: Error creating new order :: Cannot issue for "96.48.53.105": The ACME server can not issue a certificate for an IP address

fider-app-1  | ERROR [2022-09-19T08:08:24Z] [WEB] Error Trace:
fider-app-1  | - failed to get certificate for localhost (app/pkg/web/ssl.go:164)
fider-app-1  | - acme/autocert: server name component count invalid

However, the web container is working fine and the certificate has been generated successfully. I checked the BASE_URL variable and it is set correctly (with scheme https://subdomain.mydomain.com).
Any clues on what I'm doing wrong? Thank you

Having this issue as well on latest getfider/fider:main. It seems to be because the container healthcheck ./fider ping makes a request to localhost.

ERROR [2022-11-21T06:23:17Z] [WEB] Error Trace:
- failed to get certificate for localhost (app/pkg/web/ssl.go:164)
- acme/autocert: server name component count invalid

Container is unhealthy due to failing healthcheck:

The Fider app is working otherwise though.

Has there been any update on this? I'm getting the same error in the logs, even though the certificate has been created and everything appears to be working properly, otherwise.