Kebo Behind Corporate Proxy/Firewall

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

    (@peterbooker)

    Hi muffintop,

    The IP address of the API the plugin uses for most of the oAuth processing is: 89.200.139.16

    This is going to change in the future, but it will be visible on the plugin settings page from that point on and show a visible warning if it cannot connect.

    The plugin has had many reports of issues from users behind corporate firewalls/proxies. When connecting the plugin to a Twitter account, once you have logged in and given permission, you are forwarded back to us and the relevant information from Twitter has been stripped. Unfortunately, I have not found a way in which I can resolve this.

    If you have any problems/questions, let me know.

    Thread Starter muffintop

    (@muffintop)

    Hi Peter,

    Thanks for the response. yes I manged to come across the IP and had it added to our firewall – all works a treat now!

    Much Appreciated!

    Plugin Author Peter Booker

    (@peterbooker)

    Hi muffintop,

    That is great news, thanks for letting me know!

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Kebo Behind Corporate Proxy/Firewall’ is closed to new replies.

Tags