php -v still says cli.

This should always say cli, because this is the binary you call from commandline (cli). This however should say cgi-fcgi:

php-cgi -v
php5-cgi -v

Cheers!

So I actually went ahead and installed php5-cgi again. And once thats done, reboot, run make again, and it is running! I can get to my page!

So php5-cgi was somehow missing since the beginning. It is either not installed, or not properly installed when installing all the packages together (I reinstalled everything from scratch 3 times before I started asking for help here). Which is weird.

Thank you very much for all your help Gabrys! :)

"bin-path" => "/usr/bin/php5-cgi"

in conf/lighttpd/single-wiki.conf

execute that command with "-v" and check if it says cgi or cli. (You should have php5-cgi installed before).

PHP 5.2.10-2ubuntu6.3 with Suhosin-Patch 0.9.7 (cli) (built: Nov 26 2009 14:42:49)

2009-12-29 22:17:27: (log.c.97) server started
2009-12-29 22:17:27: (mod_fastcgi.c.1051) the fastcgi-backend /usr/bin/php5-cgi failed to start:
2009-12-29 22:17:27: (mod_fastcgi.c.1055) child exited with status 2 /usr/bin/php5-cgi
2009-12-29 22:17:27: (mod_fastcgi.c.1058) If you're trying to run PHP as a FastCGI backend, make sure you're using the FastCGI-enabled version.
You can find out if it is the right one by executing 'php -v' and it should display '(cgi-fcgi)' in the output, NOT '(cgi)' NOR '(cli)'.
For more information, check http://trac.lighttpd.net/trac/wiki/Docs%3AModFastCGI#preparing-php-as-a-fastcgi-programIf this is PHP on Gentoo, add 'fastcgi' to the USE flags.
2009-12-29 22:17:27: (mod_fastcgi.c.1365) [ERROR]: spawning fcgi failed.
2009-12-29 22:17:27: (server.c.902) Configuration of plugins failed. Going down.
2009-12-30 13:53:26: (log.c.97) server started
2009-12-30 13:53:26: (mod_fastcgi.c.1051) the fastcgi-backend /usr/bin/php5-cgi failed to start:
2009-12-30 13:53:26: (mod_fastcgi.c.1055) child exited with status 2 /usr/bin/php5-cgi
2009-12-30 13:53:26: (mod_fastcgi.c.1058) If you're trying to run PHP as a FastCGI backend, make sure you're using the FastCGI-enabled version.
You can find out if it is the right one by executing 'php -v' and it should display '(cgi-fcgi)' in the output, NOT '(cgi)' NOR '(cli)'.
For more information, check http://trac.lighttpd.net/trac/wiki/Docs%3AModFastCGI#preparing-php-as-a-fastcgi-programIf this is PHP on Gentoo, add 'fastcgi' to the USE flags.
2009-12-30 13:53:26: (mod_fastcgi.c.1365) [ERROR]: spawning fcgi failed.
2009-12-30 13:53:26: (server.c.902) Configuration of plugins failed. Going down.
2009-12-30 17:10:21: (log.c.97) server started
2009-12-30 17:10:21: (mod_fastcgi.c.1051) the fastcgi-backend /usr/bin/php5-cgi failed to start:
2009-12-30 17:10:21: (mod_fastcgi.c.1055) child exited with status 2 /usr/bin/php5-cgi
2009-12-30 17:10:21: (mod_fastcgi.c.1058) If you're trying to run PHP as a FastCGI backend, make sure you're using the FastCGI-enabled version.
You can find out if it is the right one by executing 'php -v' and it should display '(cgi-fcgi)' in the output, NOT '(cgi)' NOR '(cli)'.
For more information, check http://trac.lighttpd.net/trac/wiki/Docs%3AModFastCGI#preparing-php-as-a-fastcgi-programIf this is PHP on Gentoo, add 'fastcgi' to the USE flags.
2009-12-30 17:10:21: (mod_fastcgi.c.1365) [ERROR]: spawning fcgi failed.
2009-12-30 17:10:21: (server.c.902) Configuration of plugins failed. Going down.
2009-12-30 17:59:24: (log.c.97) server started
2009-12-30 17:59:24: (mod_fastcgi.c.1051) the fastcgi-backend /usr/bin/php5-cgi failed to start:
2009-12-30 17:59:24: (mod_fastcgi.c.1055) child exited with status 2 /usr/bin/php5-cgi
2009-12-30 17:59:24: (mod_fastcgi.c.1058) If you're trying to run PHP as a FastCGI backend, make sure you're using the FastCGI-enabled version.
You can find out if it is the right one by executing 'php -v' and it should display '(cgi-fcgi)' in the output, NOT '(cgi)' NOR '(cli)'.
For more information, check http://trac.lighttpd.net/trac/wiki/Docs%3AModFastCGI#preparing-php-as-a-fastcgi-programIf this is PHP on Gentoo, add 'fastcgi' to the USE flags.
2009-12-30 17:59:24: (mod_fastcgi.c.1365) [ERROR]: spawning fcgi failed.
2009-12-30 17:59:24: (server.c.902) Configuration of plugins failed. Going down.
2010-01-01 15:00:18: (log.c.97) server started
2010-01-01 15:00:18: (mod_fastcgi.c.1051) the fastcgi-backend /usr/bin/php5-cgi failed to start:
2010-01-01 15:00:18: (mod_fastcgi.c.1055) child exited with status 2 /usr/bin/php5-cgi
2010-01-01 15:00:18: (mod_fastcgi.c.1058) If you're trying to run PHP as a FastCGI backend, make sure you're using the FastCGI-enabled version.
You can find out if it is the right one by executing 'php -v' and it should display '(cgi-fcgi)' in the output, NOT '(cgi)' NOR '(cli)'.
For more information, check http://trac.lighttpd.net/trac/wiki/Docs%3AModFastCGI#preparing-php-as-a-fastcgi-programIf this is PHP on Gentoo, add 'fastcgi' to the USE flags.
2010-01-01 15:00:18: (mod_fastcgi.c.1365) [ERROR]: spawning fcgi failed.
2010-01-01 15:00:18: (server.c.902) Configuration of plugins failed. Going down.
2010-01-02 11:16:03: (log.c.97) server started
2010-01-02 11:16:03: (mod_fastcgi.c.1051) the fastcgi-backend /usr/bin/php5-cgi failed to start:
2010-01-02 11:16:03: (mod_fastcgi.c.1055) child exited with status 2 /usr/bin/php5-cgi
2010-01-02 11:16:03: (mod_fastcgi.c.1058) If you're trying to run PHP as a FastCGI backend, make sure you're using the FastCGI-enabled version.
You can find out if it is the right one by executing 'php -v' and it should display '(cgi-fcgi)' in the output, NOT '(cgi)' NOR '(cli)'.
For more information, check http://trac.lighttpd.net/trac/wiki/Docs%3AModFastCGI#preparing-php-as-a-fastcgi-programIf this is PHP on Gentoo, add 'fastcgi' to the USE flags.
2010-01-02 11:16:03: (mod_fastcgi.c.1365) [ERROR]: spawning fcgi failed.
2010-01-02 11:16:03: (server.c.902) Configuration of plugins failed. Going down.

