Welcome to the Treehouse Community

Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.

Start your free trial

JavaScript Build a Simple Dynamic Site with Node.js HTTP Methods and Headers Sending Content Type Headers in Node.js

Posted by George Akinian
George Akinian
17,615 Points

error: connect ETIMEDOUT for profile page

treehouse:~/workspace$ node app.js
Server running at http://<workspace-url>/
events.js:85
throw er; // Unhandled 'error' event
^
Error: connect ETIMEDOUT
at exports._errnoException (util.js:746:11)
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1010:19)

running out of ides. It connects to google api no problem. But won't connect to treehouse profile page. Any ideas why?

3 Answers

Alison Brodribb
Alison Brodribb
24,615 Points
Alison Brodribb
Alison Brodribb
24,615 Points

Hi Paul

It looks like you're not the only one with this issue - I've been having the same issue (which I initially put down to my rubbish internet connection), and there's a whole bunch of people in the below thread who are also having the same problem:

https://teamtreehouse.com/forum/node-wont-run-appjs

So it's probably a problem with treehouse rather than a problem with what you've done.

George Akinian
George Akinian
17,615 Points

Hi Alison, I written them a latter already. I urge others to do the same. To my findings this issue dates back to 19 days. This course has been in existence a lot longer. And It reaffirms my suspicion of recent internal modifications causing this incompatibility.

Antonio Jaramillo
Antonio Jaramillo
15,604 Points
Antonio Jaramillo
Antonio Jaramillo
15,604 Points

I'm getting the same error.

George Akinian
George Akinian
17,615 Points
George Akinian
George Akinian
17,615 Points

Could be that several processes are using the same port.

Try lsof -i:3000 this will show you what processes are running. And then you can kill that process with the command "kill -9 PID PID is the process id.