ExpressionEngine CMS
Open, Free, Amazing

Thread

This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.

The active forums are here.

Installation problems-- "open_basedir restriction"...

November 19, 2011 2:20pm

Subscribe [3]
  • #1 / Nov 19, 2011 2:20pm

    hotknife

    59 posts

    Hi,

    I’ve searched on this, but the answers haven’t been very helpful.

    I’m trying to install EE2 on a shared Windows hosting space. I’ve set the permissions per the instructions here (albeit using Windows directory-level equivalents). I didn’t yet change my system folder name, so that shouldn’t be an issue. But when I go to run admin.php, I first get the error that

    Your system folder path does not appear to be set correctly. Please open the following file and correct this: admin.php

    OK. That’s not it, clearly. I went into admin.php and turned error reporting on. Now I get this:

    Warning: file_exists() [function.file-exists]: open_basedir restriction in effect. File(.system/codeigniter/system/core/CodeIgniter.php) is not within the allowed path(s): (d:\webs\) in D:\webs\[REDACTED]\admin.php on line 183

    OK. First off, what is open_basedir? Online documentation seems to indicate that it is a means of preventing scripts from accessing files outside the root folder. Why in the world would that be triggered?

    Second, I’m not sure why the D: drive of this server is coming up in that filepath; running a filepath determination script for the directory in which admin.php et al live, I actually get:

    c:\windows\system32\inetsrv

    Any help here?

  • #2 / Nov 19, 2011 10:14pm

    First, I would suggest running http://ellislab.com/expressionengine/user-guide/installation/requirements.html to see if there are any red flags. You are correct about open_basedir, just a security setting for PHP in shared environments. If your host won’t disable it (not likely) then you hopefully can work around it but moving hosts might be the better option long-term. Hopefully it is just a path issue, something that you can set in the config file. c:\windows\system32\inetsrv is a system directory for the webserver and would not be the root for your actual site, the d:\webs\... makes a lot more sense for your actual website location. What do you get if you run dirname()? What do you have set for the system path in your config file? Might try putting the absolute Windows path there.

  • #3 / Nov 19, 2011 10:20pm

    hotknife

    59 posts

    First, I would suggest running http://ellislab.com/expressionengine/user-guide/installation/requirements.html to see if there are any red flags.

    Yes, I ran the wizard before even buying the EE2 license. The only “no” was for “URL Segment Support”, but I’m OK with that. All else was fully supported.

    I’ll run through your other suggestions before responding in detail. Thanks.

  • #4 / Nov 19, 2011 10:45pm

    hotknife

    59 posts

    You are correct about open_basedir, just a security setting for PHP in shared environments. If your host won’t disable it (not likely) then you hopefully can work around it but moving hosts might be the better option long-term.

    I’ve sent in a ticket, and I’ll see what they say. I don’t think moving is an option; my client has has been with this host a long time.

    Hopefully it is just a path issue, something that you can set in the config file. c:\windows\system32\inetsrv is a system directory for the webserver and would not be the root for your actual site, the d:\webs\... makes a lot more sense for your actual website location. What do you get if you run dirname()?

    I get “.”

    What do you have set for the system path in your config file?

    I had set “./system” just as it came from the factory, but that obviously didn’t work.

    Might try putting the absolute Windows path there.

    OK. I tried putting ‘D:/webs/[redacted]/system/’  and the page did render (sort of), but I got these errors:

    A PHP Error was encountered

    Severity: Warning

    Message: is_dir() [function.is-dir]: open_basedir restriction in effect. File(themes/cp_global_images/) is not within the allowed path(s): (d:\webs\)

    Filename: controllers/wizard.php

    Line Number: 1540
    A PHP Error was encountered

    Severity: Warning

    Message: is_dir() [function.is-dir]: open_basedir restriction in effect. File(../themes/cp_global_images/) is not within the allowed path(s): (d:\webs\)

    Filename: controllers/wizard.php

    Line Number: 1540
    A PHP Error was encountered

    Severity: Warning

    Message: is_dir() [function.is-dir]: open_basedir restriction in effect. File(../../themes/cp_global_images/) is not within the allowed path(s): (d:\webs\)

    Filename: controllers/wizard.php

    Line Number: 1540
    A PHP Error was encountered

    Severity: Warning

    Message: is_dir() [function.is-dir]: open_basedir restriction in effect. File(../../../themes/cp_global_images/) is not within the allowed path(s): (d:\webs\)

    Filename: controllers/wizard.php

    Line Number: 1540
    ....

    and on and on.

     

  • #5 / Nov 19, 2011 10:46pm

    hotknife

    59 posts

    Hang on. I turned off error reporting (thus hiding those errors) and it allowed me to complete the installation.

    Now I’ve got:

    Your config file does not appear to be formatted correctly.

    Off to check it…

  • #6 / Nov 19, 2011 10:49pm

    hotknife

    59 posts

    Hmm.  system/expressionengine/config/config.php is completely empty. Is that normal? Is there another config file somewhere? (I’m coming from an EE 1.x background here… first 2.x install.)

  • #7 / Nov 21, 2011 10:55am

    hotknife

    59 posts

    Actually, you can close this thread for now. My web host is having much bigger problems than EE. Won’t let me upload anything or make configuration changes to web sites.

    Thanks.

  • #8 / Nov 21, 2011 2:30pm

    Dan Decker

    7338 posts

    Hi hotknife,

    If you still experience trouble after your host gets everything sorted out, please let us know in a new thread.

    Thanks!

.(JavaScript must be enabled to view this email address)

ExpressionEngine News!

#eecms, #events, #releases