URL Proxy and Image Mirroring

Route data-source image fetches through a proxy to reach sources that block the ConnectWyze render servers, and cache a copy in your workspace storage for faster, more reliable renders.

What it is

Some image CDNs block requests from cloud server IPs. When ConnectWyze tries to fetch a data-source image for rendering and gets a 403 response, it can automatically retry through a proxy. In addition, the Image Mirror feature downloads image URLs from your data source and stores them in your workspace storage, so renders always use a stable, ConnectWyze-hosted copy rather than the original source.

Both features operate per data source and activate transparently during data-source syncs and renders.

When you'd use it

Your data source contains image URLs hosted on a CDN that blocks cloud server requests with 403 errors.
Feed syncs succeed but rendered images are missing or broken.
You want renders to be faster and more resilient by pre-caching images from the source instead of fetching them at render time.
You are migrating a large data source and need images available in your own workspace storage.

Quick start (user)

Enable image mirroring on a data source

Open the data source in Dashboard → Data Sources or while creating a new data source.
Scroll to the Image Mirror section in the data source settings.
Turn on the Mirror Images toggle.
Select which URL fields to mirror, or leave the list empty to let ConnectWyze auto-detect image fields.
Save the data source. On the next sync, ConnectWyze downloads each image URL and uploads a copy to your workspace storage.

Automatic proxy fallback

The proxy activates automatically. If a data-source sync or data-source test returns a 403 from the source API, ConnectWyze retries through the proxy and marks the data source to use the proxy for all future syncs. You can confirm this is active by opening the data source form — a notice appears below the Image Mirror section when the proxy is in use.

You do not need to configure anything for the automatic fallback to work.

Settings reference

Feed — Image Mirror settings

Setting	Default	Description
Mirror Images	Off (On for new data sources)	Download image URLs from this data source and store them in workspace storage on each sync.
Image Fields	Auto-detected	Which URL fields to mirror. Leave empty to mirror all detected image fields. If fields are manually specified, only those fields are mirrored.

Proxy status (read-only)

Indicator	Description
"Source API is being fetched through the proxy"	ConnectWyze detected a 403 from the source on a previous sync and enabled the proxy automatically for this data source.

How mirroring works

On each sync, ConnectWyze checks whether a mirrored copy already exists for each image URL (by content hash). If a matching copy is found, no new download or upload is performed. Only new or changed images consume bandwidth and storage.

Mirrored images are stored in your workspace storage provider. If your workspace uses a custom storage provider, mirrored images go there. Usage counts toward your workspace storage quota.

Troubleshooting

Symptom	Fix
Rendered images are broken but the data-source sync completes	Enable Mirror Images on the data source. The render worker may be unable to reach the source CDN at render time.
Feed sync shows 403 errors in logs	The proxy activates automatically on the first 403. If errors persist after one retry, contact [email protected].
Mirrored images are not updating after source changes	ConnectWyze deduplicates by content hash. If the source URL changes but content is the same, the cached copy is reused. If the URL is the same but content changed, trigger a manual sync.
Image fields are not being mirrored	Open the data source form and check the Image Fields list. If fields are manually specified, the auto-detection is skipped — add the correct field names.
Storage quota increasing unexpectedly	Each new unique image URL adds to storage. Remove unused feeds or contact support to review your storage usage.