Application Proxy - There was an error in the third-party application.

Thomas_Kwan
Shopify Partner
21 0 0

Hi there

 

Our app suddenly started getting this error since Friday (21 Jun, 2019). And the error can be seen from here - https://etechfocus-demo.myshopify.com/apps/simple-testimonials

 

That URL will hit our proxy URL ( https://myshopifyapps.com/simple-testimonials/proxy?shop=etechfocus-demo.myshopify.com) which is returning valid liquid codes. So we are not sure why our clients and our test app are getting this error.

Thanks for your help in advance.

0 Likes
Thomas_Kwan
Shopify Partner
21 0 0

Actually, we notice that our proxy was not even called. We setup our proxy as

 

Subpath prefix: apps

Subpath: simple-testimonials

Proxy URL: https://myshopifyapps.com/simple-testimonials/proxy

 

When we accessed our test store's https://etechfocus-demo.myshopify.com/apps/simple-testimonials, our proxy was not called. 

Saw the error code 500 from cloudflare

 

* Connection state changed (MAX_CONCURRENT_STREAMS updated)!
< HTTP/2 500
< date: Mon, 24 Jun 2019 14:50:10 GMT
< content-type: text/html; charset=utf-8
< set-cookie: __cfduid=df665a7c97b070af8aed7c0543ae7f76f1561387809; expires=Tue, 23-Jun-20 14:50:09 GMT; path=/; domain=.myshopify.com; HttpOnly
< set-cookie: _shopify_y=62873d60-a98e-4222-9d6a-0f59242c3fa1; path=/; expires=Thu, 24 Jun 2021 02:28:34 -0000
< set-cookie: _orig_referrer=; Expires=Mon, 08-Jul-19 14:50:10 GMT; Path=/; HttpOnly
< set-cookie: _landing_page=%2Fapps%2Fsimple-testimonials; Expires=Mon, 08-Jul-19 14:50:10 GMT; Path=/; HttpOnly
< set-cookie: secure_customer_sig=; path=/; expires=Fri, 24 Jun 2039 14:50:10 -0000; secure; HttpOnly
< set-cookie: cart_sig=; path=/; expires=Mon, 08 Jul 2019 14:50:10 -0000; HttpOnly
< content-security-policy: block-all-mixed-content; frame-ancestors *; upgrade-insecure-requests; report-uri /csp-report?source%5Baction%5D=app_liquid&source%5Bapp%5D=Shopify&source%5Bcontroller%5D=storefront_section%2Fapp_proxy&source%5Bsection%5D=storefront&source%5Buuid%5D=7d0fe70a-cdd0-4cd2-8d06-6afae0b17d26
< vary: Accept-Encoding
< x-shopid: 21465161
< x-shopify-stage: production
< x-sorting-hat-podid: 52
< strict-transport-security: max-age=7889238
< x-dc: gcp-us-east1,gcp-us-east1,gcp-us-east1
< x-sorting-hat-shopid: 21465161
< x-shardid: 52
< x-content-type-options: nosniff
< x-request-id: 7d0fe70a-cdd0-4cd2-8d06-6afae0b17d26
< x-download-options: noopen
< x-xss-protection: 1; mode=block; report=/xss-report?source%5Baction%5D=app_liquid&source%5Bapp%5D=Shopify&source%5Bcontroller%5D=storefront_section%2Fapp_proxy&source%5Bsection%5D=storefront&source%5Buuid%5D=7d0fe70a-cdd0-4cd2-8d06-6afae0b17d26
< x-permitted-cross-domain-policies: none
< content-language: en
< expect-ct: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
< server: cloudflare
< cf-ray: 4ebf8333caa6a366-HKG

0 Likes
jem_punsalan
New Member
5 0 0

We are also getting this issue, when we tried to use proxy tunnel (ngrok) pointing to our local app, it is working fine. But when using a domain for the app proxy it is the same as what you are getting. Anything else we need to look into? Thanks

0 Likes
Thomas_Kwan
Shopify Partner
21 0 0

Hi jem_punsalan

 

Are you just recently getting this error? I started getting this error since around last Friday 06/21/2019.

 

Thomas

0 Likes
jem_punsalan
New Member
5 0 0

Hi @Thomas_Kwan we only get this issue yesterday, am not sure if theres new implementations related to App Proxy for Shopify.

0 Likes
Thomas_Kwan
Shopify Partner
21 0 0

Hi jem_punsalan

 

We just tried ngrok, and yeah, it worked for us. This will be a good short-term work around for us. Almost feel like there is cloudflare is calling some IPs (ngrok's ) but not all (our server for example).

So with ngrok.io domain in the proxy URL works, but not with our domain. Using ngrok introduces an extra layer of networking routing which is not desirable.

 

thomas

0 Likes
jem_punsalan
New Member
5 0 0

Hi @Thomas_Kwan we only use ngrok for local testing our app. As for the domain app proxy issue, still not clear of the root cause. We are still trying to find the solution for this. Let us know if you also find something related to the app proxy issue.

0 Likes
pixeledluke
Tourist
8 0 1

Hi Thomas,

 

We have been experiencing exactly the same issue at: https://unionsubscriptions.myshopify.com/apps/fulfilment which is supposed to be proxying a subdomain, but doesn't seem to be getting hit at our side. Getting the same 500 error you have reported.

 

If we visit the proxying url directly, it works, just as you are seeing. We first started noticing this on the 20/06/2019.

 

I've seen your thread with CloudFlare, and seen they mentioned that Shopify have just started working with them. Have you have any update from them, or have you got any further with the issue your side?

 

Cheers,

Luke.

0 Likes
Thomas_Kwan
Shopify Partner
21 0 0

Hi Luke

 

I did not get any further update from Shopify yet. Currently as a short-term fix, I have setup a ngrok channel and I have changed the proxy url to point to ngrok instead of my server directly.That seems to be working fine.

 

We have 2 apps and I have left one app pointing to our server so that I can tell if the problem has been resolved or not.


https://etechfocus-demo.myshopify.com/apps/simple-testimonials (With short-term fix, running thru ngrok)

https://etechfocus-demo.myshopify.com/apps/proxy (Pointing to our server, still broken)

 

I will update this thread when i have additional info.

 

thanks

thomas

0 Likes
Thomas_Kwan
Shopify Partner
21 0 0

Here is timeline with the Shopify Support so far

 

Jun 24, 03:55 (13350334)

- Reported the error and I was told the problem will be reported to the Partners team

"regarding to that I can ask the Partners team, I have your email and i will give it to the said team so that they can contact you"

 

Jun 25, 04:41 (13363587)

- Enquiring status and I was told that the ticket is in the system but the ticket was NOT assigned
"The partner specialists have the ticket in the system so you have done everything right, this is a technical query so a Guru like me would be of no help to you, but they will reach out as soon as the ticket arrives on their desk"
" Then I can tell you that at this time there is no partner manager assigned to your account"

 

Jun 26 17:35 (13383873)

- Asking about status and got help from support to raise the priority up
"I will set the ticket as more urgent priority so they review it sooner but typically it does take our escalated teams 24-72hrs to review tickets"
"And it was escalated on Monday, I will also include your 2nd support ticket with it so they can review both at once"

 

Jun 27 16:55 (13395784)
- Asking for status

"just reaching out to our partner team to what's going on with the ticket since I can see it was opened on Monday"
"It appears that we can escalate this to our technical team as well so I will do that, I'm just going to ask you a few more questions so that I can get all of the information the first time and save some time"

0 Likes