Connection to Bluesky not working

[podcastingtoday]

I've received this message three times today - "Your authorization has expired. Please reconnect your account in the Blog2Social network settings." I've reconnected each time but the problem continues.

[Blog2Social Support]

Hi,

Thank you for reporting this.

The error message
"Your authorization has expired. Please reconnect your account in the Blog2Social network settings."
indicates that the connection between Blog2Social and your Bluesky account is being invalidated shortly after reconnection. Please try the following steps:

1. Disconnect Bluesky in your Blog2Social network settings completely.
2. Clear your browser cache and make sure you're logged into the correct Bluesky account in the same browser.
3. Reconnect Bluesky via Blog2Social in a new browser tab or private/incognito window.

If the problem persists, please let us know:

• Which browser you're using
• Whether you're using any security or privacy plugins
• If this happens immediately after reconnecting, or only after posting
• Pleas also make sure, that you are using the latest version of Blog2Social

We'll be happy to take a closer look and support you further.

Best regards,
Philippe

[podcastingtoday]

I've followed your instructions and it hasn't rectified the problem. I'm using Chrome, have the Wordfence plugin and the Bluesky connection shows as connected but when I post says "Connection is interrupted since 2025-06-04" and still looks connected.

[Blog2Social Support]

Hi podcastingtoday ,

Thank you for your feedback and the additional information.

We’ve tested the Bluesky connection on several demo pages and posting is still working as expected. To help narrow down the issue, please make sure the following steps are followed correctly:

1. Check your Bluesky handle:
   When connecting your Bluesky account in Blog2Social, make sure you enter your full Bluesky handle in the format of a domain name (e.g., yourname.bsky.social).
   This handle is needed to identify your correct authorization server. You’ll find it in your Bluesky profile, right after your username.
2. Use private/incognito mode:
   Open Blog2Social in a new incognito/private browser window and reconnect your Bluesky account there. This ensures no cached sessions interfere.
3. Check security plugins like Wordfence:
   Wordfence or other privacy/security plugins may block or modify requests. Please try temporarily deactivating Wordfence or add Blog2Social to its whitelist/exclusion list, and then try reconnecting.

If the issue persists:

• Let us know when exactly the connection status changes to “interrupted” — is it right after reconnecting, or only when trying to publish a post?

We’ll be happy to further investigate and assist you.

Best regards,
Philippe – Blog2Social Support

[podcastingtoday]

I've followed all of the further instructions and it hasn't fixed it - Bluesky shows that it's connected but if I go into a post to send via Blog2Social, I get this message - "The scheduling for your social media post has changed as a selected social media network is no longer connected to Blog2Social. Please check the network connections under "Networks" and make sure that the required networks are connected." Then the post is only sent to the other connected networks and Bluesky is then showing as disrupted.

If I try to send a new post - all networks (including Bluesky) show in the preview, but when I send, Bluesky doesn't work and it's interupted again.

[Blog2Social Support]

Hi podcastingtoday ,

Thank you very much for your detailed feedback and for following all the troubleshooting steps.

As of our latest internal tests, Bluesky connections remain stable on our demo instances. To help us further narrow down the cause, could you kindly check the following additional points?

---

Additional questions for further analysis:

1. Has this Bluesky account ever successfully published a post via Blog2Social before?
   Or is this the first time you’re trying to use it?
2. Can you test with a second Bluesky account (if available) to see whether the issue is limited to one specific account?
3. Does manual posting to Bluesky (outside of Blog2Social) work without problems from the same browser and network?
4. Are there any redirects or proxies (e.g., Cloudflare or security layers) used on your WordPress site that might interfere with outgoing API requests?

---

It seems the connection is being accepted by Bluesky but then invalidated when a post is being sent. This might point to an issue with the authorization token or the request payload. Since the problem doesn't currently occur on our test environments, your case could help us identify a specific condition or conflict.

We really appreciate your help and will be happy to continue troubleshooting with you!

Best regards
Philippe

[podcastingtoday]

To answer your questions -
I have been publishing to Bluesky with this account via Blog2Social since you added it to the plugin and it has been fine up until now.
I Don't have an alt Bluesky account to test.
Manual posting to Bluesky outside Bog2Social works fine from same browser and network
I am using Quic.Cloud CDN but have been for a long time.
There are no other changes I have made such as other plugins.

[Blog2Social Support]

Hi podcastingtoday ,

Thank you very much for your thorough response and clarification.

Since the issue does not occur on our test systems and your setup has worked reliably in the past, the problem may be linked to something specific in your environment (such as the CDN layer or a plugin conflict). We would be happy to continue investigating this with you directly.

To proceed:

1. Please contact our support team directly via email (customer-service@blog2social.com) or private message.
2. Within Blog2Social, you can download a diagnostic troubleshooting .txt file from the support settings. Please send us this file — it will help us better understand your server environment and pinpoint possible issues.
3. If needed, we would be happy to coordinate a secure temporary access method (e.g., staging or test credentials) to verify the behavior directly within your setup.

We’re committed to resolving this with you — thank you again for your cooperation and patience!

Best regards,
Philippe

[podcastingtoday]

Thanks - I've emailed the txt file for you to look at.