Allow Vismo on Your Network - Vismo Help Centre

If Vismo opens but files won’t load, maps stay blank, uploads fail or icons show as text, a company firewall, proxy or web filter may be blocking part of it. Give your IT team the lists below. All of them are HTTPS addresses.

Domains to allow

Step 1: Vismo itself

Allow vismo.io and *.vismo.io. That covers the app (app.vismo.io), the sign-in pages (id.vismo.io), the data service (api.vismo.io) and the other Vismo services the app talks to.

If this one is blocked, you can’t sign in or open projects at all. For emailed links that won’t open, see Having Trouble Accessing Vismo?.

Step 2: File storage

Allow wasabisys.com and *.wasabisys.com. Vismo’s file storage is provided by Wasabi, and your browser sends uploads to it and loads downloads, thumbnails and previews from it directly.

If only this one is blocked, the project pages load and the file list appears, but files won’t open, thumbnails are blank, or uploads fail.

Step 3: Maps

Allow all four of these for the project map and map backgrounds:

api.mapbox.com for satellite and street imagery
tile.openstreetmap.org for the OpenStreetMap background
tiles.openfreemap.org for the place labels shown over satellite imagery
s3.amazonaws.com for the 3D terrain tiles. If it is blocked, the ground in 3D views is drawn flat

Step 4: Fonts and icons

Allow fonts.googleapis.com and fonts.gstatic.com. Without them the text uses a plain font and icons can show as words.

Optional

Vismo works without these. They only power the “what’s new” and ideas widgets:

frill.co and *.frill.co
frill-prod-app.b-cdn.net

Still stuck?

If your IT team has allowed everything above and something still fails, email support@vismo.io with what you were trying to do, the project and file involved, and any blocked address your IT team saw in their logs. See also Report a Problem.