Skip to content

Controlling timeout / unresponsive terminal #50

@yeban

Description

@yeban

Hi. I have set up a command-line bootcamp server (commit: bee2f50) for an online course. I am finding that the terminal pane becomes unresponsive after a while. The setup includes Nginx which proxies the connection to docker-browser-server. I am not using ssl.

Reasoning that a network timeout might be causing the terminal to become unresponsive, I increased proxy_read_timeout setting of Nginx to to 3,600 (1 hr). It helped to an extent. But the terminal pane does not stay responsive for 1 hr (in one test the terminal stayed responsive for ~25 minutes).

I was wondering if I might just be experiencing a 'network blip' causing the websocket connection to drop, or if it is something that can be controlled in the setup. I will try a few other Nginx timeout options, but just wanted to check with you first. A colleague was wondering if docker-browser-server uses ssh to run commands in the docker container and if so the timeout we might be seeing is coming from the ssh server. Do you think that is possible? Anything else I should consider?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions