Posted by Markus on 06/20/07 11:21

Hi

My ISP seems to have made a PHP version upgrade - without any change in
the code, a new error occurs:

PHP Warning: ftp_nlist() [function.ftp-nlist]: open_basedir restriction
in effect. File(/var/tmp/) is not within the allowed path(s):
(/data/htdocs/domain.com/:/usr/local/share/pear/:/tmp/:/var/tmp/) in ...

I have found some bugs related to open_basedir and temp directory
creation, they have all been set to Bogus, as /tmp/ should be added to
the allowed paths. Others are about trailing slashes that do not match.

But what looks special and disturbing to me in my example: The required
path does actually match an allowed paths entry:

- File(/var/tmp/)
- allowed path(s):
(/data/htdocs/domain.com/:/usr/local/share/pear/:/tmp/:/var/tmp/)

So, what could I be missing? Both temporary directory and open_basedir
seem to be properly set. Could this be a disturbing between the PHP and
FTP users, which have different base directories? Or is it related to
the trailing slash problem?

Does anybody know a way how to work around this? I am grateful for any hint!

Markus

• Next in forum: Re: Parsing a php include (which also contains php code) - or "Reparsing" the php file
• Prev in forum: Re: Parsing a php include (which also contains php code) - or "Reparsing" the php file
• Thread view: open_basedir: allowed path not recognized

[Reply to this message]