Getting 404 at CF Steps
umpire7777777 opened this issue · 4 comments
Hope you can help me find what I'm doing wrong.
I forked the repo, setup my secrets and variables. I'm getting a 404 error. This looks like a CF/Credential error, but I cannot figure it out :( I run a curl test to verify the token is valid. "This API Token is valid and active"
Pics of my repo action secrets:
Log at Delete old rule and list (If I comment this step out, fails at Create).
Run npm run cloudflare-delete
cloudflare-delete
npm run cloudflare-delete:rule && npm run cloudflare-delete:list
cloudflare-delete:rule
node cf_gateway_rule_delete.js
file:///home/runner/work/cloudflare-gateway-pihole-scripts/cloudflare-gateway-pihole-scripts/lib/helpers.js:106
throw new Error(HTTP error! Status: ${response.status}
);
^
Error: HTTP error! Status: 404
at request (file:///home/runner/work/cloudflare-gateway-pihole-scripts/cloudflare-gateway-pihole-scripts/lib/helpers.js:106:11)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async file:///home/runner/work/cloudflare-gateway-pihole-scripts/cloudflare-gateway-pihole-scripts/cf_gateway_rule_delete.js:4:27
Node.js v20.9.0
Error: Process completed with exit code 1.
Try removing the CLOUDFLARE_ACCOUNT_EMAIL
secret. It's not needed if you're using token authentication.
I started without that entry and had the same error, so I tried with it. I just removed it and have the same error.
Resolved. For others, the ID is NOT the userID, it's the account ID that looks like this:
5c836a76bc95766496cb94756e8675978 (this is fake)
The easiest way to find this is login to cloudflare, then this is the string after the dash URL:
https://dash.cloudflare.com/5c836a76bc95766496cb94756e8675978
Thank you!
closing