Topic-icon Autotune and get this error

Active Subscriptions:

None
13 years 5 months ago #29305 by alaqua
Hi,

I was setting up autotune and i got these errors



getFieldList - Error: Could not communicate with SourceCoast.com to fetch up-to-date information.
getAuthorization - Error: Could not communicate with SourceCoast.com to fetch up-to-date information.

Could not fetch application and recommendation data from SourceCoast.com. Cached values were loaded, but may be out of date.
It's highly recommended that you make a successful connection to get the most up to date application data and recommendations.

basic check had both passed

other check:

JFBConnect Remote Error Check
Checks performed on: sglaunchreview.com/

Test: JFBCSystem plugin is enabled
Pass
Test: Facebook Javascript library inclusion
Pass
Test: Checking Facebook locale setting
Pass
Test: Checking for known-conflicting extensions
Pass

Please help
Thanks
The topic has been locked.
Support Specialist
13 years 5 months ago #29313 by alzander
Alan,
That error usually occurs from either of the following scenarios:
* Your server has a firewall setup that isn't allowing outgoing connections to our server to fetch the right information. You'll need to make sure your server can send out requests to sourcecoast.com and facebook.com
* cURL is not properly configured on your server. Our "Basic Info" page of Autotune should check if cURL is enabled. If that shows it's enabled, that's likely not the problem, but there are still cases where it doesn't work right.

Hope that helps get you started. There's not much we can do on our end of things, so you may need to contact your hosting provider to check the above.

Please let us know if you have any questions or need further assistance,
Alex
The topic has been locked.
Active Subscriptions:

None
13 years 5 months ago #29397 by alaqua
Replied by alaqua on topic Autotune and get this error
Hi, I had contacted my hosting company this is the conversation that we had:

me: hi one of the script i bought requires me to do this => Your server indicates that Live Update is not supported. Please contact your host and ask them to enable the cURL PHP extension or activate the URL fopen() wrappers. If these are already enabled, please ask them to configure their firewall so that it allows access to the following URL: www.sourcecoast.com/updates/jfbconnect.ini
Just a moment...
Chan: Hello
me: hi
need some technical help*
Chan: hold on please
me: ok
Chan: let me read your query
me: ok
Chan: Hello
let me know your domain name please
me: i have 2...
rparc.net
and sglaunchreview.com
Chan: ok hold on please
me: ok
Chan: PHP curl and fopen already enabled in our servers
me: ok
can the server ping the required site?
www.sourcecoast.com/updates/jfbconnect.ini
Chan: Not able to ping to the site sourcecoast.com
ask them to open firewall from their end
or give our server IP to whitelist
me: ok able to provide the details?
Chan: rparc.net --> 103.9.101.121 sglaunchreview.com --> 103.9.101.71

What else do i need to do. I cannot auto update now
The topic has been locked.
Active Subscriptions:

None
13 years 5 months ago #29399 by alaqua
Replied by alaqua on topic Autotune and get this error
I have this error when trying to update.

Update: :Extension: Could not open www.sourcecoast.com/updates/jfbconnect.xml
The topic has been locked.
Support Specialist
13 years 5 months ago #29406 by alzander
Alan,
Something's not adding up correctly. We don't have restrictions on the IPs that can access our server unless your hosting company is on large, well-known blacklists (I doubt that's the case).

Can you let me know if the JFBConnect Overview page is showing version information about what's available for our extensions? If so, that's making a connection to sourcecoast.com as well (and obviously working).

The error message you're seeing in the Joomla updater is something we're looking into, but something all users are seeing, not just you.

Keep us posted. This is not a common issue and we'd like to resolve it, but it's not as easy as entering your IP in on our end as I don't think you're really being blocked.

Thanks,
Alex
The topic has been locked.