CMS Builder and outgoing ports
2 posts by 2 authors in: Forums > CMS Builder
Last Post: April 7, 2008 (RSS)
Hi,
My client's server's firewall is set to block all outgoing traffic. So everytime my client tries to login to the cms, there is a "connection refused" error. So the ISP allows traffic on port 80 for a few hours and we can get in. But they're not willing to leave it open permanently.
So CMS Builder must be calling home or something when it launches. Can someone help me get this resolved?
Thanks,
Tony
My client's server's firewall is set to block all outgoing traffic. So everytime my client tries to login to the cms, there is a "connection refused" error. So the ISP allows traffic on port 80 for a few hours and we can get in. But they're not willing to leave it open permanently.
So CMS Builder must be calling home or something when it launches. Can someone help me get this resolved?
Thanks,
Tony
Re: [tonythemediaguy] CMS Builder and outgoing ports
By Dave - April 7, 2008
Hi Tony,
You bet. The registration system should be passive. Meaning if there's a firewall you shouldn't get any errors. But it sounds like there's obviously a problem with how it's interacting with the firewall.
We've had a number of reports of PHP installs that are firewalled. I'm not sure how we're going to deal with that if/when we add more network features like blog pingbacks and so on.
Do you have the actual error message? I can probably write you a fix for it based on that.
You bet. The registration system should be passive. Meaning if there's a firewall you shouldn't get any errors. But it sounds like there's obviously a problem with how it's interacting with the firewall.
We've had a number of reports of PHP installs that are firewalled. I'm not sure how we're going to deal with that if/when we add more network features like blog pingbacks and so on.
Do you have the actual error message? I can probably write you a fix for it based on that.
Dave Edis - Senior Developer
interactivetools.com
interactivetools.com