MockTest1 issues connection and questions

Hi,

I tried the troubleshooting guide and also send an email regarding my problem, but no reply.
Sorry using the forum, this is my last resort.

First, every single day when is close to 100 min I got connection closed. I change PC, different internet providers, clean cookies, using chrome, refresh lab, refresh page and so on! What else can I do?

Also, those questions (mocktest1) I copied the kodekloud answer and test again, still gave me wrong answer.
I re-tested using those answer and same thing!

Q29
Q27
Q20

TIA

Hi @sampaiofab,
Thanks for highlighting this. We will get this checked.

Regards,

Hi @Tej-Singh-Rana

Q 20 ask to save the output in routes.txt and in the answer says save the output in route.txt

Also I still have problems with 404…

TIA

This still seems to be an issue. Every time I get to question 26, about 45 mins in, the exam connection is lost.

I cannot get thru the mock exam in its entirety with out losing the connection.

Thank you for your assistance.

Hi! I started Mock Test 1, and I can’t connect to any of the terminals. It says “connection closed”.

@Gerard-Cancino when you say “I can’t connect to any of the terminals”, what are you doing to attempt this? This is a different problem than the previous posters on this thread.

You should probably look at our troubleshooting guide, and see if anything applies to you. I just tried to access Mock Test 1, and it works for me.

If you still can’t the lab to work for you, then by all means contact support at [email protected]. But most likely the guide will get you up and working.

Hi @rob_kodekloud ! The issue happened again. The attempt is clicking on “Open An Additional Terminal” button. Following the troubleshooting guide, opening a private tab without extensions, the page returns a 404.

   GET https://terminal-5767adadc37a4472.labs.kodekloud.com/ 404 (Not Found)

I attached screenshots to the post on what the error looks like. There might be a timeout on the virtual machines to expire at a certain time.

In addition, websocket is enabled on my browser. The websocket echo returns a 200 Status Code.

Thank you for the support!

This is most often a networking problem at your end, for example, when you’re accessing the labs from work and your work network has an aggressive content filter or firewall.

Another issue, which some of the other posters on this thread have seen, is that the terminal can time out after about an hour. This is annoying, but not too bad, since while the terminal gets restarted, your “work” from the lab is still on the the terminal’s file system. The terminal “history” does disappear, but usually that’s easy enough to work around.

@rob_kodekloud I don’t believe this is caused by a network block.
2 reasons:

  1. If the connection is not established, a status code of 503 should have been returned. Instead, a 404 status code was returned, which means that connection is established, but the server cannot find the resource (terminal).
  2. The issue occurs after several minutes in. As a result, nothing is initially blocking the request.

I have noticed that the terminal has a timeout occasionally, and like you said that there is a workaround. I can continue with the exam. The timeout issue is not the same as the “Connection Closed” issue, which prevents any input into the terminal.