Feature #496
1&1 Hosting fsockopen() - Feature Request
| Status: | Resolved | Start: | 11/02/2008 | |
| Priority: | Normal | Due date: | ||
| Assigned to: | - | % Done: | 0% |
|
| Category: | - | |||
| Target version: | - | |||
Description
1&1 only has a medium trust level. The don't allow much with the fsockopen() and hence causes people likemyself to show 'Error Connecting' with server status. I have verified that it does not affect the database operations ( you can't use the one in your 1&1 package). They force people to use a proxy:
$proxy = 'ntproxy.1and1.com';
$port = '3128';
Thread discussion w/ paypal ipn and fsockopen on 1&1:
http://www.pdncommunity.com/pdn/board/message?board.id=ipn&message.id=548
History
Updated by Olly Ginger 64 days ago
We used to host our own proxy, but people with fsockopen blocks, often have the ability to open proxy connections blocked too.. so it doesn't really help.
Updated by Robert Mozden 64 days ago
There has to be some work-around. For me personally, the ability to add in the known proxy would be fine.
Updated by Robert Mozden 64 days ago
lol - if I had the money for a dedicated server, I wouldnt need sourcebans. Instead I would just do a symbolic link to 1 set of ban files.
Updated by Recon _ 64 days ago
That wouldn't exactly work though... They could overwrite each other... And besides, SB provides so much more.
Updated by Robert Mozden 61 days ago
- File fsockopeninoneandone.php added
I spoke to 1&1 today regarding the server status not updating. They put this code on my website and it works fine.
Updated by Lane Babuder 28 days ago
- Status changed from New to Resolved
Can we put this up as a "speak to your host's support" thread and call this closed?