controller.go:131] cert-manager/controller/challenges "msg"="re-queuing item due to error processing" "error"="Cloudflare API Error \n\t Error: 6003: Invalid request headers\u003c- 6103: Invalid format for X-Auth-Key header" "key"="monitor-api/all.api.eosasia.one-3316827228-3059390612-2382995675"

[zhaochenglan]

Bugs should be filed for issues encountered whilst operating cert-manager.
You should first attempt to resolve your issues through the community support
channels, e.g. Slack, in order to rule out individual configuration errors.
Please provide as much detail as possible.

Describe the bug:
A clear and concise description of what the bug is.

i created Issure of cloudflare

controller.go:131] cert-manager/controller/challenges "msg"="re-queuing item  due to error processing" "error"="Cloudflare API Error \n\t Error: 6003: Invalid request headers\u003c- 6103: Invalid format for X-Auth-Key header" "key"="monitor-api/all.api.eosasia.one-3316827228-3059390612-2382995675"

Expected behaviour:
A concise description of what you expected to happen.

Steps to reproduce the bug:
Steps to reproduce the bug should be clear and easily reproducible to help people
gain an understanding of the problem.

Anything else we need to know?:

Environment details::

• Kubernetes version (e.g. v1.10.2):
• Cloud-provider/provisioner (e.g. GKE, kops AWS, etc):
• cert-manager version (e.g. v0.4.0):
• Install method (e.g. helm or static manifests):

/kind bug

[vmrm]

Is there any progress on that bug?

[archonic]

I have also hit this. I'm getting:

Cloudflare API Error \n\t Error: 6003: Invalid request headers\u003c- 6103: Invalid format for X-Auth-Key header" "key"="example/example-production-976563017-440184870-1077222838

@zhaochenglan Have you resolved your issue?

[archonic]

I've solved this for myself. I had created an API token, but it needs the "Global API Key".

[stek29]

@archonic use apiTokenSecretRef instead of apiKeySecretRef, it's available since #2170 was merged

[stek29]

It's not a bug, it's a misconfiguration, so maybe the issue be closed?

[jacobblock]

ty, apiTokenSecretRef worked for me. And needed perms Zone:Read, DNS:Edit on the token.