Raspberry Pi Forums

Hello,

some days ago I changed the OS of my PI to Rasbian (with PIXEL).
After the installation there was no configuration offered.
As I'm used to run my PI headless I tried to access it with SSH after the installation.
Unfortunatedly I just get a reject message.

The next question here is: what are the default login credentials ?

And my last question: How can I avoid to have the GUI (PIXEL ?) started ? There is no screen attached and it will hopefully reduce the CPU load.

Regards and merry Christmas to all

pidiger wrote:Hello,

some days ago I changed the OS of my PI to Rasbian (with PIXEL).
After the installation there was no configuration offered.
As I'm used to run my PI headless I tried to access it with SSH after the installation.
Unfortunatedly I just get a reject message.

The next question here is: what are the default login credentials ?

And my last question: How can I avoid to have the GUI (PIXEL ?) started ? There is no screen attached and it will hopefully reduce the CPU load.

Regards and merry Christmas to all

SSH is now disabled by default in Raspbain Jessie since the November Release: https://www.raspberrypi.org/blog/a-secu ... ian-pixel/

as you intend to run headless over SSH, why don't you start with Raspbian Lite ??

pidiger wrote:Hello,

some days ago I changed the OS of my PI to Rasbian (with PIXEL).
After the installation there was no configuration offered.
As I'm used to run my PI headless I tried to access it with SSH after the installation.
Unfortunatedly I just get a reject message.

The next question here is: what are the default login credentials ?

And my last question: How can I avoid to have the GUI (PIXEL ?) started ? There is no screen attached and it will hopefully reduce the CPU load.

Regards and merry Christmas to all

Default login is pi and raspberry

Go to the configuration utility and set the default login to command line. Or you could just start with Lite.

Thanks for all the information.
I was not aware that SSH is now disabled by default.
And I thought that Raspbian with PIXEL is good enough for my purposes.

pidiger wrote:Thanks for all the information.
I was not aware that SSH is now disabled by default.
And I thought that Raspbian with PIXEL is good enough for my purposes.

Well if you don't want pixel then you can install lite. No VNC means you can just not have a GUI and just SSH in.

The default user is "pi" and the default password is "raspberry" for both the Pixel and Lite versions of Raspbian Jessie.

Raspbian Jessie with Pixel comes with a complete desktop graphical user interface (GUI) and many other graphical and educational applications. If you are going to run headless SSH then Raspbian Jessie Lite is probably a better choice. It is a leaner command line version of the OS with no GUI or other "fluf" that SSH users would not normally need.

To enable SSH in either version create a file named "ssh" in the /boot partition of the SD card after writing the Raspbian image to it. The /boot partition will be the only part of the card you can see from Windows or Mac computers, and it will be much smaller than the card's original size (the rest of the card is formatted with a Linux filesystem that Windows/Mac can't read).

Make sure that the filename is just ssh, and not ssh.txt, because Windows has common file extensions hidden by default and you won't see it unless you disable that feature.

If you think you might want a GUI for use with VNC, then you can use the full Raspbian Jessie with Pixel. Note that the default is for Pixel to auto-login to the pi user and start the desktop. For SSH use you will probably want to disable the Desktop/GUI auto-start, which can be done with sudo raspi-config from SSH. If you want to create your own user, disable the pi user auto-login as well (I usually do that regardless).

You will get a warning about the security risk of having SSH enabled with the default password. Heed this warning and change the password immediately, then reboot before doing anything else. The password can be changed with sudo passwd pi, or by using the configuration utility (sudo raspi-config).

If you power down the Pi without a proper shutdown before you have successfully logged in using SSH, you will have to re-image the card and start over. Powering down the system before a successful SSH login interrupts the process of enabling SSH and breaks it. It's never a good idea to power down a computer without a proper shutdown anyway.

Merry Christmas/Happy Holidays to all my fellow Raspberry Pi users!

Dear Forum,

On my recent (December 2016) RPI, ssh is disabled by default, as discussed.
I followed the instructions to put an ssh file (no extensions) with "touch ssh" in the /boot partition to gain ssh access. After inserting the SD in the RPI, and connecting to my laptop directly with the ethernet cable, I can ping the RPI fine:

