Remote Desktop to a Raspberry PI through your web browser

[windy54]

Hi ,

I have just tried following the above instructions and when I get to

sudo wget https://raw.githubusercontent.com/raspb ... er/vncboot --no-check-certificate

I get the following error:

pi@small4gb /etc/init.d $ sudo wget https://raw.githubusercontent.com/raspb ... er/vncboot --no-check-certificate

--2016-01-08 16:23:20-- https://raw.githubusercontent.com/raspb ... er/vncboot
Resolving raw.githubusercontent.com (raw.githubusercontent.com)... 62.252.172.241
Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|62.252.172.241|:443... connected.
GnuTLS: A TLS fatal alert has been received.
GnuTLS: received alert [0]: Close notify
Unable to establish SSL connection.

I am guessing this a problem with the link, I have had search through github and on
https://github.com/raspberrypilearning/ ... lob/master

found a file vncboot which I have downloaded, so I tried
sudo wget https://github.com/raspberrypilearning/ ... er/vncboot --no-check-certificate

but this gave me a 404 error.

I am going to carry on following the instructions using the file I downloaded and will post a response if it works.

I am using a 4GB image of jessie which I found in the forum, I want to update our schools raspberry PIs to the latest image but on the existing 4GB cards. I do not see why this will cause the problem I have seen.

Any ideas as to what the problem is?

[W. H. Heydt]

Please don't shout. (That is, please don't use all caps in your subject line. Thank you.)

[topguy]

There are no link to instructions "above".

If I click on the first link in your post I see the script, I could have saved that to a file or just used cut&paste to in a ssh (or putty) terminal to transfer it to a Pi. "wget" is just a commandline way of transferrring a file from a web-server, you can do it any other way if the result is the same.

[W. H. Heydt]

I am using a 4GB image of jessie which I found in the forum, I want to update our schools raspberry PIs to the latest image but on the existing 4GB cards. I do not see why this will cause the problem I have seen.

Any ideas as to what the problem is?

The current release of Jessie expands to 4.3GB. This causes problems with some unzip programs and it will NOT fit on a 4GB SD card.

[B.Goode]

Steve

There are several other occurences of this error in the forums, none with convincing solutions.

A couple of thoughts -

Maybe the stripped-down version the OS is missing some component needed to interwork github?

Why is it necessary to invoke the wget of the script with sudo? Maybe the certificate or whatever doesn't play nicely as root?

[hippy]

Resolving raw.githubusercontent.com (raw.githubusercontent.com)... 62.252.172.241
Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|62.252.172.241|:443... connected.
GnuTLS: A TLS fatal alert has been received.
GnuTLS: received alert [0]: Close notify
Unable to establish SSL connection.

There was another user having problems resolving github sites with Virgin Media as their ISP, were getting Virgin Media IP addresses back instead of correct ones. Sounds like the same problem -

viewtopic.php?f=28&t=131570

[B.Goode]

PS: works OK for me using 'full' Raspbian Jessie using TalkTalk as the ISP from the other side of Leicester -

Code: Select all

pi@raspberrypi ~ $ wget https://raw.githubusercontent.com/raspberrypilearning/teachers-classroom-guide/master/vncboot --no-check-certificate
--2016-01-08 16:58:30--  https://raw.githubusercontent.com/raspberrypilearning/teachers-classroom-guide/master/vncboot
Resolving raw.githubusercontent.com (raw.githubusercontent.com)... 185.31.19.133
Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|185.31.19.133|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 889 [text/plain]
Saving to: ‘vncboot’

vncboot             100%[=====================>]     889  --.-KB/s   in 0s

2016-01-08 16:58:35 (2.18 MB/s) - ‘vncboot’ saved [889/889]

This is the content of the vncboot script:

Code: Select all

pi@raspberrypi ~ $ cat vncboot
## BEGIN INIT INFO
# Provides: vncboot
# Required-Start: $remote_fs $syslog
# Required-Stop: $remote_fs $syslog
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: Start VNC Server at boot time
# Description: Start VNC Server at boot time.
### END INIT INFO

