Assets only accessible locally

This situation is common when the assets are only accessible on your local VPN and not publicly accessible.

As Percy re-renders the DOM in a browser outside of your test suite, you may need to instruct the SDK to capture remote assets. This ensures they are available locally to Percy when rendering a screenshot.

By default, the SDK captures all assets served on the same hostname as where the tests were running. For example, the tests are run on percy.io, all assets with the percy.io hostname are saved locally. Assets served from cdn-example.percy.io will not be captured unless that hostname is added to the [allowed-hostnames] config(/docs/percy/take-percy-snapshots overview#all-configuration-options).

Reference Topic

• Percy Common - FAQs