basedir restriction & .htaccess errors / Synology 106e v

[keithww]

This looks like two errors that may be related.

on the .htaccess I really don't understand this one, I have created this as an empty file and given the serendipity user full access to this file, but it still fails.

If I create the file from the text on the screen I get a page not found from the web server, most likely because of the second error.

on the "fopen() [function.fopen]: open_basedir restriction" error, I looks like I need to add a dir to the path, or give permission to a dir. This is a NAS, and I have full control if I can find the file. I do not have Telnet installed yet, but that will be done this evening.

http://www.synology.com/enu/products/DS ... /index.php

Thanks for the help.

Page from after the install below.

___________________________________________________________

To check your local webserver installation, serendipity needs to be able to write the file ".htaccess". This was not possible because of permission errors. Please adjust the permissions like this:
chmod go+rwx /volume1/web/serendipity/
and reload this page.Checking to see if the database and tables already exists... they do, will not install the database again

Attempting to write .htaccess file...... FAILED
Cannot write to file /var/services/web/serendipity/.htaccess. Please create the file yourself or check permissions

* Just copy the code below and place it in /var/services/web/serendipity/.htaccess in your serendipity folder:

# BEGIN s9y
DirectoryIndex /serendipity/index.php
php_value session.use_trans_sid 0
php_value register_globals off

<Files *.tpl.php>
deny from all
</Files>

<Files *.tpl>
deny from all
</Files>

<Files *.sql>
deny from all
</Files>

<Files *.inc.php>
deny from all
</Files>

<Files *.db>
deny from all
</Files>

# END s9y


Warning: fopen() [function.fopen]: open_basedir restriction in effect. File(/var/services/web/serendipity/serendipity_config_local.inc.php) is not within the allowed path(s): (/volume1/web:/volume2/web:/volume3/web:/volume4/web:/volume1/photo:/volume2/photo:/volume3/photo:/volume4/photo:/usr/syno/synoman/phpsrc:/etc:/var/run:/tmp:/var/spool/php:/volume1/@tmp/php:/var/services/web:/var/services/photo) in /volume1/web/serendipity/include/functions_installer.inc.php on line 72

Warning: open(/var/services/web/serendipity/serendipity_config_local.inc.php) [function.fopen]: failed to open stream: Operation not permitted in /volume1/web/serendipity/include/functions_installer.inc.php on line 72
Serendipity has been successfully installed
Visit your new blog here
Thank you for choosing Serendipity

[garvinhicking]

Hi!

It looks odd to me that s9y seems to detect the path as /volume1/web/serendipity/ - but the error messages refer to "/var/services/web/serendipity/ - how does that come?

Did you maybe enter a path configuration in the installer that is not the path where you copied serendipity to?

The fopen() seems to be related to that path mismatch. Your server allows access to /volume1/web/serendipity, but it denies acces to /var/services/web/.

HTH,
Garvin

[keithww]

Like I said this is a NAS, so I have limited access to the root, but I do have access to privileges for /var/services/web/ and the serendipity user has full access to this dir.

[garvinhicking]

Hi!

But what is the difference in those directories?

If you copied the s9y release files to /var/services/web/ you must also make sure in the installer configuration you enter /var/services/web as the directory...

You need to make sure that the directory where you put s9y in is allowed to be writable and is contained in your PHP.ini's include_path and open_basedir path(s).

If symbolic links are in place, your server admin must make sure that the TARGET of the symlinks are contained in the php.ini settings AS WELL as the symbolic link path- at least from my experience it's required to add both.

Best regards,
Garvin