URGENT: Application not accessible via browser on subnet pjljw-kztyl-46ud4-ofrj6-nzkhm-3n4nt-wi3jt-ypmav-ijqkt-gjf66-uae

Since around 8 PM EST our application is no longer accessible via browser. We are receiving 500 errors from the boundary nodes. This impacts the other test environments that we deployed in the same subnet which we haven’t touched in days, so we don’t believe it’s a result of a code change on our end.

You can also see many access control headers being sent in the response from the boundary node, so something appears buggy.


@diegop Is there someone on the team you could forward this to?

/api/v2/ requests were never really meant to go through raw (as that would prevent your canister from handling those requests). We recommend modifying your usage of the agent and sending them to https://ic0.app directly. That should resolve your issue.

That said those requests should be getting 307 redirected, and we are working on correcting this to give developers time to migrate before removing the redirect.


@Daniel-Bloom How do we make that change safely? If we point to ic0.app instead of raw.ic0.app it works but it will ask to create a new Principal ID

Found it, hardcoding host to point to the non-raw URL worked.
const agent = new HttpAgent({ host, identity });

1 Like

In modclub_assets/src/modclub_assets/src/utils/actor.ts I would recommend changing:

12:  // Setting host to undefined will default to the window location 👍🏻
13:  return isLocalEnv ? dfxConfig.networks.local.bind : undefined;

to use "ic0.app" instead of undefined.


Perfect thanks for the quick response @Daniel-Bloom

1 Like