You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From one moment to another, with a deployment that did not touch anything near to cron requests or vercel.json, now cron requests are not receiving the CRON_SECRET variable and thus it resolves in 403. I could get rid of the security but I don´t want my crons to be publicly available.
this is how my code for checking the authorization header looks. It has worked perfectly for months, and it works locally. But suddenly now it does not work on production as authorization header is undefined.
Really need to know what is going on. I'm working with Node.Js express
The text was updated successfully, but these errors were encountered:
From one moment to another, with a deployment that did not touch anything near to cron requests or vercel.json, now cron requests are not receiving the CRON_SECRET variable and thus it resolves in 403. I could get rid of the security but I don´t want my crons to be publicly available.
this is how my code for checking the authorization header looks. It has worked perfectly for months, and it works locally. But suddenly now it does not work on production as authorization header is undefined.
Really need to know what is going on. I'm working with Node.Js express
The text was updated successfully, but these errors were encountered: