The demo is not working

[GGos3]

When I click the "Try the demo manager" button on the following URL: https://access-manager.openzeppelin.com/, I encounter the following error:

"Ahh snap! Something went wrong while fetching the Access Manager.[Network] Failed to fetch."

To troubleshoot the issue, I decided to access the NEXT_PUBLIC_URQL_ENDPOINT specified in the .env.example file.

NEXT_PUBLIC_URQL_ENDPOINT_MAINNET=https://api.thegraph.com/subgraphs/name/ernestognw/access-manager-mainnet
NEXT_PUBLIC_URQL_ENDPOINT_GOERLI=https://api.thegraph.com/subgraphs/name/ernestognw/access-manager-goerli
NEXT_PUBLIC_URQL_ENDPOINT_SEPOLIA=https://api.thegraph.com/subgraphs/name/ernestognw/access-manager-sepolia

For all three URLs, I received the following message:

"message": "This endpoint has been removed. If you are the owner of this subgraph you can upgrade it by going here: https://thegraph.com/hosted-service. If you have any questions, reach out to [email protected]. Learn more about why this happening here: https://thegraph.com/docs/en/sunrise/#upgrading-subgraphs-to-the-graph-network"

"This endpoint has been removed."

Therefore, I have a few questions:

1. Do you have any plans to update and maintain this endpoint?
2. If a user wants to use the explorer on their private network, how should they proceed?

Thank you for your efforts.

[yorhodes]

encountering the same issue
tried deploying on sepolia but cant get the demo to work with my deploy
I tried running things locally but couldnt get past these subgraph issues

[ernestognw]

Hey both! thanks for reporting
I updated the explorer and removed Goerli since it's been deprecated. It's working now with mainnet and sepolia only.

• If a user wants to use the explorer on their private network, how should they proceed?

Adding new networks is frankly easy if there's subgraph support. I'd recommend using Alchemy Subgraphs if your chain is supported, though, for private networks you might need a different solution.

A good indexer is ponder, but I haven't had the time to migrate the subgraph to Ponder, in that case, it'd be as easy as providing a reliable JSON RPC endpoint.