Hosting Issue
2 posts by 2 authors in: Forums > CMS Builder
Last Post: January 30, 2009 (RSS)
By _kate_ - January 30, 2009
I tried to install CMSB on a website and received this error message >
Warning: fsockopen(): unable to connect to tcp://www.google.com:80
(Connection timed out) in /srv/www/www.websiteaddress.com.au/htdocs/cms/lib/init.php on line 231 Error: PHP fsockopen() and/or network connectivity disabled!
Test connection to www.google.com return error #110 - Connection timed out
I wrote to the hosting support to have the changes made and they replied with the following >
Security policy prevents direct outbound WWW connections from the web server, and so cannot be allowed. You can however access external sites using our web proxy, IP address 000.00.0.00 (NB changed IP) port 8080
Will I still be able to use CMBS on this hosting account or should I tell the client to change over to another host?
Warning: fsockopen(): unable to connect to tcp://www.google.com:80
(Connection timed out) in /srv/www/www.websiteaddress.com.au/htdocs/cms/lib/init.php on line 231 Error: PHP fsockopen() and/or network connectivity disabled!
Test connection to www.google.com return error #110 - Connection timed out
I wrote to the hosting support to have the changes made and they replied with the following >
Security policy prevents direct outbound WWW connections from the web server, and so cannot be allowed. You can however access external sites using our web proxy, IP address 000.00.0.00 (NB changed IP) port 8080
Will I still be able to use CMBS on this hosting account or should I tell the client to change over to another host?
Re: [_kate_] Hosting Issue
By Dave - January 30, 2009
Hi Kate,
This feature isn't required so you can try disabling the error with the following code:
- Open cmsAdmin/lib/init.php
- Search for: displaySocketErrors();
- Add a comment (#) to disable it like this:
# displaySocketErrors();
In future we have some features in mind that will require outbound web connections (such as using google spellcheck, link validation, etc) but for now you're fine without it.
Hope that helps!
This feature isn't required so you can try disabling the error with the following code:
- Open cmsAdmin/lib/init.php
- Search for: displaySocketErrors();
- Add a comment (#) to disable it like this:
# displaySocketErrors();
In future we have some features in mind that will require outbound web connections (such as using google spellcheck, link validation, etc) but for now you're fine without it.
Hope that helps!
Dave Edis - Senior Developer
interactivetools.com
interactivetools.com