kvan637@sc-phy-324060 ~]$ ping 169.254.19.99
PING 169.254.19.99 (169.254.19.99) 56(84) bytes of data.
64 bytes from 169.254.19.99: icmp_seq=1 ttl=64 time=0.078 ms
64 bytes from 169.254.19.99: icmp_seq=2 ttl=64 time=0.080 ms
64 bytes from 169.254.19.99: icmp_seq=3 ttl=64 time=0.092 ms
64 bytes from 169.254.19.99: icmp_seq=4 ttl=64 time=0.071 ms
64 bytes from 169.254.19.99: icmp_seq=5 ttl=64 time=0.043 ms
64 bytes from 169.254.19.99: icmp_seq=6 ttl=64 time=0.088 ms
64 bytes from 169.254.19.99: icmp_seq=7 ttl=64 time=0.084 ms
64 bytes from 169.254.19.99: icmp_seq=8 ttl=64 time=0.083 ms
64 bytes from 169.254.19.99: icmp_seq=9 ttl=64 time=0.080 ms
64 bytes from 169.254.19.99: icmp_seq=10 ttl=64 time=0.075 ms
64 bytes from 169.254.19.99: icmp_seq=11 ttl=64 time=0.081 ms
64 bytes from 169.254.19.99: icmp_seq=12 ttl=64 time=0.080 ms
64 bytes from 169.254.19.99: icmp_seq=13 ttl=64 time=0.079 ms
^C
--- 169.254.19.99 ping statistics ---
13 packets transmitted, 13 received, 0% packet loss, time 12267ms
rtt min/avg/max/mdev = 0.043/0.078/0.092/0.011 ms

but I STILL cannot ssh into the RPI with the default account and password:

[kvan637@sc-phy-324060 ~]$ ssh pi@169.254.19.99
pi@169.254.19.99's password:
Permission denied, please try again.

Any suggestions?

Thank you.
Kasper

kaspervw wrote:...
After inserting the SD in the RPI, and connecting to my laptop directly with the ethernet cable...

Try connecting your Raspberry Pi to your router.

Connecting it directly to your computer requires several extra steps which I can't remember now (too much holiday cheer). You need static IP addresses and ICS, and I can't remember the rest. Anyway, if you want to wait around a bit more, I'm sure someone else will give you a more coherent answer about direct connections, but if you don't want to wait, then connect your Pi to your router with an Ethernet cable and it should work.

Try login as root instead.

I think I need help, before I kill either myself or this nice Pi3 I've just bought.
Using my W10 PC I have downloaded and installed jessie lite on a micro SD card using Win32DiskImager.
I created a directory /boot and, within it, created a file called ssh.txt and then removed the extension so that I have a file called "ssh".
I put the SD card in the Pi3 and plugged it into my router using an ethernet cable
I can see the Pi with address 192.168.1.15 and I can ping it from the PC
When I open putty and ask to SSH into 192.168.1.15 I get "Network Error: Connection refused".
Same with telnet from DOS.
Huh??
So I turned my Avast off and tried again - problem remains.
If I had the money, and the space for one, I would go and buy an HDMI screen, but I have neither.
I have had other Pis connected on my system in the past with no problem (they are no longer here).
So what stupid mistake am I making?

jellis wrote:I think I need help, before I kill either myself or this nice Pi3 I've just bought.
Using my W10 PC I have downloaded and installed jessie lite on a micro SD card using Win32DiskImager.
I created a directory /boot and, within it, created a file called ssh.txt and then removed the extension so that I have a file called "ssh".
I put the SD card in the Pi3 and plugged it into my router using an ethernet cable
I can see the Pi with address 192.168.1.15 and I can ping it from the PC
When I open putty and ask to SSH into 192.168.1.15 I get "Network Error: Connection refused".
Same with telnet from DOS.
Huh??
So I turned my Avast off and tried again - problem remains.
If I had the money, and the space for one, I would go and buy an HDMI screen, but I have neither.
I have had other Pis connected on my system in the past with no problem (they are no longer here).
So what stupid mistake am I making?

Don't create the directory 'boot'. The files goes in the same directory as start.elf.

OMG, life-saver!!
Thank you ShiftPlusOne!!!