Connection to http://pdn.pega.com refused" errors in log
Hi All - I am also facing this issue with my system. I found that several articles on PDN are mentioning about disabling the PDN News feed by setting AllowAccessToExternalSystem DSS to false rather than actually eliminating the root cause. Can someone please help me with the resolution to this issue which can make this functionality work as usual?
Pegasystems Inc.
AU
Does the instance of Pega that you are using have access to pdn.pega.com, or is it on an isolated network or subject to firewall blocks.
If it does not have access, then setting the DSS is appropriate to stop Pega from attempting to access the feed in the first place.
Updated: 23 Jun 2016 22:06 EDT
Pegasystems Inc.
US
Hi Dhirendra,
The background is that PRPC wants to access the PDN for an RSS feed to use for notification of information. It should attempt to do so only once a week, but there were issues when the connection was not successful which leads to the attempt being made for every operator login. As you know setting the DSS AllowAccessToExternalSystem to false will disable these connection attempts to PDN.
The data page D_PDNFeed is responsible for getting PDN feeds on UI and it uses a REST connector(pyRSSConnectService) as it's source.
Please check the test connectivity is successful and ensure your application server isn't blocking any outgoing requests to https://collaborate.pega.com/, I think should some connection issue in here.
Let us know your observations
BR//
Harish
JPMC
US
Thank you Joel Mcleish and Harish Gunneri for your response! Connectivity is not successful on connector rule and it gives sometime HttpHostConnectException and sometime SocketTimeout (read timeout) exception.
If it is firewall issue I believe it should not even work from Mozilla REST client (I tested and it does work from REST client), Please correct me if I am wrong.
Accepted Solution
Pegasystems Inc.
AU
Hey Dhirendra,
If you're using a REST client then you would be testing connectivity between your client and the service. The connectivity issue here points to issues between the Pega server and the service endpoint.
Pegasystems Inc.
US
As suspected, looks like your application server is blocking or having a problem to access https://collaborate.pega.com/, if you can sort out this at your app server level, test connectivity will work fine on Connector rule.
Like Joel said test connectivity works fine from REST client as it's between your client and service endpoint.
JPMC
US
Sure Harsih and Joel! I will try to find the issue at app server level and see what is it preventing this to connect.