Can't Proceed - API Error: (#5)

Andy,
Ugghh. For Autotune, it looks like you changed your password as your subscriber ID is different than it used to be. If you didn't change your password, or aren't seeing a subscriber ID that starts with '1bb', let me know.. then something is wrong..

As for the app not working, can you try the following App ID and Secret Key? Shouldn't make any difference, but since it's not created by you, maybe it will. If it does work, we can transfer the app to you (and change the secret key). Can't imagine it's something with you as the creator, but it's a best guess.
API Key: 211307415621504
Secret Key: b0bcd692ba4ed7835bbc9f6d8a548caa

I did some looking into your new IP address. Couldn't find any reports of issues for spam or other problems. Also, from a quick check, it doesn't look like any previous sites on there should have been 'bad'. It all makes me thing something really fishy is going on. Hopefully the API key above helps...

Thanks, and good luck,
Alex

Andrew,
I hate to say it, but I just don't think there's anything we can do then. With JFBConnect code, there's only so much we can do. This is definitely an issue on Facebook's end where they aren't liking the IP addresses from your hosting provider. That's something that we simply can't work around, and would need to be fixed by Facebook itself. Since the API/Secret key work from your local computer, it's an indicator that it's likely just the IPs of your host that are causing this. The only other option I can think of is switching hosts. That's not something I want to recommend though as that can take a bit of work, and I can't guarantee that will fix things either.

I'm not sure if you contacted Facebook, but hopefully you can get some information from them. With JFBConnect, we do have a 30-day money back guarantee and would have no problem refunding your purchase. I'd love to give you a better solution, but unfortunately, I've exhausted all other ideas that I can come up with.

Finally, if you do decide to continue with JFBConnect, we can gladly look more into your Aututone issues. I'm unsure what is causing your subscirption ID to fail, but I'm sure we can get to the bottom of those issues since we fully control that system.. though we haven't heard of them either.

Very sorry for the issues. Just let us know how you'd like us to proceed.

Alex

Andrew,
Just got an alert about your post on Stack Overflow ( here ).

One thing I noticed from that post was:

You may want to make sure the server IP is whitelisted, as well...

If, when you got the dedicated IP address for the SSL cert, that didn't change your server IP address, then nothing really changed. As your host mentioned, the server IP is where all requests are made to Facebook. Since you're getting the blocked message when making server calls, that's the IP address that is being blocked by Facebook. You'd need to get the server IP address changed.

Many times, when you get a dedicated IP address for an SSL, that changes the server IP address.. but not always. It depends on the hosting method (shared, VPS, dedicated). The further 'right' you go in that list, the easier it is to get a new server IP address.

I had originally tried to do a reverse IP lookup on your site's public IP address, which didn't lead to much. A reverse lookup will tell how many sites are using that IP address. The more sites, the greater the chance that one is causing the block. However, for your server IP address, that shows that a lot of sites are hosted on that server:
www.yougetsignal.com/tools/web-sites-on-web-server/ (lists 300+)
domaintz.com/tools/overview/50.22.11.11 (lists 1300+)
www.domaintools.com/research/reverse-ip/ (lists 1500+)

The reports are never perfect as they have to scan logs to gather it, but they give a good rough approximation of few, some, or lots. In your case, your server definitely hosts "lots" of other sites.. any of which could be causing the block for the IP address.

There's not much you'll be able to do about that, and again, it's something you'd need to take up with your host. Ideally, you'd be able to either:
* Get your host to move your site to another server they own. It may still have 'lots' of sites hosted on that server, but hopefully, none of them is causing a block from FB.
* Get Facebook to tell you what site it is that's causing the block so you can relay that to your host, have them booted from the server, and hopefully get the block removed.

Hope that helps, and sorry again for the troubles,
Alex

Andy,
Fantastic! Not sure if you started that process before my post, or if my post lit a bulb for you.. either way though, very excited to hear it's moving along now!

Should you need anything else, just let us know.. and good luck!

Alex