bin/configure.php

Once you have both *.ini files in conf/wikidot, go to your Wikidot root directory and run this as root:

lighttpd -D -f conf/lighttpd/single_wiki.conf

This is what Wikidot calls in order to run Lighttpd. Additionally here's the -D flag, that makes Lighttpd not go to background. If errors don't show on the consele, they should be logged to tmp/lighttpd/error.log (in Wikidot root directory).

Put here any errors on console or logged to file.

port 8080 is not being listed. So I guess wikidot is not binding to lighttpd properly. What should be configured so that it would bind to lighttpd? Thanks.

Alex

1. netstat -natp | grep lighttpd

This should return at least two lines, one for default :80 lighttpd server, second for lighttpd run from wikidotctl. If you have indeed two different ports listed (for example :80 and :8080) try http://127.0.0.1:8080/ in your browser to see what Lighttpd has to say :-).

Yes, I did use that to start wikidot, and it did give me a message stating that wikidot has started, without any errors. So I assume everything has been installed correctly.

Do I need to make any manual configurations or changes to other files in order to get this to work? For example, the ones mentioned in the previous posts, or any other files that you can think of?

Alex

/etc/lighttpd/lighttpd.conf
/wikidot/conf/lighttpd/wikidot_ini.conf
/wikidot/conf/lighttpd/single_wiki.conf
/wikidot/conf/lighttpd/wikidot_ini.conf.orig

I did modify /wikidot/conf/wikidot.ini to not use wikidot as username and password though.

Thanks,
Alex

I want to setup a Wikidot site from home and I have encounter a trouble.

I am using Ubuntu Server 9.10 and it is running on Virtualbox. I followed the guide at http://www.wikidot.org/installation-guide , and even though I have encountered different issues before, everything is set up right now.

However, when I enter the link at the end of 'make', I get "Internet explorer cannot display the webpage". I also tried using Firefox (which is recommended for wikidot) and I am still unable to load the page.

I have tried loading the page from another computer on the same network, using the IP of this ubuntu machine; as well as using the local host IP directly from the ubuntu machine. Both of which have similar results.

When loading the IP without specifying port 8080 (ie. using the default port 80), I do get the default page from lightpd, so I know lighttpd is working.

Would someone be able to enlighten me in the right direction if they haev encountered this? Or if anyone have any suggestions?

Thanks,
Alex