Fixing “Content not viewable in your region” (Imgur Geoblock) During Influitive Join / Sign-Up for UK Users

Solution

Issue / Symptom

UK users attempting to access an Influitive join link or sign-up page see an Imgur block page with the error:

"Content not viewable in your region"

This often appears as an Imgur-branded placeholder/image during the join/sign-up experience.

What this is (and what it is not)

• Not an Influitive join-code geographic restriction.
• Is a third-party content access issue: the page is attempting to load an Imgur-hosted asset, and Imgur is blocked in the UK.

Common impact

• The join/sign-up page appears broken or partially broken for UK users.
• The join link may still function, but the blocked asset can confuse users or interfere with client-side “embedded” experiences that depend on that content rendering.
• Users may believe the join link is broken if they don’t immediately see their name appear; validate by completing a test registration and confirming the user appears in the hub’s user list/member view.

Troubleshooting and investigation

1) Confirm the join link itself works

1. Open the join link:

   https://your_instance.domain.com/join/<join_slug>

2. Confirm it redirects/loads the sign-up flow:

   https://your_instance.domain.com/users/sign_up?join-code=<join_code>

3. If the page loads but the Imgur block message appears, continue below.

2) Reproduce from a UK network path

1. Test from a UK ISP or via a UK VPN.
2. Perform a hard refresh to eliminate cached assets:
   • Windows/Linux: Ctrl+F5
   • macOS: Cmd+Shift+R
3. Note whether the Imgur block message appears only after the hard refresh. This can indicate cached/conditional loading and can help pinpoint a client-side reference.

3) Identify where Imgur is referenced

Check for any references to Imgur in:

• Custom JS configured on the hub (a common culprit)
• Injected scripts, theme customizations, or embedded widgets used on the sign-up/join flow

Quick ways to confirm:

• Search Custom JS for imgur.com or i.imgur.com.
• Use browser DevTools → Network tab, reload the sign-up page, then filter requests for imgur.

Root cause

A direct Imgur URL (for example: <imgur_url>) was present in the hub’s Custom JS and used in sign-up/join page image logic (notably tied to “under 18” / sign-up image behavior). When UK users loaded the join/sign-up page, the browser attempted to fetch the Imgur asset and received Imgur’s UK geoblock response, resulting in "Content not viewable in your region".

Remediation options

Option A (recommended): Replace Imgur with a UK-accessible host

1. Upload the image to a host accessible in the UK (or your organization’s approved CDN).
   • Example: a UK-accessible image host (e.g., Postimage) or your own CDN.
2. Update the hub’s Custom JS to replace any Imgur references such as:

   https://imgur.com/<image_id>
   https://i.imgur.com/<image_id>.png

   …with your new image URL, for example:

   https://<new_image_host>/<path_to_image>

3. Save changes and publish/activate the updated customization.

Option B (temporary mitigation): Point to an Influitive-hosted image

1. Replace the Imgur URL in Custom JS with an image URL hosted within Influitive-managed storage.
2. Confirm the replacement image content is acceptable (temporary images may not match the original messaging exactly).
3. Plan a follow-up to host the final asset in a stable, UK-accessible location if needed.

Optional improvement: Decouple “under 18” messaging from an image

If the “under 18” requirement is intended as a text/link element, implement it as HTML (or a configurable page element) rather than baking it into a single image. This reduces dependency on any single image host and helps prevent regional image blocking from disrupting the join flow.

Follow-up adjustment: If you provide a different hosted image URL that is accessible in the UK, update Custom JS again to point to that new asset.