#!/bin/sh
#/etc/init.d/vncboot

export USER='pi'

eval cd ~$USER

# Check the state of the command: this'll either be start or stop
case "$1" in
  start)
    # if it's start, then start vncserver using the details below
    echo "Starting VNC for $USER..."
    su $USER -c '/usr/bin/tightvncserver :1 -geometry 1280x800'
    echo "...done (VNC)"
    ;;
  stop)
    # if it's stop, then just kill the process
    echo "Stopping VNC for $USER "
    su $USER -c '/usr/bin/tightvncserver -kill :1'
    echo "...done (VNC)"
    ;;
  *)
    echo "Usage: /etc/init.d/vncserver {start|stop}"
    exit 1
    ;;
esac
exit 0
pi@raspberrypi ~ $

[windy54]

Thanks for all the replies.

The only reason the original post was in capitals is because I coped the heading from the raspberry pi page
http://www.raspberrypi.org/guides/teach ... r-guide.md which happens to be in capital letters.

I have followed the instructions on a full jessie download and can't get it to work.

however my provider is virgin media so I will follow the link given in one of the responses and see if that corrects it.


thanks again

Steve

[windy54]

So it looks like my problem with the wget is down to virgin media,

If I follow the instructions in the link

Anyway, I did find a resolution by editing /etc/resolvconf.conf

There is a commented out line name_servers, simply uncomment this and put in the ip address of a dns, e.g. 8.8.8.8 for google.

The wget commands now work, however I can't connect via a browser. I can connect via VNC.

However in order to connect via VNC I had to use simplesi.net/auto-install-x11vnc and not the instructions in the post.

I think I will start with a clean image and try again.

Has anyone followed the instructions on the raspberry pi site and connected via browser to a PI?

again, thanks for replies

[windy54]

I have gone back to the wheezy image, ran sudo apt-get update and upgrade and then followed the instructions.

tightvnc now runs and I can log into it from my MacBook on 192.168.0.14:5901

When I try and log in via the browser I using 192.168.0.14:5901 an error message "safari Can't open the page, because the server dropped the connection is displayed.

If I try 192.168.0.14 the error message is can't connect to the server.

when I look at the vnc log on my PI it is full of lines as below

• 09/01/16 15:07:23 Got connection from client 192.168.0.8
  09/01/16 15:07:23 rfbProcessClientProtocolVersion: not a valid RFB client
  09/01/16 15:07:23 Client 192.168.0.8 gone
  09/01/16 15:07:23 Statistics:
  09/01/16 15:07:23 framebuffer updates 0, rectangles 0, bytes 0

so now it is a case of googling what a RFB client is

I am using Safari version 9 on my macbook which should be compatible and I have tried chrome on my phone.
At least I have made some progress in installing tightvncserver on wheezy, which implies there is something different in Jessie.

Steve

[B.Goode]

Steve. I haven't tried it, and this is beyond the limits of my competence, but I'm wondering whether modifying stuff in init.d is the right way to manage a system that relies on systemd? Maybe the doc hasn't been updated for the move from Wheezy to Jessie?

I have tried to look at the github repo for the resource to see if this has been flagged as an Issue, but I can't trace a linked repo...

(On reflection, the TLS error you were seeing was a probably a consequence of the broken name resolution.)

[windy54]

So I took my wheezy image into school and gave it to one of my code club members to try out.

Using a cable connection rather than wifi and Internet explorer it worked.

I do not believe the cable connection has anything to do with it but it is a difference.

I could not try internet explorer at home due to lack of a working Windows PC.

We managed to log into the raspberry PI from another machine.

At some point I would like to get it working with Jessie.

[B.Goode]

I was just looking for something else entirely, and found this had been raised as an Issue: https://github.com/raspberrypi/documentation/issues/273

(I haven't tested the proposed solution.)