Last post Jul 28, 2005 03:05 PM by iwonder
May 15, 2005 08:44 PM|wabatson|LINK
Just got DNN 3.0.12 through GoDaddy.
I cannot get the base News Feed (RSS) module working. Here are the steps I followed.
The page displays the following error.
News Feed Is Not Available At This Time. Error message:The remote server returned an error: (401) Unauthorized.
Okay now you can make me feel stupid. [:)]
May 16, 2005 03:07 AM|walkerstewart|LINK
Judging from the error, it looks as though you need some form of authorisation to access the RSS newsfeed you have specified.
Try generating an RSS feed from one of your DNN module (see edit screen for url (I think)), then access it via the RSS news feed module.
This will show whether you are doing something incorrect or if it is just the feed you are accessing
Hope this Helps,
May 16, 2005 11:01 AM|iwonder|LINK
I can use the newsfeed link you specified w/o issues on my local machine, so there are some paths to explore for resolution to your issue. Ok, there are a couple of issues regarding RSS to be aware. First, that error message is sometimes just a product
of the caching for the site. If you've set up DNN with default values the site search index function will be set to 30 minutes. This sometimes causes issues with RSS and XML feeds until the site index is updated or while the index is being updated.
Next, some hosts will require a proxy username and password to operate through their firewall. If this is the case, you'll need some mods to core and some more info from your host to get by it. The mods are due to an incomplete function of passing the
proxy username and password to the app.
Finally, as MS strengthened security, the RSS, XML, and Webservices functions proviced within any .Net web application require some configuration changes that hosts need to make to allow them to function. There's a new document in the DNN \Documentation
folder that discusses the issue and workarounds. The bad news is good news too, though. All asp.net v1.0 sites were default operating from a security model that left opportunities for exploitation. These security issues were dealt with by MS using a newer
approach called Code Access Security. The topic is too deep to cover in this post, but if you do a google on the 'code access security', you'll find some good in-depth articles. Maybe a search on these forums would help too, as we have discussed the topic
many times, since the 'feature' became available.
Now, I'm not sure how GoDaddy hosts DNN, but most host are being encouraged to go to the new security model, and DNN is being developed and tested as a 'medium trust' application. The long story short, if a host is operating in 'medium trust' mode, the
RSS, XML, and WebServices modules in DNN will not function without host or site configuration adjustments.
Check the above issue out, and let us know how it goes. It could just be simply a need to refresh your browser view, so we'll keep watching for news from you.
May 16, 2005 04:39 PM|cathal|LINK
the doc iwonder mentions isn't in the documentation folder at the moment, it will be in the next release. I'm fairly sure godaddy are running in medium trust, so you'll have to specify the site in your web.config. Try adding the following to your web.config.
<trust level="Medium" originUrl="http://p.moreover.com/*"/>
May 16, 2005 05:18 PM|iwonder|LINK
May 17, 2005 10:27 AM|mannyd|LINK
very peculiar.. i am getting the same error on my dnn example site. yet running the godaddy rss feeds fine. hmm. i will have to mention this with the hosting team. thanks guys
Jul 28, 2005 01:25 PM|scott99a|LINK
Jul 28, 2005 03:05 PM|iwonder|LINK
Well, that error usually means there's a need for credentials to passthru a proxy server. This can be accomplished by specifying the information in the Host Settings for a site. However, you'll need your host to give you the essential information. It
can, also be due to the feed requiring some kind of username/password combo to get to the content. However, I don't believe this error is due to Code Access Security, as that issue reports a different error altogether. If I had to guess, I'd say the proxy
server info was required before you can leave your 'host' domain to get outside domain connectivity.