Feed Manager - (504) Gateway Timeout

This forum is only for questions or discussions about working with the mojoPortal source code in Visual Studio, obtaining the source code from the repository, developing custom features, etc. If your question is not along these lines this is not the right forum. Please try to post your question in the appropriate forum.

Please do not post questions about design, CSS, or skinning here. Use the Help With Skins Forum for those questions.

This forum is for discussing mojoPortal development

This forum is only for questions or discussions about working with the mojoPortal source code in Visual Studio, obtaining the source code from the repository, developing custom features, etc. If your question is not along these lines this is not the right forum. Please try to post your question in the appropriate forum.

You can monitor commits to the repository from this page. We also recommend developers to subscribe to email notifications in the developer forum as occasionally important things are announced.

Before posting questions here you might want to review the developer documentation.

Do not post questions about design, CSS, or skinning here. Use the Help With Skins Forum for those questions.
This thread is closed to new posts. You must sign in to post in the forums.
8/13/2014 9:39:15 AM
Gravatar
Total Posts 63
Jerry McCreary
SureFire Studios, Inc.

Feed Manager - (504) Gateway Timeout

The feed manager pulling feeds from Events Calendar Pro is suddenly causing the site to hang up when navigating to the page with instance of the feed manager.

Can you suggest a fix or what I need to look for?

(Is this a known problem that upgrading to the latest version of mojoPortal and Events Calendar Pro would fix?)

System info:

mojoPortal Version 2.3.8.1 MSSQL
Operating System Microsoft Windows NT 6.1.7601 Service Pack 1
ASP.NET Info v4.0.30319 Running in Full Trust
 

Feature Versions:

STS_EventCalendar 3.4.0.5

Error:

2014-08-13 10:13:58,222 ERROR 71.80.14.120 - en-US - /mypage - mojoPortal.Web.FeedUI.FeedCache - There was a problem trying to read the feed for url http://www.mysite.com/events293rss.aspx.  Ignoring. 
System.Net.WebException: The remote server returned an error: (504) Gateway Timeout.
   at System.Net.HttpWebRequest.GetResponse()
   at Argotic.Common.SyndicationEncodingUtility.CreateWebResponse(Uri source, ICredentials credentials, IWebProxy proxy)
   at Argotic.Common.SyndicationEncodingUtility.CreateSafeNavigator(Uri source, ICredentials credentials, IWebProxy proxy, Encoding encoding)
   at Argotic.Syndication.GenericSyndicationFeed.Create(Uri source, ICredentials credentials, IWebProxy proxy, SyndicationResourceLoadSettings settings)
   at mojoPortal.Web.FeedUI.FeedCache.GetRssFeedEntries(Int32 moduleId, Guid moduleGuid, Int32 entryCacheTimeout, Int32 maxDaysOld, Int32 maxEntriesPerFeed, Boolean enableSelectivePublishing)

Thanks,

Jerry

8/13/2014 9:45:33 AM
Gravatar
Total Posts 18444

Re: Feed Manager - (504) Gateway Timeout

most likely a network issue or firewall issue. The web server is trying to make a server side web request to get the feed but it is failing to get a response. could be a network problem or a change in firewall settings could be blocking the web request. even though it is on the same server it still is like the server is making a request over the internet.

first step is to check the feed manually with a web browser making the request for the feed url, that is probably working fine but the web server is not able to make a similar request for some reason.

8/13/2014 9:52:35 AM
Gravatar
Total Posts 63
Jerry McCreary
SureFire Studios, Inc.

Re: Feed Manager - (504) Gateway Timeout

Yes, the feed is working fine from the web browser. I'll pass your info along to the sys admin, then followup on this post.

8/22/2014 9:03:54 AM
Gravatar
Total Posts 63
Jerry McCreary
SureFire Studios, Inc.

Re: Feed Manager - (504) Gateway Timeout

Turns out that the issue was indeed a change in the network/firewall.

Thanks Joe.

You must sign in to post in the forums. This thread is closed to new posts.