Yep that's good enough for me. If you could send me the site details (domain, sr number and your name and address) using the link under my avatar then I will set this up for you and email you details on how to continue.

This has already been suggested. I believe it was intended that outbound connections would not be allowed but is seems slightly different configurations were used on some servers when they were upgraded. The ones that do allow fopen haven't been closed off as we have moved several customers to these servers now.
Please be aware that we will only move your site if you can prove it's absolutely necessary and moving your site will make it unavailable for a short period while the DNS updates.

I've replied to your message via email but in case you read this first:
Moving your site from one server to another will not effect your email accounts. You will simply have a new webspace folder with a different SR number. Email accounts are not linked to this.

Hi Eccles,
I sent you a private message last week, but have not heard back. I am on server 5. If I were to migrate to another server on Freeola, this presumably would mean that all 'sr' numbers would change too, including email addresses?

If this is the case, it's not an option as I have so many email addresses attached to this domain.

Look forward to hearing from you.

Hi Eccles. I have just found this thread and I too need outbound http access for a script. But it's being blocked.

What is the status of getting things opened up?

Thanks.

I will ask again:
"Well, could my sites be moved to server number 2 then?"

Well, could my sites be moved to server number 2 then?

Any news on this? As it seems to be dragging on a bit :(

I'm surprised no other web site developers have encountered this issue and reported it.

If any other web site developers have the time, please could you test whether this issue will affect you, by creating a 'tester.php' file containing the following:

<?php
$fp=fopen( 'http://www.google.co.uk/index.html', 'rt');
$testSTR=fgets($fp);
echo $testSTR;
?>

Upload it to your website then navigate to it using your usual web browser, do you see:
a) window.google={BLAH BLAH BLAH}
OR
b) Warning: fopen(http://www.google.co.uk/index.html) ... /freeola/users/#/#/

If you see (a) then you are OK, but, if you see (b) then the issue affects you, the first # is the server number your site is hosted on.

Please report your findings.

Gotta get this sorted ... ... ... please!

Sorry, but I've got to keep asking in case it gets forgotten; is there any progress on this problem? As its been over 2 weeks since I raised the ticket :o(

Do the engineers need anything more from me?

Have they looked at my 'tester.php' script at the locations I gave?

Its just I wouldn't have thought it'd take too long to rectify this problem, because as it works on some servers, surely they can identify the server differences and make the relevant changes ... can't they?

How soon is soon? :o)

Any updates on this?

Any updates on this issue?

Thanks, received and forwarded on!

Not yet. The server engineers have asked me for the location of scripts that are having problems so that is why I asked toshinmac to get in touch.
He hasn't done so yet so if you have scripts that are suffering the fopen problem then please send me their location (server and full path) and I can the forward them on.

Hi toshinmac,

The issue with sessions and open_basedir should now be fixed. Could  you send me the full paths of the scripts that are having trouble using fopen and also the paths of the ones that work on web server 2 and I can then check this out more thoroughly. You can use the link under my avatar to send me a message.

Hi postmanpat,

Thanks for the feedback.

Nothing to do with this issue but discovered whilst trying to work around the problem.

I tried putting some code onto server 8 - the first line of which is:
session_start();
and I get:
Warning: session_start() [function.session-start]: open_basedir restriction in effect.  File(/var/tmp/) is not within the allowed path(s): (/freeola/users/) in
/freeola/users/8/5/srnumber/htdocs/index.php5 on line 2

Fatal error: session_start()  [<a href='function.session-start'> function.session-
start</a>]:  Failed to initialize storage module: files (path: ) in
/freeola/users/8/5/srnumber/htdocs/index.php5 on line 2

The code works without issue on server 6 so I looked further into the problem by looking at the server settings using phpinfo();

Server 8 (and some of the others) have 'open_basedir' set to '/freeola/users/'
Server 6 has 'open_basedir' set to 'no value'.

It looks as though there is some inconsistency across the servers in the way that they have been configured.

I think this one warrants a ticket in the first instance.

Our web servers should be blocked from allowing outbound http access, so any that allow this are lucky! We are looking at getting this restriction removed so that you can check remote files or use things like RSS feeds.
Hopefully I can update you soon and let you know what the decision is.

Hi,

How / Did, this problem get resolved?
Because I am suffering from the same problem.
I have some PHP pages which use fopen and if I upload them to either server 0 or 1 they display the error, but if I upload them to server 2 they work fine. And I really want to be able to use them on my web site hosted on server 0.
Also, I swear at the start of the week the same PHP pages were working fine on server 0.
I have raised a support ticket regarding this, so hopefully it will get fixed soon.

Thanks

I'm not 100% but it seems as though allow_url_fopen is not set on server 6 (assuming your file permissions are correct). What does running phpinfo(); on server 6 show? If it shows it as disabled but  the other servers are showing as enabled the drop us a support ticket.
If it's read only access you need then why not try is_file()?