Proxies stopped working at 26 August

Extensions
1

Hi everyone!

Are we having an outage at app theme extension proxies?

Yesterday this proxy at my development or the production app started returning 404 to every proxy call from my app theme extension regardless of its address and environment.

Dev environment:

[app_proxy]
url = "https://existed-criteria-tournaments-sudden.trycloudflare.com/apps"
prefix = "apps"
subpath = "myapp"

Production environment:

[app_proxy]
url = "https://mytestserver.mywebsite.com"
prefix = "apps"
subpath = "myapp"

I don’t see any logs about “route not found” at both development and production deployments, I also added various logs everywhere so I deduct requests are not reaching my Remix Admin app at all.

response = await fetch('/apps/myapp/api/proxy/uploadPic', {
  method: 'POST',
  body: formData
});

I’m using latest shopify cli version: 3.84.0 . I’m close to pulling my hair out.

How should I proceed on this?
Thank you

2

Im having the same problems, my fetch in extension all together wont process, Even with network_access = true configured, the runtime’s implementation of fetch() internally tries to construct a Request object, but the constructor is broken in the sandbox. I’ve been banging my head agaisnt a wall for 2 days:

"@shopify/ui-extensions": "^2025.10.0-rc.23",
"preact": "^10.10.x",
"@types/node": "^20.2.0",

Im using latest shopify cli version: 3.84.0 also. Not sure if its because of the RC Ui-Extensions or what but I can’t even do a GET request, never mind a POST

Im using a Partner Dev shop with password and enabled the checkout ui preview with network_access true on the extension toml. Im lost for ideas

3

Oh thank god I’m not the only one having this. Lets notify each other if we find a solution. But from the looks of it its beyond our reach. network_access = true in my toml too.

Only config I have in my extension.toml is this:

name = "my-app-name"
type = "theme"

network_access = true

Its an app theme extension. It needs to be able reach my Remix admin app

4

Hi folks - it’s possible this was related to a temporary bug which has been resolved. If you’re still seeing this issue, please let us know.

5

Thank you!
Workaround I used was resetting everything. I’m currently not having any problems with this.