proxmox/docs/04-configuration/REOWN_CLOUD_DAPP_ORIGINS.md

Reown Cloud — Allowed Origins for DApp

WalletConnect/Reown requires your DApp’s origins to be allowlisted in the project settings. Otherwise the frontend can get 403 when fetching remote project configuration even when the project ID is correct in the bundle.

Project ID in use

• Project ID: b890bbeeff48275b4a115e2ef105195a
• Dashboard: https://cloud.reown.com

What to do

1. Log in at https://cloud.reown.com and open the project with the ID above.
2. Go to Settings (or Allowed origins / Domains).
3. Add these origins (exact scheme + host, no trailing slash):
   • https://dapp.d-bis.org — production behind NPMplus
   • http://192.168.11.58 — direct LXC (VMID 5801) for testing
   • Add http://localhost:5173 (or your dev URL) if you use Vite dev locally.
4. Save. Changes usually apply immediately.

After adding origins

• Reload the DApp in the browser; the “Project ID Not Configured” / “Failed to fetch remote project configuration… 403” errors should stop if the built bundle already contains the correct project ID (see frontend-dapp/.env and .env.local and rebuild/redeploy if needed).

Optional: NPMplus and SSL

From a host on the same LAN as NPMplus (192.168.11.167:81), you can ensure the proxy and SSL are in place:

# From repo root, with NPM_PASSWORD set (e.g. in .env)
source .env && bash scripts/nginx-proxy-manager/complete-dapp-npmplus-from-lan.sh

Then in the NPMplus UI, open the proxy for dapp.d-bis.org, request SSL, and enable Force SSL.

References

• Reown App Kit: https://reown.com/appkit
• Env used in this repo: VITE_WALLETCONNECT_PROJECT_ID in smom-dbis-138/.env and smom-dbis-138/frontend-dapp/.env (and .env.local; .env.local overrides .env at build time).