Our Partner & Developer boards on the community are moving to a brand new home: the .dev community forums! While you can still access past discussions here, for all your future app and storefront building questions, head over to the new forums.

Re: Proxy issue 500 response

Solved

Proxy issue 500 response

mchase
Tourist
3 1 1

Hi 

I've developed a custom app that simply serves static files for PWA features , which is served at , https://cb.pwa.mcjb.enterprises/d/manifest.json

Proxy configuration

Screenshot from 2020-09-10 12-05-39.png

Response when installed in the app.

Screenshot from 2020-09-10 12-08-12.png

Any idea?

Much appreciated 

Matt

Accepted Solution (1)
mchase
Tourist
3 1 1

This is an accepted solution.

Turns out it was a few problems, for anyone reading this if you use the shopify koa app and implement server.use to serve static files make sure you implement it before createShopifyAuth as requests to /a/proxy/manifest.json for example will attempt to re-authenticate if implemented afterwards and return a 302 redirect back to root.

Calling the wrong URL was my first problem once I sorted that out I still had the same issues, turns out that if you are calling static files in this way it will not work on a development store due to the store being password protected.

View solution in original post

Replies 5 (5)

darrynten
Shopify Partner
48 3 18

I've been experiencing major issues with the App Proxy since the beginning of the month.

I'm convinced they changed something recently, and have reached out to support for more info.

@darrynten
mchase
Tourist
3 1 1

Could be something to do with this, notice that content-encoding is stripped from the header, https://stackoverflow.com/questions/48931350/content-encoding-header-not-returned-from-cloudfront

mchase
Tourist
3 1 1

This is an accepted solution.

Turns out it was a few problems, for anyone reading this if you use the shopify koa app and implement server.use to serve static files make sure you implement it before createShopifyAuth as requests to /a/proxy/manifest.json for example will attempt to re-authenticate if implemented afterwards and return a 302 redirect back to root.

Calling the wrong URL was my first problem once I sorted that out I still had the same issues, turns out that if you are calling static files in this way it will not work on a development store due to the store being password protected.

darrynten
Shopify Partner
48 3 18

Did disabling the password on the store fix the problem?

@darrynten

criticDev
Shopify Partner
3 0 2

what helped me is deploying my app using "npm run deploy" and then activating my embed block in the current theme.