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

General Discussion

"Communication Problem"

Hi Guys ,

While taking the code challenge in JavaScript Basics , I keep getting "communication problem" message.

If any one, who has encountered similar issues in the past ? Also, any suggestions ?

Looking forward to hearing from you guys !

Thanks,

Kashif

I am having the same issue, but the code challenge in Database Foundation... Very frustrating. I need to retake the challenge at least 4-5 times each challenge before I can proceed to the next lesson without errors...

2 Answers

Hi Shinsuke !

I agree its super frustrating.Hopefully will get some sort of solutions shortly.

Will let you know, if I happen to receive any solutions via an email from Tree house.

Thanks for turning up the volume !

Nathan Williams
seal-mask
.a{fill-rule:evenodd;}techdegree
Nathan Williams
Python Web Development Techdegree Student 6,851 Points

Hey folks,

Sorry for the trouble!

It looks like there was an issue with CCs this morning. Some recent changes have been causing a little bit of instability, and it's pretty hard to track down exactly where it's coming from, but we're working on it.

Everything's stable at the moment, and we're keeping an eye on things, but if you're ever wondering if there's a problem, you can check our status page, and you can always feel free to contact our support team if you're having problems that aren't listed on the status page.

Regards,

Nathan W

Thanks for the update Nathan!