netlify 502 bad gateway: sharp
0xrpj opened this issue · comments
I was working on macOS.
Fixed with this command:
npm install --platform=linux --arch=x64 sharp
Thanks @0xrpj! There might be a need for us to remove the package-lock.json as I think that npm install command will fix the deployed environment for some folks, but end up breaking local.
Either way, I'll link to this thread from the README for now. And I'm gonna re-open the issue so other people can add information as we learn where it stands up and falls down.
Any fix available yet? Thanks!
@GudCode You're experiencing this issue? It should be fixed now with netlify deploys since locking to a lower version of Satori and removing the package-lock.json
If you ran npm update that could be a reason you're experiencing this. Try deleting the node_modules directory and package-lock.json locally and then running npm install again and see if it fixes stuff.
Yes, no luck. When I test it in https://warpcast.com/~/developers/frames by clicking the frame's button. I get:
?frame=poster
postFakeCastFrameAction 400 - Failed to post fake frame action: Failed to post to frame. Error: Request failed with status code 502
@depatchedmode Any ideas why this is occurring? Thanks!
@GudCode Bit stumped, honestly. This might be the moment where we need a real dev.
Let me find time to look at this along some other upgrades this week. Can you share a link to the deployed frame so that I can test against the error?
@GudCode @depatchedmode did you guys ever figure this out? Encountering same.
@beeboopx Couple of questions and I should be able to help:
- Which version of
simplest-frameare you on? I fixed some things last night for v0.11.1 - What operating system are you developing from locally? There will be differences in the sharp build used locally, versus the one used on Netlify. Hoping to find a way for this to be accounted for by default but need to do more testing.
- Do you have any logs you can share of the error? Might help to debug your specific case.