Hi all!
It just stoped working. My proxy url results in 404 and error “Error: You made a POST request to “/” but did not provide an `action` for route “root”, so there is no way to handle the request.”
It used to work even with extended paths that I map to my backend. Like, /apps/my-path being base url and /apps/my-path/some-endpoint with custom path extension, but it results in 405 saying ‘Method not allowed’.
Please help.
I am currently troubleshooting this issue and could use some more information from you.
Please send an email to andrew.murray@shopify.com with your organization id, app id, and the affected shop id. The first two can be found from URL in developer dashboard.
Hi Andrew, thank you, it works now.
Thanks for following up @Marko_Jakic - I’ll close this thread out, glad to hear everything is working! Feel free to reach out to us again if we can help with anything 
How it works? is any troubleshooting u have done?
Hey @prasanth_sk 
- are you encountering the same issue? Issue, if so, feel free to ping me here along with any error messages and I can take a look into this for you as well.
Yeah I’m facing the same 404 in app porxy url issue @Alan_G
Hi @Alan_G Its been 2 days can i get any update on this ?
I’m getting quite frustrated with the lack of support
Hey @prasanth_sk, sorry for the delay here. Our staff are generally off on weekends, so I’m just catching up now; I definitely understand the frustration and really appreciate your patience.
I can dig into this during regular Eastern business hours and I’m happy to prioritize it. To move fast, could you please share your shop domain, the app’s ID, the exact app proxy URL you’re hitting in the browser, your current App proxy settings (prefix, subpath, and proxy URL), the server route that should receive this request and what it returns, and any X-Request-IDs from the 404 response headers?
If you’d prefer, feel free to let me know if you’d prefer to DM me the sensitive bits. Once I have those details, I can trace where the 404 is occurring and we can look at concrete next steps. Hope to hear from you soon!
Thanks @prasanth_sk, appreciate you sending all of this info my way. I’ll do some investigation into this on my end and loop back with you once I have more to share/next steps. Speak with you as soon as possible here
Hey @prasanth_sk - I can’t reach out over email due to our policies, but I’ll open up a DM with you here in the forums so that we can discuss privately, I was able to do some further digging an will share info with you there.
Morning @Alan_G
I’m currently facing this same issue. Two days ago (Sep 17th) I was forced to start using the Next Gen Platform (through my IDE console) and since then the proxy started throwing 404/500. It was pretty obvious because before doing the upgrade, I was using the proxy normally to debug some feature.
What I could see is that the app’s proxy URL gets “kind of” stucked. When I run “npm run dev”, I do not see the normal authenticate logs in the console. I figured it must be hitting somewhere else.
Please find below data from my dev environment:
Console shows:
app_proxy │ Using URL: https://.trycloudflare.com/proxy
app_proxy │ Any changes to prefix and subpath will only apply to new installs
Expected: shopify app dev preview uses the above proxy URL for the already-installed dev store.
Actual: /apps/dablox-push → 404 or 500 (no hit on my server). Direct GET https://<tunnel>/proxy → 200.
Tried:
shopify app dev preview linkapplication_url via --tunnel-url/proxy, GET/POST)It would be great if you could shed some light upon this matter.
Appreciate your help and support!
Best,
Matias
Hey @Matias_Corrao - happy to take a look into this and thanks for the details, based on what you’re seeing, it looks like the proxy is being forwarded to an invalid host, since the CLI output shows “Using URL: https://.trycloudflare.com/proxy” without a subdomain (unless you just edited it out there).
Normally, the Cloudflare Quick Tunnel created by shopify app dev should generate a full hostname (for example, https://abc123-test-tunnel.trycloudflare.com/proxy), so the empty hostname seems like there might be a misconfiguration or a CLI state issue rather than expected behavior.
Could you let me know if you’re using the current Shopify Remix template? Since you’re running app dev, it seems like it, but just wanted to confirm that. If you can also check the App proxy settings in your toml file that would be helpful!
If it currently shows https://.trycloudflare.com/proxy, replace it with your actual tunnel URL and retest to see if it sticks.
If you’re rely on the Shopify CLI-managed updates, try setting automatically_update_urls_on_dev = false in your shopify.app.toml and run shopify app dev clean to clear any temporary URLs before starting dev again. You could then switch it back to true to see if it generates the URLs as needed.
I also just wanted to share one of my colleague’s posts here that explains how Next Gen dev replaces URLs (including the Proxy URL) and how to reset your environment just in case it’s helpful:
If you’re still seeing those 404s/500s, just ping me here and we’ll dig deeper for sure. One thing that might help if you’re still seeing the issues is adding the -–verbose flag at the end of your shopify app commands, it can help us track down exactly what the app is doing and if you’re open to sharing those, that would be really useful! Hope this helps!
Hello Allan,
Thanks for the quick response. Sorry about the missing cloudflare subdomain, it was actually a typo error on my side, but the proxy was actually being well formed and accessible.
I’ve finally resolved this issue by setting up a new store and making a fresh app install on it. I was suspecting that the app setup for the store I was previously using had some inner issue, so I decided to test it
Thank you once again!
Best regards,
Matias
Hey Matias! No worries - glad this has been resolved and everything’s working for you. I’ll mark this thread as solved for now, but just ping me here if I can help out with anything else
Hey there. We are also encountering issues. We have not gone live on prod yet but our staging app has been impacted since releasing a new version following the next gen migration.
Any attempt to hit a proxy route is met with a 404 and we do not see any request hitting out staging server.
We have then tried to release a prior version of the app which was working before, and even that does not resolve the issue.
We have also tried to test locally and are seeing the same issues.
This is a big blocker for us as its stopping us being able to make any deployments and are worried about the customer impact when we do go to release the next version of our production app. This is compounded by the fact that even rolling back to an older version of the app release does not seem to solve the issue.
Suggesting creating a new store and app doesn’t seem like an acceptable solution as we need to be able to test the behaviour of a release on our staging app before we can go to prod.
Same here,
config that worked before:
dev
[app_proxy]
subpath = “proxy”
prefix = “apps”
url = “https://locally-tennis-ready-seek.trycloudflare.com/proxy”
staging
[app_proxy]
subpath = “proxy”
prefix = “apps”
url = “https://securify-remix-app-uzs6d.ondigitalocean.app/proxy”
now both apps when added with app embed shows
POST 404 https://vladislav-dog-photos.myshopify.com/apps/proxy/check-restriction
installed,uninstalled,deployed again - nothing helps.
Is this logic of subpath - prefix - url, how all is tight together, changed in next-gen?
btw why I don’t see my extension in dev console? I am running `shopify app dev`
UPD. OK it seems that the problem might be with extension ids, because next gen re-registered them silently and now I have no idea where to put new ids, could someone please tell me:
when I do deploy and I see:
│ Using .env.development for default values:
│ │
│ • Org: Etterno.io Inc │
│ • App: Securify 2.0 Dev
what else should be there in .env.development so the app correctly finds extensions and work with them?
Also the fact that shopify dev stopped updating related .toml is highly confusing. Now I have 2 independent processes that just I am not even sure how they are connected:
shopify app dev (which updates whatever the hell it wants and it seems has no impact on anything except its own internal working)shopify app deploy (which still wants correct .toml with all the links, so if you want to release a new development version you go and update all the trycloudflare links manually???)Hi @Vladislav_Sorokin – There are a few different questions/issues here and you are replying to a solved thread, but I will try to help.
deploy is still referencing the .env file. We don’t use them anymore. I’ll look into this. More details on this change here.app.toml because there was never a reason to commit the Cloudflare URLs to source control. The app URL is still updated, but just on your chosen development store. The new dev pushes all configuration and extensions to just your dev store. More details on the new app dev hereapp.toml, running a deploy, then adding it back and running deploy again?Hey @Nick , thanks for getting involved.
Yes, I tried to do this (removing the proxy entirely). Didn’t help.
Now I am creating new extension from scratch, hope it will work!
Also I noticed this weird instruction:
The theme app extension development server is ready. Next steps 1. Install your app in your development store [1] 2. Setup your theme app extension in the host theme [2] 3. Preview your theme app extension at http://127.0.0.1:9293
but when I test my theme on 127.0.0.1:9293 I hit cors obviously, so I am not sure, if this is new way of testing that the theme extension works? Before that I used to go to app embeds section on https://admin.shopify.com/store//themes, enabled it there, open my store on myshopify domain and see if my extension works or not.
Please start a new thread so someone w/ theme extension expertise can assist.