Installed WebIDE- but cannot access it

[cappy2112]

I've installed the webID packages as directed here
http://learn.adafruit.com/webide/installation

When I try connecting using my IP address followed by :3000, in Chrome
http://learn.adafruit.com/webide/getting-started

Chrome cannot see the webserver
Oops! Google Chrome could not connect to 192.168.0.28:3000

I'm able to SSH to the rpi using this IP address.

I've followed the directions- I could use some help.

Thanks

[Ron2222]

I am also having the same problem. I followed Afafruit directions but when tried http://192.168.1.xx:3000.local or http://192.168.1.xx.local "Error can not find the server" I tried Chrome,Firefox, and IE10. maybe the server is down. could someone check it and let us know?

[DaveC3]

Same issue here. I posted the issue a few day ago.

[dremo]

Try connecting on the default web port 80. The tutorial says to connect to 3000 but I think WebIDE starts on port 3000 only if port 80 is already in use.


I've used http://192.168.1.xx:80 or http://raspberrypi.local:80




Drew

[JohnDee]

Ditto - I have the same connection problem. 'Tried the :80 port, too. 'Tried installing with the one line command script? and also manually.

Either way the sever installs and starts (or so it reports) but I can't get a WEBide connection through FF or Chrome, either using IP or raspberrypi.local address although I CAN access the Rspi and use SSH and VNC from Win 7 PC successfully.

Anyone know where are the configuration / log files to try to troubleshoot this problem?

C'mon back...

Hello?

[Syn7]

I had the same issue. 80 instead of 3000 did the trick.

I didn't see it in the tutorial, and excuse this suggestion if it is and I simply missed it, but that is mos def worthy of note in the tutorial. Of course my first move, after running out of my own ideas, was to come here and search webIDE and viola! But you can save people a lot of time by editing that in.

That being said, the tutorials are much appreciated and very helpful. I like how they don't hand hold you so much that you don't learn anything on your own, but still hand hold you enough to get through it in a reasonable amount of time.

Thanx.

S.


PS, why 80 and 3000? And what else would be using 80?

[cappy2112]

Try connecting on the default web port 80. The tutorial says to connect to 3000 but I think WebIDE starts on port 3000 only if port 80 is already in use.


I've used http://192.168.1.xx:80 or http://raspberrypi.local:80

Drew

:80 worked for me too.
The tutorial really needs to be updated to be more clear

[Syn7]

PS, why 80 and 3000? And what else would be using 80?

Anyone?

I don't need a full explanation. A few keywords or a link would help.

Thanx

[adafruit_support_mike]

RFC 2616 (Hypertext Transfer Protocol -- HTTP/1.1) (http://www.ietf.org/rfc/rfc2616.txt), page 12:

HTTP communication usually takes place over TCP/IP connections. The
default port is TCP 80 [19], but other ports can be used.

and the '[19]' bit is a reference to RFC 1700 (ASSIGNED NUMBERS) (http://www.ietf.org/rfc/rfc1700.txt), page 20:

www-http 80/tcp World Wide Web HTTP
www-http 80/udp World Wide Web HTTP

Every protocol has an assigned number. It makes it easier for machines to establish connections with each other. At the machine-connection level, "I want a webpage" translates to "make a connection on port 80 then send an HTTP request". You can do it manually from a terminal:

Code: Select all

funhouse:~ mike$ telnet info.yawp.com 80
Trying 63.144.68.172...
Connected to info.yawp.com.
Escape character is '^]'.
GET http://info.yawp.com/misc/ HTTP\1.1


then press RETURN twice. The server will send you the HTML for that URL.

The 'port 3000' thing is there to avoid port collisions on machines that are already running a webserver for other purposes. We don't want to clobber an existing service in the process of setting up a new one.

On a unix system, only the root user can launch services whose port number is less than 1024, but in most server daemons the root process gives up most of its access privilieges as soon as it opens the port. Ports above 1024 are available to anyone, so when you run a specialized webserver you generally choose a port number somewhere in the thousands.

Port 8000 is the traditional fallback for people who want to run, say, a secure server alongside the regular one, and we don't want to clobber that either.

[Syn7]

Awesome. Thanx.