Is there any way to check for hardware faults?
1 Like
I only got an IPV6 adress. Could this be a problem?
1 Like
Donât think so, I am on IPv4 
It is to be expected that the pi3b+ shows more hardware problems due to itâs increased power hunger
The whole micro-USB thing is a bad idea from the beginning and not only the PSU but also the cables are important. These things are hard to detect reliably and maybe only some applications that push the limits fail, and fails seem random.
This read could be of interest
Of course, donât use the pi to power any hdd or anything else through USB
also read this
I think you might be right. I checked with raspimon and it seems the psu is insufficient. I will report back with a better cable.
1 Like
Hi,
I got the same Problem that it says âNextCloudPlus not yet initialized, trying again in a few seconds âŚâ and just stays there forever. refreshing the page just resets it and generates new random passwords ( http://i.imgur.com/t9FWp7D.png )
I build myself a little Stack out of 4 Pi3s, a Network-swtich and a USB-Powerbar, a 32GB SD-Card per Pi. I put HypriotOS on all of them to create a docker swarm, then used this image https://hub.docker.com/r/ownyourbits/nextcloudplus-armhf/ . Which I hope was the right one from the severe there.
1 Like
thatâs the right one. Like I said before, try it out first with a single pi plugged in with a good power supply and a good SD card
Let us know how the docker swarm experiment goes. I have been wanting to set that up myself
Oke, I removed 2 Pis, this USB-Charger can go up to 60 watts between the 6 slots so the 2 remaining ones definitely have enough power now (and the front LEDs donât show any low power levels.), the SD Cards are still work without a problem as far as I can tell.
Still the same Problem, Forever a loop when pressing the activate button.
I donâT know too much about docker yet, but docker attach and docker log commands (docker logs -f -t --details) show no sign of anything happening inside the container when pressing the button.
1 Like
I solved the problem by installing DietPi. It was super easy, works flawlessly and I am very happy about the performance. I can really can recommend it to you 
I have the same problem. But was does dietPi change? I wanted to use the NCP image on raspberrypi as many things are already preconfigured.
I know how to get DietPi running, but how do I install NCP then? I am a absolut Linux beginner. I can get SSH working, but do not know how to get the github script running.
additional info: I got NCP running some days ago, but I broke it by setting the backup medium to the medium where NCP was installed.
First, go to the DietPi Website, download the image for the raspberry pi and flash it to your SD-Card. I used Win32 Disk Imager but be careful that you do not erease other disks, markt the correct drive letter!
Then you create a file called âsshâ with notepad++ and put it directly on the sd card (boot partition).
You can set it up with Putty or with HDMI and Keyboard. I recommend that your router is giving a static ip to your pi.
Eject your sd from your pc, put it in your pi and boot it up. User name is: root and password: dietpi.
The file system will resize automatically and you will directly go into the dietpi launcher.
From the dietpi menu you will need to choose nextcloud in the optimized software tab, validate it and click install⌠it will take up to 20 Minutes depending on your pi and your internet connection.
I chose fail2ban too, to secure ssh from bruteforce in my home network (from trolling friends :P) After everything is finished type in http://âyour ipâ/nextcloud into your browser and you will be landing on the login page.
Default login is: username = admin; password = dietpi
Nextcloud is installed and ready to use 
but I highly recommend to change the password of the root user.
I have it running for some weeks now and on the 3 B+ it is running like a charm. I only lost some data because my nextloud client on pc was doing crazy things and I had no backup. So do Backups! Win32 Disk Imager can make them too 
Ah and besides, i made the pi only available in my home network and not from the web, because it is safer and I am saving very private data on it. If I want to access it from outside, I am using a VPN from my phone to my home router.
Feel free to ask if there is any question
Greetings
Borotes
Thank you very much! Install nextcloud is not a big deal- that I managed. But NCP offers some great solution, as is it preconfigures with lets encrypt, Samba and a very good menu (nextcloudpi.local:4443) for automatic backups etc.
It is a pity that its not working right now.
NCP is working perfectly right now, as usual. I test it everyday and there are thousands of users that verify this. Only in the Telegram group (everyone is invited btw) there are around 60 people.
I am positive that people seeing this have a bad power supply / SD card. You have no idea how many rpi users are running undervolted. OFC you need something CPU instensive to notice to the point where it fails.
I have the same issue, but installing on a laptop not a pi. I tried a pi and it worked, but frustratingly slowly, so Iâm having another try with more powerful hardware (a thinkpad I had lying around). In this case it appears to be an installation error, but Iâm not sure how to work out which part has failed.
I installed Debian Stretch, then installed nextcloudpi using the script on the nextcloudplus.com main page:
curl -sSL https://raw.githubusercontent.com/nextcloud/nextcloudpi/master/install.sh | bash
First:
I had an error that the | was unexpected.
Second:
As that seemed strange, I simply executed the same line again, and it worked fine this time, for most of the installation, installing maria-db and at least starting to install nextcloud. However it ended on an error that the file had ended unexpectedly when looking for a closing `"â. I compared the preceding lines with âŚ/install.sh, but couldnât work out quite where it had got up to, as most of the code is evidently pulled from other locations.
I navigated to localhost in the web browser, and got the same error reported above - it presented me with generated passwords etc, but when I clicked âactivateâ it failed with âNextcloudpi not yet initialised, trying again in a few secondsâŚâ and hung there forever.
Third:
I tried running the script a third time (why notâŚ). This time it ran through checking packages and not installing them because they already existed (obviously), and completed without the above error. It finished with
âSite nextcloud disabled.
To activate the new configuration, you need to run:
systemctl reload apache2
Site ncp-activation already enabled
useradd: user âncpâ already existsâ
I ran systemctl reload apache2, then returned to localhost in a web browser.
Same error again, still saying ânot yet initialisedâ
Where should I start in troubleshooting this?
Thanks
Forget that, managed to solve it.
From the shell, ran
sudo ncp-config
to launch the terminal version of the configuration panel.
Scrolled down to nc-init and ran it.
This initialised the installation, and I can now log in.
I do not know whether everything is fully running properly yet, but this is a manual way of triggering the initialisation. It may be that some others who hit this may be able to solve it in the same way, where it is not hardware-related.
Hey there,
I read this chat and thought thatâs my solution for the same problem: ncp ist no initialized yetâŚ
But after doing the ncp-init manually in the menu, it didnât change anything. Still appears âncp is not initialized yetâŚâ when enter with the IP adress from the raspberry pi in the browser.
Are there any other solutions for this problem?
I used this download for the image: NextCloudPi_RPi_03-04-19.tar.bz2
Iâm a bit frustrated, because I donât have many experience with Raspi and Linux but I read a lot of articles saying that NextCloudPi is such an easy and great solution for your cloud at home.
I would be very glad if you could help me.
Thank you
Sam
Hey there,
I had the same problem after doing a new clean installation with the image from 03.04.2019. âNextCloudPlus not yet initialized, trying again in a few seconds âŚâ stays there forever.
I tried different power sources, but it didnât help.
I solved it by executing âncp-initâ manually.
Now my Nextcoudpi works again 
Thanks @samden
Servus,
I just registered to share what was MY problem for this issue, maybe someone runs in the same one.
After wasting hours I noticed I had browser cookies turned off for the page by a browser plugin (uMatrix). Turning cookies back on solved the problem.
Greetings from Chewbacca