Safenet staking app fails to load (manifest.json error + postMessage origin mismatch)

Safe Development Wallet Web
1

Issue Description

When trying to access the Safenet staking app via Safe Wallet (https://app.safe.global), the app fails to load and only a blank screen is displayed.

Console Errors

The browser console shows the following errors:

  • Error loading Safe App manifest
  • Failed to fetch manifest.json (IPFS gateway)
  • postMessage target origin does not match recipient window’s origin
  • FetchEvent resulted in a network error

Example:

Error loading Safe App manifest (signal is aborted without reason)
postMessage target origin does not match recipient window’s origin
FetchEvent for manifest.json resulted in a network error

Environment

  • Browser: Chrome (latest)
  • OS: (e.g., Windows 11 )
  • Network: (home)

Steps to Reproduce

  1. Go to https://app.safe.global
  2. Connect wallet
  3. Try to access Safenet staking app
  4. App fails to load (blank screen)

Expected Behavior

Safenet staking app should load normally.

Actual Behavior

  • Blank screen appears
  • Safenet staking app does not render
  • Console shows manifest.json and postMessage errors

Additional Notes

  • Issue persists after hard refresh (Ctrl + Shift + R)
  • Also reproducible in incognito mode
  • Seems related to IPFS gateway (dweb.link) or Safe App origin validation
2

Hi @CLEMJ ,

Thanks for the detailed report. I can’t seem to reproduce this, unfortunately.

Do you have any ad blockers or extensions enabled that would interfere? That’s the most likely cause since Safe apps runs in iframes which can cause issues.

Does the gateway work for you when accessing it directly via https://bafybeibu22ajqhgpurle3rqsvbhgvikh2nheaprvgblt7odzw73hmkpfle.ipfs.dweb.link/?

In any way, you could use the staking app directly via https://staking.safenet-beta.eth.limo/ and then connect you Safe via WalletConnect. Would that work for you?

If the issue persists, could you please reach out to the Safe Wallet support via the chat box in the lower right corner on https://app.safe.global? The team has the best context there.

Hope this helps.

3

Hi @tschubotz

I was able to resolve the issue. The problem occurred as previously described, but after switching my connection to a US IP via VPN, the Safe App loaded correctly and worked without any errors.

Additionally, I’d like to provide some context from my side. I am a user based in South Korea, and currently there are situations where certain Cloudflare services or IP ranges appear to be broadly restricted at the network level by local policies. Because Safe Apps rely on IPFS gateways and Cloudflare infrastructure, this likely caused the access failure I experienced earlier.

So in this case, it seems the issue was not related to browser extensions or configuration, but rather a regional network restriction.

Thank you

2 Likes