By mark semczyszyn on Sunday, 19 January 2014
Posted in Technical Issues
Replies 11
Likes 0
Views 1.7K
Votes 0
Fresh install of latest EasyBlog on a Joomla 3.2.1 server. It's an intranet so behind a firewall proxy. To get Joomla Updating working, I needed to set a proxy in /libraries/joomla/http/transport/curl.php and also remove libraries/joomla/http/transport/socket.php and libraries/joomla/http/transport/stream.php

When viewing EasyBlog Dashboard, it says can't connect to news server. When clicking updater (I have not yet entered my API key) I get a blank white screen. Is this because the above two transports had to be removed for Joomla Update to work?

thanks, mark
Thanks for updating mark, glad that your issues are resolved now
·
Monday, 17 February 2014 18:27
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello Mark,

You might want to try again to retrieve the API key from the http://stackideas.com/dashboard and enter the API key before update. If you still face the issue, you can manually download Easyblog and install it in Extension Manager or you can provide us your backend and FTP access so we can have a better look on your issue here.
·
Sunday, 19 January 2014 09:06
·
0 Likes
·
0 Votes
·
0 Comments
·
OK - went to Easyblog Dashboard and copied API Key, when to joomla administration backend and EasyBlog component, CLicked "what next" on the right hand side and entered my API key. CLicked save. Message was API key saved successfully. Then clicked updater, and this was in the httpd error log

[Thu Jan 30 20:16:45 2014] [error] [client 172.16.101.103] PHP Fatal error: Call to a member function xpath() on a non-object in /var/www/html/components/com_easyblog/helpers/helper.php on line 444, referer: http://luna.smhsct.local/administrator/index.php?option=com_easyblog

Manually updated to latest easyblog _3.9.15218 and rechecked updater. Same error in error log and updater produces a blank screen. FYI, Joomla updates work fine.
·
Friday, 31 January 2014 04:21
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello Mark,

Without access your your site there is little we could do to debug the issue on your site
·
Friday, 31 January 2014 05:04
·
0 Likes
·
0 Votes
·
0 Comments
·
Yup sorry - it's not possible being a secure Intranet. Any other debug info I can supply?
·
Friday, 31 January 2014 06:11
·
0 Likes
·
0 Votes
·
0 Comments
·
Guys - I need to update this - the EasyBlog updater isn't working (for me).

It's not working because my intranet is behind a proxy and doesn't have direct access to the Internet. I just built a test site using same joomla and php version that has a direct internet connection. Installed EasyBlog (latest) and went to dhashboard. The latest news shows. News doesn't show on the intranet version because it can't connect to the internet. What's the mechanism Easyblog is using for connecting to the Internet? I've had to force joomla to use Curl for its HTTP transport because only that supports a proxy directive.

This is clearly something to do with the proxy and lack of direct internet connection - so not really an emergency or a major issue with Easyblog. Just wanted to update you and see if we can find a workaround in this case.

Thanks, mark
·
Friday, 31 January 2014 17:36
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello Mark,

Sorry for the late reply. It seems like your proxy is able to connect to Joomla server but not to our server. You can try contacting the server people to check if our domain is blocked? Also I would suggest that due to this issue you should refrain from using the Updater. Please download the installer and update manually Hope this helps.

Thanks!
·
Wednesday, 12 February 2014 15:33
·
0 Likes
·
0 Votes
·
0 Comments
·
HI! I control the proxy so if there is a specific domain you guys have for updates, I can check? Although the server does apparently have a natted connection to the Internet - but it's going through the NHS network so that may be an issue. I'll see if I can resolve this another way and get the server pointing through an alternate internet connection. In the mean time, yes, I shall keep an eye on the dashboard and apply updates manually.

cheers, mark
·
Thursday, 13 February 2014 17:49
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi - I'm in control of the Proxy so it's not that - but I'm told that IP address 198.61.176.150 is being blocked and dropped on the main firewall - that's rackspace cloud hosting in Texas registered to stackideas.com - so that's yours, right?

SPI on the firewall seems to be blocking it because the outbound port is 80 but the responses are coming from dynamic ports - not port 80 - at the moment, it's dropping replies from 56424 - 56490.

Can you specify a port range we can expect replies from and then include them in the firewall rule?

mark
·
Thursday, 13 February 2014 19:18
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello Mark,

I am not too sure what port are you referring to here as we did not set any specific ports. When you are connected to port 80, I don't see why it's returning to other ports?
·
Friday, 14 February 2014 01:47
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi - good news. The source ports being returned by the firewall are irrelevant - apparently, it;s some internal service port thing and not unusual. I've had the internet connectivity of the server altered not to use the NHS network. Everything now works - news, updates etc. For some reason your cloud service is being blocked on the NHS network which is outside my control. Going for the alternate internet connection bypasses any blocks that may have been applied.

thanks for your help and confirmation of ports etc. I'm happy for this ticket to be closed.

mark
·
Monday, 17 February 2014 18:07
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post