Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

netlify 502 bad gateway: sharp #3

Open
0xrpj opened this issue Jan 29, 2024 · 10 comments
Open

netlify 502 bad gateway: sharp #3

0xrpj opened this issue Jan 29, 2024 · 10 comments
Labels
bug Something isn't working

Comments

@0xrpj
Copy link

0xrpj commented Jan 29, 2024

No description provided.

@0xrpj
Copy link
Author

0xrpj commented Jan 29, 2024

image

@0xrpj
Copy link
Author

0xrpj commented Jan 29, 2024

I was working on macOS.

Fixed with this command:
npm install --platform=linux --arch=x64 sharp

@0xrpj 0xrpj closed this as completed Jan 29, 2024
@depatchedmode
Copy link
Owner

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.

@depatchedmode depatchedmode reopened this Jan 29, 2024
@depatchedmode depatchedmode added the bug Something isn't working label Feb 1, 2024
@depatchedmode depatchedmode changed the title Hey, this is getting 502 bad gateeway while deploying on netlify, how'd you fix it in your app? netlify 502 bad gateway: sharp Feb 12, 2024
@iteration-n
Copy link

Any fix available yet? Thanks!

@depatchedmode
Copy link
Owner

@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.

@iteration-n
Copy link

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

@iteration-n
Copy link

@depatchedmode Any ideas why this is occurring? Thanks!

@depatchedmode
Copy link
Owner

@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?

@beeboopx
Copy link

@GudCode @depatchedmode did you guys ever figure this out? Encountering same.

@depatchedmode
Copy link
Owner

@beeboopx Couple of questions and I should be able to help:

  1. Which version of simplest-frame are you on? I fixed some things last night for v0.11.1
  2. 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.
  3. Do you have any logs you can share of the error? Might help to debug your specific case.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants