掲示板

RSS Portlet notifies url not found

6年前 に Thomas Lucas によって更新されました。

RSS Portlet notifies url not found

New Member 投稿: 4 参加年月日: 14/06/26 最新の投稿
We are using Liferay 6.2 GA4. On our startpage we use a rss-portlet to display the followig feed:
https://agent.outsourcing.de/users/1/web_requests/12/market_news.xml
The portlet worked with this url for a long time. But as of late the portlet gives an error: "https://agent.-... not found" . allthought the url still works.
There were no changes in the short past. The only thing to mention is, that the ssl-certificate was expired. But I renewed it now.

any ideas?
I tested other external urls - they worked.
I tested it on production, test an developement (local) system. Same behavior on all systems.

Thanks
6年前 に Karen Housden によって更新されました。

RE: RSS Portlet notifies url not found

New Member 投稿: 7 参加年月日: 17/05/15 最新の投稿
I've just encountered the same issue (different rss feed, however). It was working fine for months and then suddenly stopped. We've made no Liferay upgrades or certificate issues as mentioned by the thread creator. I've tried a few others (yahoo, reuters) and have found no issue. I've looked through the feed data and don't see anything "unusual". Alas, it tells me it can't find the feed.

The feed we're using is coming from a Word press blog, if that makes a difference.

Anyone have an answer?
thumbnail
6年前 に Olaf Kock によって更新されました。

RE: RSS Portlet notifies url not found

Liferay Legend 投稿: 6396 参加年月日: 08/09/23 最新の投稿
Note that it's the server, not the browser, requesting those RSS feeds. Any changes to its DNS, firewalls, portfilters or allowed outbound connections etc. might result in failure of document retrieval from the external URL, even if it's available in the browser. The originally mentioned "agent.outsourcing..." URL today is not even available from my browser.

A good initial test is to just run wget on the URL in question directly from a shell on the server that Liferay runs on. If even that can't get the document, Liferay won't be able to get it as well.
6年前 に Thomas Lucas によって更新されました。

RE: RSS Portlet notifies url not found

New Member 投稿: 4 参加年月日: 14/06/26 最新の投稿
Olaf Kock:
The originally mentioned "agent.outsourcing..." URL today is not even available from my browser.

That's good news. The URL is only accessible from the liferay-server and from networks not blocked by firewall.

In our case the reason was in fact the renewed certificate. The server delivering the news is running huginn on nginx webserver to aggregate and filter news. The procedure for installing certificates on nginx is different from apache (where liferay runs on) and althought the browser was telling a different story the certificate was not installed proper.
So maybe - in case that word press is running under ssl- the certificate could be the root cause.
6年前 に Karen Housden によって更新されました。

RE: RSS Portlet notifies url not found

New Member 投稿: 7 参加年月日: 17/05/15 最新の投稿
I've done curl and wget on the server and it returned as expected. I've looked through Liferay logs and found no error. Was really hoping for a path to go down, but I'm not getting one.

I've used a custom template for this particular thing, but the rss feed portlet doesn't work either. If I add a new rss portlet to a page, the default feeds within it work, except this one: http://www.liferay.com/community/blogs/-/blogs_stream/community/rss . It shows the same result the blog I'm accessing in my template shows. We're still on 6.2, haven't upgraded just yet, incidentally. Curl and wget on that url also work as expected.

Error:
http://www.liferay.com/community/blogs/-/blogs_stream/community/rss cannot be found.
thumbnail
6年前 に Olaf Kock によって更新されました。

RE: RSS Portlet notifies url not found

Liferay Legend 投稿: 6396 参加年月日: 08/09/23 最新の投稿
A quick guess: Redirects or TLS-certificate trust. When I wget that URL, I'm being redirected 4 times (sorry for the german wget output, you might identify the "301/302 Moved" parts):

$ wget http://www.liferay.com/community/blogs/-/blogs_stream/community/rss
--2017-09-22 12:06:52--  http://www.liferay.com/community/blogs/-/blogs_stream/community/rss
Auflösen des Hostnamen »www.liferay.com (www.liferay.com)«... 2400:cb00:2048:1::6810:d7a0, 2400:cb00:2048:1::6810:d6a0, 2400:cb00:2048:1::6810:daa0, ...
Verbindungsaufbau zu www.liferay.com (www.liferay.com)|2400:cb00:2048:1::6810:d7a0|:80... verbunden.
HTTP-Anforderung gesendet, warte auf Antwort... 301 Moved Permanently
Platz: http://web.liferay.com/community/blogs/-/blogs_stream/community/rss [folge]                                                                         
--2017-09-22 12:06:53--  http://web.liferay.com/community/blogs/-/blogs_stream/community/rss                                                               
Auflösen des Hostnamen »web.liferay.com (web.liferay.com)«... 173.196.212.35, 38.75.15.57                                                                  
Verbindungsaufbau zu web.liferay.com (web.liferay.com)|173.196.212.35|:80... verbunden.                                                                    
HTTP-Anforderung gesendet, warte auf Antwort... 301 Moved Permanently                                                                                      
Platz: https://web.liferay.com/community/blogs/-/blogs_stream/community/rss [folge]                                                                        
--2017-09-22 12:06:53--  https://web.liferay.com/community/blogs/-/blogs_stream/community/rss                                                              
Verbindungsaufbau zu web.liferay.com (web.liferay.com)|173.196.212.35|:443... verbunden.                                                                   
HTTP-Anforderung gesendet, warte auf Antwort... 302 Found                                                                                                  
Platz: http://web.liferay.com/community/blogs/general/-/blogs_stream/general/rss [folge]                                                                   
--2017-09-22 12:06:54--  http://web.liferay.com/community/blogs/general/-/blogs_stream/general/rss                                                         
Verbindungsaufbau zu web.liferay.com (web.liferay.com)|173.196.212.35|:80... verbunden.                                                                    
HTTP-Anforderung gesendet, warte auf Antwort... 301 Moved Permanently                                                                                      
Platz: https://web.liferay.com/community/blogs/general/-/blogs_stream/general/rss [folge]                                                                  
--2017-09-22 12:06:54--  https://web.liferay.com/community/blogs/general/-/blogs_stream/general/rss                                                        
Wiederverwendung der bestehenden Verbindung zu web.liferay.com:443.                                                                                        
HTTP-Anforderung gesendet, warte auf Antwort... 200 OK                                                                                                     
Länge: 15037 (15K) [text/xml]                                                                                                                              
In »»rss«« speichern.                                                                                                                                      
                                                                                                                                                           
rss    100%[========================================================>]  14,68K  --.-KB/s    in 0s       
                                                                                                                                                           
2017-09-22 12:06:55 (175 MB/s) - »rss« gespeichert [15037/15037]                                                                                           
                                                                                                                                                           
$ 
6年前 に Karen Housden によって更新されました。

RE: RSS Portlet notifies url not found

New Member 投稿: 7 参加年月日: 17/05/15 最新の投稿
No worries, I should brush up on my German! emoticon

I did notice the redirects on that particular URL. I'll run down that path. Thank you for the suggestion!
6年前 に Karen Housden によって更新されました。

RE: RSS Portlet notifies url not found

New Member 投稿: 7 参加年月日: 17/05/15 最新の投稿
No redirects on the URL I'm using and still no answers.
6年前 に Kirti Maharwal によって更新されました。

RE: RSS Portlet notifies url not found

New Member 投稿: 2 参加年月日: 17/10/18 最新の投稿
Did you find any resolution for this issue? I am facing the same issue.
6年前 に Karen Smallwood によって更新されました。

RE: RSS Portlet notifies url not found

New Member 投稿: 4 参加年月日: 10/05/17 最新の投稿
No, but if you're in need of help also, I'll spend some time reverse engineering the rss portlet and see what the problem is. I'd love a quick solution, but no one seems to have one.
thumbnail
6年前 に Olaf Kock によって更新されました。

RE: RSS Portlet notifies url not found

Liferay Legend 投稿: 6396 参加年月日: 08/09/23 最新の投稿
As I wrote above: TLS certificate trust can be a biggie: If your JVM doesn't trust the issuer of a https-certificate, it won't connect. And one of the redirects on the URL above redirects from http to https. This is not always easy to debug. Where your browser displays a big fat warning that you may be able to interactively override, server-to-server-communication just stops cold. Sometimes with better, some times with worse error logging.

After that, the URL you're trying to consume might reveal invalid RSS that chokes up the parser. But I'd suspect the error message to reflect this.
thumbnail
6年前 に Daniel Tyger によって更新されました。

RE: RSS Portlet notifies url not found

Regular Member 投稿: 105 参加年月日: 13/02/06 最新の投稿
Kirti Maharwal:
Did you find any resolution for this issue? I am facing the same issue.

We were also facing this issue. In a test env, we increased logging and saw PKI / SSL handshake error messages...

In our case, it did turn out to be SSL-related - but it took some time to get to the bottom of it. The source RSS site had undergone a new certificate setup via GoDaddy a few weeks prior to the new failures...

We tried importing the SSL cert / trust chain from that site into our liferay-tomcat .jks store without success. We also tried the reverse on the source side (import our InCommon certs to it...). No success.

The solution was to instead import the source site's trust chain into the CACERTS store of our 1.7 jdk and restart Liferay services. Due to the aging 1.7's cacerts and the GoDaddy new trust chain certs - apparently one was not available to tomcat.

Hope it helps someone else.