Skip to main content
Exhibit home page

Troubleshooting

If something isn't working as expected, check the sections below for the fastest fix.

Importing IIIF manifests

A IIIF manifest URL won't load or shows an error

  1. Check that the URL points to the JSON manifest, not the catalogue web page. A IIIF manifest URL usually ends in /manifest, /manifest.json, or index.json and returns JSON data when opened in a browser tab (see Using IIIF with Exhibit).
  2. Check for CORS restrictions. Because Exhibit loads IIIF manifests directly in your browser, the hosting institution's server must allow Cross-Origin Resource Sharing (Access-Control-Allow-Origin: *). You can test a manifest URL at test-cors.org: if Send Request returns XHR status: 0, CORS is blocked on the institution's server; if it returns XHR status: 200, CORS is configured properly.
  3. Check for automated bot challenges. Some institutional repositories place Cloudflare Turnstile or Anubis bot-challenge screens in front of their IIIF endpoints, which block web applications from fetching the manifest JSON.

Audio, video, and embedding

Audio or video doesn't play with sound automatically

Modern web browsers block unmuted autoplay until the visitor has clicked or tapped the page. Turn on Enable Landing Page in Settings so visitors click Start Exhibit (or Start in Kiosk) before reaching your audio or video clip, or click the speaker button in the viewer controls to unmute sound.

My embedded exhibit doesn't show up in WordPress or a VLE

  • Make sure you copied the full <iframe ...></iframe> code from the Share panel (see Save, Share, and Embed).
  • In WordPress, raw <iframe> tags are stripped unless your site administrator enables them or installs the WordPress iframe plugin using [iframe ...] shortcode syntax.