Log in | Register
  1. Forum
  3. Discontinued Products
  5. JFBConnect v8.x Support (Joomla 3 Only) (CLOSED)
  7. We could not fetch that page

Topic-icon We could not fetch that page

8 years 11 months ago #52809 by bcnx
Hi,
while running autotune, we get:
JFBConnect Remote Error Check
Checks performed on: http://www.automation-magazine.be/
Error: Uh oh! We could not fetch that page.
Maximum (20) redirects followed

The DNS records are fresh, but they are functional. Also, when I click on the link in the error message, it works fine.
Is this something on your end?

thx,

BC
The topic has been locked.
Support Specialist
8 years 11 months ago #52810 by mel
Replied by mel on topic We could not fetch that page
It seems like there's something wrong on your site with how it's redirecting the user. I tested your page www.automation-magazine.be/ with another automated checker which also has the same number of redirects when trying to get your page as well:
www.internetmarketingninjas.com/header-checker/

-Melissa
The topic has been locked.
8 years 11 months ago #52811 by bcnx
Replied by bcnx on topic We could not fetch that page
Mmm, that's quite peculiar. Not sure why this Joomla site does that. I will try some things like changing the template and disabling modules and/or plugins.
Could you please describe what your check consists of?
Thanks,

BC
The topic has been locked.
8 years 11 months ago #52812 by bcnx
Replied by bcnx on topic We could not fetch that page
OK, here is something interesting: when I use the language in the URL (like www.automation-magazine.be/index.php/nl ), there is no problem the Ninja checker. Should I use these language containing URls with JFBConnect?

Thx,

BC
The topic has been locked.
8 years 11 months ago #52813 by bcnx
Replied by bcnx on topic We could not fetch that page
Just found a way to work around this issue, I hope it does not break other things:
Simply edit the languagefilter plugin en set 'Remove URL Language Code' to yes and this "solves" the problem.


BC
The topic has been locked.
Support Specialist
8 years 11 months ago #52817 by mel
Replied by mel on topic We could not fetch that page
Glad you were able to resolve the issue. Let us know if you run into any other problems with the error checker.

-Melissa
The topic has been locked.
8 years 11 months ago #52827 by bcnx
Replied by bcnx on topic We could not fetch that page
Hi,

it seems that the solution for this problem breaks access to the site for Safari browsers. This means we need to change it back. We're going to have a situation where the autotune check will not work, but does that mean that the social website logins will be faulty as wel?

Thank you,

BC
The topic has been locked.
Support Specialist
8 years 11 months ago #52835 by mel
Replied by mel on topic We could not fetch that page
Changing it back *should not* affect functionality. Our error checker is simply a tool to determine basic configuration and connectivity issues that usually cause problems with Facebook. However, if you have an error in our checker, it doesn't necessarily mean there will be functionality problems on the site. Please continue to test to make sure the social login and other Facebook functionality is working and let us know if you run into other problems.

-Melissa
The topic has been locked.
  1. Forum
  3. Discontinued Products
  5. JFBConnect v8.x Support (Joomla 3 Only) (CLOSED)
  7. We could not fetch that page
From the Blog
Facebook | Twitter | LinkedIn | Blog RSS