Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author Peter Booker

    (@peterbooker)

    Hi megan_buzzhoney,

    Sorry you have had problems since the server switch. It was far more rushed than I would have liked and I am still trying to iron out issues.

    Is your website being run from inside a work/company network? Could it be possible a firewall is blocking the new IP address?

    I had a look at the server logs and I cannot see any refused connections made by my server.

    The major difference since I switched the API server is that the IP address changed, it is now: 23.239.13.127

    I will try to get an update out tonight which will show on the settings page if the plugin can connect to our API server properly or not.

    Thread Starter megan_buzzhoney

    (@megan_buzzhoney)

    Thanks Peter. I don’t think our server is doing anything. It’s on an VPS. I will be waiting for your update. Hope that helps!

    Plugin Author Peter Booker

    (@peterbooker)

    Hi megan_buzzhoney,

    Sorry for the slow response. It took me much longer than expected to add Server Status and Tweet Data Debug tools to the plugin.

    Relevant to you in the new version (1.4.6) is the box in the top right corner of the plugin’s settings page. Shortly after the page loads this will turn either green (for success) or red (for failure). This tests whether or not your website can successfully make a connection to the API server.

    I have a feeling this will likely turn red. If so (or if it turns green) can you also click on the link ‘Debug Tweet Data’ at the far bottom of the plugin’s settings page. Once the loading circle has gone, is there anything in the box at all. Ideally it should be oddly encoded text (which is your Tweet data).

    Let me know what you find.

    Thread Starter megan_buzzhoney

    (@megan_buzzhoney)

    Hi Peter,

    Thanks a lot for the new version! I just updated. The status box is green showing:
    API Status
    23.239.13.127 Success.

    But clicking Debug Tweet Data gives me “Sorry, no Tweet data was found.”

    Thanks,
    Megan

    Plugin Author Peter Booker

    (@peterbooker)

    Hi megan_buzzhoney,

    Thank you very much for letting me know. This is the first instance I have seen where someone can connect to the API fine but the Debug Tweet Data link fails to find any cached data. “Sorry, no Tweet data was found.” means that there was no transient with Tweet Data, which is rather odd.

    This may help me to track down what is happening, I will use this to follow up on some ideas. Thank you again for helping me to debug the problems. I really want to get them resolved so you can all use the plugin without issues.

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

The topic ‘Connection refused’ is closed to new replies.