• Resolved jmsilles

    (@jmsilles)


    Good afternoon, appreciate any help you can offer here –we’ve exhausted all of our options and need a little insight. Simple version: Instagram feed stopped updating, followed the typical approach (clear cache, reconnect, etc). When trying to reconnect, the process would just sit there for hours on the callback to the website. So we started to investigate, and now I’m here 🙂

    Prior to this point:
    – Disabled security plugins, cleared server cache, tried to reconnect, hangs on “connecting”; disabled browser plugins, disconnected in the Instagram account, etc. Never gets past “connecting”
    – Tested with a different instagram account, no issues
    – Tested with a different plugin for feeds, WORKED with the account we have an issue with
    – Tested again with the same account with Spotlight, hangs
    – Tested on two different computers, two different internet connections, hangs
    – Tested with the main connection approach and tested via the create a token approach; no change
    – No errors in the network tab or console log

    On a test site:
    – Deleted the feeds, account, deleted the plugin, cleared the DB of all references to Spotlight, cleared server cache, disabled security plugins
    – On the Instagram account, removed website/application access; checked all notifications, security settings, etc for any warnings, alerts, “is this you?” etc.
    – Attempt to connect fresh, same outcome
    – Again, it shows up in Instagram as connected, but the Spotlight popup will sit for hours on “connecting”
    – I tried again with the “create a token” method instead and did a video recording and caught something
    — There’s a brief-brief moment from when you click “allow” where the console shows “Error with Permissions-Policy header: Unrecognized feature: ‘attribution-reporting”, and Error with Permissions-Policy header: Unrecognized feature: ‘shared-storage’ and Error with Permissions-Policy header: Unrecognized feature: ‘shared-storage-select-url’ and “The Content Security Policy directive ‘upgrade-insecure-requests’ is ignored when delivered in a report-only policy.”
    – After that, the popup goes to the “connecting” screen and just stays there

    If it helps: This Instagram account is a business account (double checked) and it’s an 18+ account because it has alcohol. That was our first guess as to the issue, but apparently it’s been setup for months without an issue and other social feed products (that we don’t like as much) don’t have the issue. So we’re stumped.

    Appreciate any help you can provide. Thank you!

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Support Hendra Setiawan

    (@hendcorp)

    Hi @jmsilles

    Thanks for the thorough write-up, it made this much easier to look into.

    The “connecting” screen you’re stuck on comes from our connection server, at the step where it receives Instagram’s approval. That happens before anything is sent to your website, which is why the Access Token Generator stalls in the same place. So your site, security plugins, cache and browsers aren’t the cause, and the console messages come from Instagram’s own page and are harmless.

    Your test with the other plugin is a useful one: it shows the account itself isn’t blocked from the API. We’ve seen a similar stall with a couple of other age-restricted business accounts, so your 18+ guess may well be connected, but we’d like to narrow it down before drawing conclusions.

    Could you help with two things?

    1. From your description, it sounds like you used the Basic (Connect via Instagram) option. Could you confirm?
    2. If you haven’t tried it yet, please try Advanced (Connect via Facebook) under Instagram Feeds > Settings > Accounts. It works for Business accounts linked to a Facebook Page and connects through Facebook instead of the Instagram login.

    Please let us know what you find, and we’ll take it from there.

    Plugin Support Hendra Setiawan

    (@hendcorp)

    Hi @jmsilles

    Since we haven’t heard back in a while, I’ll mark this topic as resolved for now.

    If you’re still stuck on the “connecting” screen, just reply here and let us know which connection option you used and whether Advanced (Connect via Facebook) worked for you. We’ll pick it back up from there.

Viewing 2 replies - 1 through 2 (of 2 total)

You must be logged in to reply to this topic.