Welcome to the Treehouse Community

The Treehouse Community is a meeting place for developers, designers, and programmers of all backgrounds and skill levels to get support. Collaborate here on code errors or bugs that you need feedback on, or asking for an extra set of eyes on your latest project. Join thousands of Treehouse students and alumni in the community today. (Note: Only Treehouse students can comment or ask questions, but non-students are welcome to browse our conversations.)

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and a supportive community. Start your free trial today.

APIs Build a Chatbot with Watson APIs Introducing the Watson APIs Starting Our Local Client

Running localhost doesn't appear the same as in the video.

When I run the localhost environment, my chat interface seems even more bare than the video example. Specifically, there doesn't appear to be a "what Watson understands" output in the right sidebar. https://cl.ly/1Y1V2u1N1540 I'm not sure what would account for this difference.

Mike Speev
Mike Speev
232 Points

I'm having the same issue as the poster above. My localhost environment does not populate the way it does in the video. Please help! Thanks!

Mike Speev
Mike Speev
232 Points

Figured it out!

  1. Delete the original file downloaded from the video
  2. Redownload it from the downloads
  3. Start the whole process again in terminal
  4. Include HTTP:\localhost:3000

5 Answers

Steven Sullivan
Steven Sullivan
11,616 Points

Hi Caleb.

If you haven't resolved yet, you might want to double check your .env files. Make sure to not include the <> with your workspace ID, username, or password.

Chris Rosato
Chris Rosato
500 Points

I had some trouble with this. But, I realized I was getting a 403 error. Which led me to believe my workspace connection was not getting authenticated via Bluemix. The readme file included details about the CLI for Bluemix.net. So, after using Brew to install the tool, I was able to authenticate, the 403 error was gone, and the additional "Watson understands" data populated the interface. This was not something that was seemingly covered in the video, I suppose it likely should have been. Thank you!

Tony Yoon
Tony Yoon
137 Points

FIXED! What fixed my issue was replacing the version date to 2017-05-26

Steven Sullivan
Steven Sullivan
11,616 Points

Great! Glad you resolved, Tony!

Tony Yoon
Tony Yoon
137 Points

Can you elaborate more about your solution? I'm having the same issue where I'm not connecting with Bluemix. I am not getting any data back from the service. I am getting a 400 bad request in my browser console. Please help!

Chris Rosato
Chris Rosato
500 Points

Have you set up the CLI tool (cf-cli)? I'm on a Mac and I used Brew to install. Use 'cf login' via terminal to establish a connection to the endpoint (https://api.ng.bluemix.net) and enter your credentials. Since you have a different error than I did, I'm not confident we are having the same issue, but I would check to ensure there are 1.) no syntactical errors in your .env file, 2.) have established your credentials properly on your BlueMix workspace and 3.) have really scoured the associated Readme file that you can find on GitHub here: https://github.com/watson-developer-cloud/conversation-simple.

Best of luck Tony.

Tony Yoon
Tony Yoon
137 Points

Hey Chris, thanks for the response.

No, I have not set it up through CLI tool, but isn't the instance created in the video enough? On the readme, it reads: "You can use an existing instance of the Conversation service. Otherwise, follow these steps"... these steps being basically the CLI steps you're referring to.

running this command: 'cf create-service conversation free my-conversation-service', seems just like creating an instance of the service through the Watson Dashboard (which were the steps in the video)

Chris Rosato
Chris Rosato
500 Points

I could be wrong, but when I followed the video alone, I only got as far as 403 error. The interface certainly is different as compared to when the video was produced, so it is possible other things are also different now. I believe you can use use the CLI tool to simply authenticate the service. I did not create a new service through the tool or do a push. I just used it to login and that resolved my error. Prior to that, I had wondered if my script had cross-site scripting permissions errors, but it turns out I just needed to authenticate my endpoint. I hope that helps; it sounds like you are close.

Steven Sullivan
Steven Sullivan
11,616 Points

First please try typing "node -v" in your terminal. Make sure you're not in the parent directory, but in the directory that contains all of your files (node modules, .env, app.js, etc.

What does it say?

Tony Yoon
Tony Yoon
137 Points

Hi Steven, my node version is 8.9.4