nZEDb => Support => Topic started by: RoddyJoff on 2018-06-09, 10:26:00 AM

Title: nZEDb on Raspberry STRETCH
Post by: RoddyJoff on 2018-06-09, 10:26:00 AM

I have been trying to install nZEDb onto my RPI 2B+ for the last week or so and am driving myself mad!

I have tried Wheezy, Jessie and finally the latest Stretch.

First of all I used this:

to install LAMP with no errors.

Everything works including the default Apache index.html file when I connect from my Mac at

Next I installed nZEDb using the following command:

sudo git clone /var/www/nZEDb

and this is where it starts to wrong.

I discovered that the default web directory on Stretch differs to that of Wheezy. The original nZEDb installation expects /var/www but it now is /var/www/html on Stretch.

I therefore attempted to ‘fix’ this by changing sites-available and DocumentRoot and other things I cannot remember, getting myself into an endless loop.

If I install a simple index.html file in /var/www/nZEDb before making any changes then works insofar that I get the message in the index.html file so why doesn’t work, having removed the index.html file?

I am at a loss to say the least. I am about to re-install Apache to set everything to a base/normal state but after that don’t know where to go.

Should I have install nZEDb in /var/www/html rather than try to reconfigure?

If not how do I fix it?

Many thanks in advance ;-)


I think a simpler question would be, in which directory should I execute this command:

sudo git clone

/var/www or var/www/html or /var/www/nZEDb

Many thanks.
Title: Re: nZEDb on Raspberry STRETCH
Post by: kaibosh on 2018-06-12, 09:37:33 AM
Minimum memory requirement is 4Gb. Even if you managed to get nzedb installed, it would run so damn slow due the shared USB/network config the RPi's have.
Title: Re: nZEDb on Raspberry STRETCH
Post by: hardknox on 2018-07-10, 10:43:30 AM
I've been running it on my RPi for about 4 years. As the previous poster mentioned it will be slow. You should have no more than 4-8 groups indexed -- depending on how busy they are -- and keep only about 6 months of data. Only 1-2 users would be good to :)

On that note the following guide was pretty helpful -- as was the Ubuntu guide these guys provide in the wiki on github

Edit: Additionally only run everything sequentially (do not use tmux or more than 2 concurrent sessions). I ended up having to write a few custom scripts over a period of time to get it running how I wanted.