Project

General

Profile

Actions

Bug #8184

closed

HTTP Request Failure in FeedWordPress

Added by Luke Waltzer almost 7 years ago. Updated almost 7 years ago.

Status:
Resolved
Priority name:
Normal
Assignee:
-
Category name:
-
Target version:
-
Start date:
2017-05-22
Due date:
% Done:

0%

Estimated time:
Deployment actions:

Description

Trying to set up syndication using FeedWordPress, I have success when I'm syndicating from Commons site to Commons site, but when I try to syndicate to a host outside of the Commons I get the following error:

HTTP request failure

cURL error 28: Connection timed out after 10001 milliseconds
HTTP Transport:

string(12) "WP_Http_Curl"


I have verified this with multiple validated feeds generated by the Commons (but was only testing on Reclaim-hosted sites).


Files

Actions #1

Updated by Boone Gorges almost 7 years ago

  • Status changed from New to Reporter Feedback

I've just tried the following:

1. Activate FeedWordPress
2. At Dashboard > Syndication > Syndicated Sites, add new feed https://teleogistic.net/feed
3. Once this feed source appears on the 'Syndicated sources' list, click "Update Now"
4. Page reloads with an "Update complete" message in the "Update feeds now" box

Am I looking at the right place? If not, please give more details about what you mean by "when I try to syndicate to a host..." and where you're seeing the error. If I've described the correct routine, please share the specific feeds you're testing with, so that I can see whether it has to do with the specific source feeds.

Actions #2

Updated by Luke Waltzer almost 7 years ago

Sorry if this wasn't clear; this error appears on a non-Commons site (have tested two) when trying to import feeds generated by Commons sites (also two).

Actions #3

Updated by Boone Gorges almost 7 years ago

Can you please share the details? Specifically, exactly what feed URLs are you using? (Send them to me privately if you'd prefer not to share in this context.) It's possible that there's a redirect issue or something like that, depending on URL format.

Actions #4

Updated by Boone Gorges almost 7 years ago

  • Related to Bug #7997: Transition from single cac-files.php file server to site-specific .htaccess directives added
Actions #5

Updated by Boone Gorges almost 7 years ago

  • Related to deleted (Bug #7997: Transition from single cac-files.php file server to site-specific .htaccess directives)
Actions #6

Updated by Luke Waltzer almost 7 years ago

http://vp.commons.gc.cuny.edu/?tag=cuny-humanities-alliance&feed=rss2

http://tlc.commons.gc.cuny.edu/feed/

http://gcdi.commons.gc.cuny.edu/feed/

These were successful on workshop.commons.gc.cuny.edu but not on sandbox.sahawaltzer.org or on cunyhumanities.org.

Actions #7

Updated by Boone Gorges almost 7 years ago

I'm not able to reproduce timeouts on a local machine. The TLC feed is failing validation because of what appears to be a whitespace issue? Screenshot attached. (The other two are importing in what I think is the correct way, though I do not have much experience with this plugin.)

I don't see an obvious place in the feedwordpress plugin where it'd be outputting an error message like what you've reported. Can you please confirm exactly where in the interface you're seeing the message, and what steps you're performing up to that point? It will help me make some guesses about the source of the problem if I know exactly where FWP is getting hung up, but I don't have enough information yet.

Actions #9

Updated by Boone Gorges almost 7 years ago

Thanks for the screenshots, Luke. I can now see the path that's leading to the error.

As a test, can you try adjusting the timeout interval for the feeds in question? Go to "Feed and Update Settings", and increase the "Feed timout" under Advanced Settings. Try something like 30 seconds. (In my local tests, Commons feeds were responding in between 6 and 13 seconds.)

Actions #10

Updated by Luke Waltzer almost 7 years ago

Tested up to 60, but still timing out after about 10 seconds.

Let me know if I should ask Tim if there's a setting on the Reclaim side that's forcing this...

Actions #11

Updated by Boone Gorges almost 7 years ago

Yes, I'd suggest reaching out to Reclaim. This suggests that something - either globally on Reclaim, or within your WordPress installation - is overriding the timeout settings on outgoing pings.

Actions #12

Updated by Luke Waltzer almost 7 years ago

  • Status changed from Reporter Feedback to Resolved

Tim reports:

Our global firewall snagged 146.96.128.200 which appears to be the IP for the Commons. I just cleared it out and whitelisted it (occasionally FWP activity will trigger something there, our firewall shows a captcha but of course a server can’t exactly answer a captcha). Sorry about that! Let me know if any issue persists.

I have run a successful test-- thanks, Boone!

Actions #13

Updated by Boone Gorges almost 7 years ago

Glad to have it tracked down! Thanks for following up.

Actions

Also available in: Atom PDF