• Resolved audioscapist

    (@audioscapist)


    I’ve been trying to setup Revive To Sky on my site for a few days now but have never managed to get a connection. Test connection gives me “Error: Rate Limit Exceeded” – I am definitely using a Bluesky App Password, and have connected successfully through the Jetpack social plugin. I have tried new passwords, and have left it over 24 hours before trying again. Is there anything else someone might suggest?

    Thanks

    • This topic was modified 3 months, 1 week ago by audioscapist.

    The page I need help with: [log in to see the link]

Viewing 12 replies - 1 through 12 (of 12 total)
  • Plugin Author Rhys Wynne

    (@rhyswynne)

    Are you connected via a VPN or a shared connection? The rate limit is quite high, but not unbreakable (300 per account/30 in a 5 minute connection). If you are, disconnect and try again.

    To the best of my knowledge, I don’t think it would affect the plugin from posting, only for testing the connection, so maybe set it up and see if it does actually post.

    I’m working on a fix for the test connection button, hopefully it’ll be pushed out over the next few weeks all being well.

    Thread Starter audioscapist

    (@audioscapist)

    Thanks for the response Rhys. It’s not posting, and I’m not connected via VPN or a shared network. I tried disconnecting anyhow butb no dice. I’ll try again in a few days. Thanks

    Plugin Author Rhys Wynne

    (@rhyswynne)

    Okay, that’s confusing, as something is tripping up your server from posting. What it is I’m not sure.

    Could you try the following (you may need to leave it a few hours between tasks):-

    1. Disable (for now) the Jetpack sharing, see if that works.
    2. Create a new key for only for Revive to Sky – don’t test, just save for now with how you want it set up.

    Do you know how to access log files? That could give some more clues.

    Thread Starter audioscapist

    (@audioscapist)

    Tried again today and it now says “Error: Invalid identifier or password”. Checked those and they are correct.

    Done no.1 – no difference

    Done no. 2

    Log files? Possibly not but I’ve just installed wp debugging and found the debug.log. No mention on Revive To Sky

    Plugin Author Rhys Wynne

    (@rhyswynne)

    Okay. I’m not sure about that but found a Github thread and there was seemingly problems about it – https://github.com/bluesky-social/social-app/issues/4961. So maybe they will right themselves?

    You may need to switch on WP DEBUG to get some Revive to Sky messages, here’s how to do that. It should then start writing to the debug.log.

    Be sure to switch it off after it’s done! I’m not sure if that plugin will switch WP DEBUG on or off.

    Thread Starter audioscapist

    (@audioscapist)

    Interesting and thanks for the useful information. The plugin I’ve installed does make changes to the wp-config.php file, both on and off, I’ve checked by viewing the wp-config.php file itself so that’s good to know. See below for what appears when I try the Revive To Sky connection if that’s of use. It hasn’t posted anything but I did mange to share a post using the Jetpack share button. I’m using a custom child theme that I messed around with ages ago without knowing what I was doing (and still don’t), so it’s very possible that I broke something…

    [18-Jan-2026 15:58:56 UTC] Revive to Sky: Running cron event
    [18-Jan-2026 15:58:56 UTC] Revive to Sky: Post to bluesky with title funk and the like.
    [18-Jan-2026 15:58:56 UTC] Revive to Sky: Skeet: vibes from the head: funk and the like - https://audioscapist.net/jazz-funk/funk-and-the-like/
    [18-Jan-2026 15:58:56 UTC] Revive to Sky: Hashtags: Array
    (
    )

    [18-Jan-2026 15:58:56 UTC] Revive to Sky: Mentions: Array
    (
    )

    [18-Jan-2026 15:58:56 UTC] Revive to Sky: Links: Array
    (
    [0] => Array
    (
    [start] => 41
    [end] => 94
    [url] => https://audioscapist.net/jazz-funk/funk-and-the-like/
    )

    )
    Plugin Author Rhys Wynne

    (@rhyswynne)

    Hi There,

    I’ve pushed version 1.1.1, which connects via the server (rather than your browser), and also includes more debug information. Could you upgrade and try again?

    Thread Starter audioscapist

    (@audioscapist)

    Got “Rate limit exceeded. Please wait 30–60 minutes before trying again” when testing connection and the debug log gave the below,

    Thanks

    [20-Jan-2026 19:36:09 UTC] Revive to Sky: Test Connection Response: Array
    (
    [headers] => WpOrg\Requests\Utility\CaseInsensitiveDictionary Object
    (
    [data:protected] => Array
    (
    [date] => Tue, 20 Jan 2026 19:36:09 GMT
    [content-type] => application/json; charset=utf-8
    [content-length] => 61
    [x-powered-by] => Express
    [access-control-allow-origin] => *
    [ratelimit-limit] => 10
    [ratelimit-remaining] => 0
    [ratelimit-reset] => 1768939808
    [ratelimit-policy] => 10;w=86400
    [etag] => W/"3d-egyFOcXCrKQFzoI7522/4+PpxIk"
    [vary] => Accept-Encoding
    )

    )

    [body] => {"error":"RateLimitExceeded","message":"Rate Limit Exceeded"}
    [response] => Array
    (
    [code] => 429
    [message] => Too Many Requests
    )

    [cookies] => Array
    (
    )

    [filename] =>
    [http_response] => WP_HTTP_Requests_Response Object
    (
    [data] =>
    [headers] =>
    [status] =>
    [response:protected] => WpOrg\Requests\Response Object
    (
    [body] => {"error":"RateLimitExceeded","message":"Rate Limit Exceeded"}
    [raw] => HTTP/1.1 429 Too Many Requests
    Date: Tue, 20 Jan 2026 19:36:09 GMT
    Content-Type: application/json; charset=utf-8
    Content-Length: 61
    Connection: close
    X-Powered-By: Express
    Access-Control-Allow-Origin: *
    RateLimit-Limit: 10
    RateLimit-Remaining: 0
    RateLimit-Reset: 1768939808
    RateLimit-Policy: 10;w=86400
    ETag: W/"3d-egyFOcXCrKQFzoI7522/4+PpxIk"
    Vary: Accept-Encoding

    {"error":"RateLimitExceeded","message":"Rate Limit Exceeded"}
    [headers] => WpOrg\Requests\Response\Headers Object
    (
    [data:protected] => Array
    (
    [date] => Array
    (
    [0] => Tue, 20 Jan 2026 19:36:09 GMT
    )

    [content-type] => Array
    (
    [0] => application/json; charset=utf-8
    )

    [content-length] => Array
    (
    [0] => 61
    )

    [x-powered-by] => Array
    (
    [0] => Express
    )

    [access-control-allow-origin] => Array
    (
    [0] => *
    )

    [ratelimit-limit] => Array
    (
    [0] => 10
    )

    [ratelimit-remaining] => Array
    (
    [0] => 0
    )

    [ratelimit-reset] => Array
    (
    [0] => 1768939808
    )

    [ratelimit-policy] => Array
    (
    [0] => 10;w=86400
    )

    [etag] => Array
    (
    [0] => W/"3d-egyFOcXCrKQFzoI7522/4+PpxIk"
    )

    [vary] => Array
    (
    [0] => Accept-Encoding
    )

    )

    )

    [status_code] => 429
    [protocol_version] => 1.1
    [success] =>
    [redirects] => 0
    [url] => https://bsky.social/xrpc/com.atproto.server.createSession
    [history] => Array
    (
    )

    [cookies] => WpOrg\Requests\Cookie\Jar Object
    (
    [cookies:protected] => Array
    (
    )

    )

    )

    [filename:protected] =>
    )

    )
    Plugin Author Rhys Wynne

    (@rhyswynne)

    Hi There,

    Hmmm…okay, I’m running out of ideas. Could you potentially try the following:-

    A clue is in one of the header.

    RateLimit-Reset: 1768939808

    This is a Unix timestamp. So put it into here – https://www.unixtimestamp.com – and it’ll tell you when the rate limit reset.

    Right now, the only things I can suggest are the following:-

    • Switch off all plugins and switch to a default theme, and try again.
    • Speak with your host, say you’re getting this.
    • If you are comfortable, you can run WordPress on a different server. You can set up a local instance that runs WordPress. Run a default instance but just the Revive to Sky plugin. You can use a program like https://localwp.com to run it
    • Set up a separate bluesky account with a different app password.

    That may give us clues as to what’s happening.

    Thread Starter audioscapist

    (@audioscapist)

    Thanks Rhys, I’ll try what you recommend

    Plugin Author Rhys Wynne

    (@rhyswynne)

    I’m assuming this is fixed so marking this as complete.

    Thread Starter audioscapist

    (@audioscapist)

    Hi Rhys, sorry I should have said. Not fixed on my setup but I’m going to update my theme soon as the one I’m on is pretty ancient, and I think it’s likely to be the problem, but many thanks for your help.

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

You must be logged in to reply to this topic.