I used a browser to set up an admin account and create a user. However, I donāt know how to get SSH access.
I have a Ubuntu One account and think I understand I need to somehow make a connection between my Nextcloud Box and that account. However, I donāt currently have a clue how to proceed. Is there documentation on how to proceed in this scenario?
When using a pi2, SSH access was easy. To connect for the first time I could enter ubuntu as both default user name and default password. If I try this on a pi3-based system, I get access denied.
Iām hoping that I can use the installation I have already, rather than have to scrap that and start again, installing Ubuntu Core 16 first and then installing Nextcloud on that, which I think will be a significantly more complex process than what Iāve done so far: use a pre-built image including Ubuntu Core 16 and Nextcloud.
Not really, itāll take a little longer to setup but it isnāt complex vs setting up a traditional server.
That said, if you were to build from scratch Iād suggest the older method with a full ubuntu/debian server as you get far more control.
SSH in the newest is a pain as it require(s/d) registering a key with Ubuntu as far as I recall. They were working on that.
I have just installed my Nextcloud box using a pi2 but stuck a pi3 in and reinstalled using the official imageā¦ Nextcloud is up and working but of course I want to secure itā¦ I too have tried withour success to SSH into the wretched box using login/password ubuntu/ubuntu but get access deniedā¦
Hi,
same with me.
I made the transition from Pi2 to Pi3 some month ago successfully, but with no access to my system with SSH.
Since it was running nicely I thought it OK. I assumed there is a fault on my side not permitting me my system access. Then there came a power failure and my router got a new IP-address.
Now i needed access to the system to add the new IP to the list of trusted domains. NO CHANCE.
So I decided today that i had to rebuild my Nextcloud Box system from scratch.
Thatās what i did.
At the end of the installation (OOBE is the euphemism for this badly documented procedure) it tells me: "default.user@address.de can connect remotely to this device via SSH:
ssh ubuntuaccountuser@192.168.X.XXX."
At the end of the day and after much reading and googling i do not find any hint on how to do this. I have installed and used āSSH Cryptonautā but to no avail.
frustrated but optimistic
Thanks for help
I have a nextcloud box with a raspberry pi2 and I am trying the ubuntu-core image. I too could not log in.
I am trying the information from the guide posted but I have a question
Where do I find information regarding:
The ā brandā of the device. This is provided to you by the entity that created the Core system.
The ā model ā of the device. This is also provided to you by the entity that created the Core system.
I donāt remember noticing anything like that when I bought it last year.
I tried searching for this but couldnāt find anything.
I have the āvamillaā (?) nextcloud box from WD and used a ~2 yr old raspberrypi 2 that I have in case that helps with the supposed values for brand and model.
the guide seems to be a bitā¦ quirky at times. some ppl got stuck with it. especially with a rp2 model b (or such).
afaik all of them installed the nextcloudpi-image which is pretty well maintained by @nachoparker and some more guys. https://ownyourbits.com/2017/02/13/nextcloud-ready-raspberry-pi-image/
so i suggest: give it a try and iām pretty sure that youāll like it
If your still having issues I suggest you install Rasbian using NOOBS installer and then apt-get apache, php and modules.
Pop in the setup_nextcloud.php then restart and browse to mypi/setup_nextcloud.php and let it set itself up.
You may need to chown to www-data:www-data and chmod 755 but I expect it will work without it.
Never used the nextcloud image myself but used the standard stretch img with an āsshā file on the boot partition loads of times and never had issues
I tried the official NextcloudPi at first, and for me the problem wasnāt the Nextcloud stuff (works without problems) but the buggy third-party tools (especially wicd-curses for the wifi configuration). The wifi connection just didnāt connect via wicd-curses.
I was able to edit the respective config files for the wifi configuration manually via command line, but I think for user who donāt want to configure such things manually, or first of all having to find out what and where to configure it manually, it might be a bit of a burden.
Meanwhile I installed a plain Rasbian (Stretch) now and put everything else (Nextcloud, Solr, Mysql) on Docker for ARM, it works very well, including remote ssh access. First I had it on RPI2, now it runs on RPi3 without problems so far.
good boy. whereas i myself wasnāt aware that he was already looking into it. but heās a great guy and so itās not surprising that heās always aware of the probs.
hey @mathiasconradt! I just didnāt recognize you in the picture before! xD
I couldnāt reproduce your problems. Every time I test a new image I connect through wifi for convenience, so I wonder what happened in your case. In any case, wicd-curses is not ideal, but itās the best option I know for a headless setup.
I started porting Archās wifi-menu , but it is not as featureful. Also wicd it is not available in the web interface. In any case, itās added for convenience, and because it is not in the web interface it is considered a bit more āadvancedā, and for basic users I recommend just pluging in the ethernet.
Hi @nachoparker, I have no idea whatās wrong with wicd-curses. I have no problems with the wifi configuration anywhere else. wicd-curses finds the wifi network, but just doesnāt connect.
And when I edit the config files (/etc/wpa_supplicant/wpa_supplicant.conf and /etc/network/interfaces) manually, everything is stable and works fine.
