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!

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

General Discussion

Ting Ting Yin
PLUS
Ting Ting Yin
Courses Plus Student 361 Points

"This is a preview link for a Treehouse Workspace that is not currently active. If you are the workspace owner,

"This is a preview link for a Treehouse Workspace that is not currently active. If you are the workspace owner, you can launch it again via the Treehouse site."

Akshay Alok
Akshay Alok
7,857 Points

Hi, I was also facing the same issue. I then noticed that the code I was wishing to preview required a server to run on, which I had not initialized.

If you too are on a track learning a course which requires you to implement a code on a server, check if you haven't already initiated the server before previewing. For the people making a dynamic website using node you can probably type in:

node <javascript-code-name-that-creates-a-server>.js

on the console and then preview... Hope this helps. Btw in my case I had to run

node app.js

2 Answers

It looks to me like maybe you're looking at a workspace that has timed out. try refreshing the workspace by pressing control-r. If that doesn't work then go back to the treehouse website and re-open the workspace from there. It can be found by clicking the icon on the left of the screen that is a square with <> inside of it. You might not be able to see it unless your window is maximized.

Jay Padzensky
Jay Padzensky
4,731 Points

Hi Ting,

Sorry to hear about this. Are you still having any issues? If so, please email Support at help@teamtreehouse.com with screenshots, and details about your environment (OS, browser, their versions, private or public network) so we can start to to identify the issue.