ASP.NET CORE 2.1 Server timeout while debugging

Question

'Error: Server timeout elapsed without receiving a message from the server.'.

I'm trying to debug some server-side code and while I do that the client gets disconnected in less than a minute.

I'm only using SignalR to communicate to clients, without controllers yet.

Is there any setting that can disable timeout or at least make it way longer than it is now?

my launchSettings.json:

{
  "iisSettings": {
    "windowsAuthentication": false,
    "anonymousAuthentication": true,
    "iisExpress": {
      "applicationUrl": "http://localhost:26793",
      "sslPort": 44386
    }
  },
  "profiles": {
    "IIS Express": {
      "commandName": "IISExpress",
      "launchBrowser": true,
      "environmentVariables": {
        "ASPNETCORE_ENVIRONMENT": "Development",
        "ASPNETCORE_HTTPS_PORT": "44386"
      }
    },
    "Api": {
      "commandName": "Project",
      "launchBrowser": true,
      "environmentVariables": {
        "ASPNETCORE_ENVIRONMENT": "Development",
        "ASPNETCORE_URLS": "https://localhost:5001;http://localhost:5000"
      }
    }
  }
}

Answer 1

Thanks to @Arhire Ionut

Here is how to increase Javascript client timeout

hubConnection.serverTimeoutInMilliseconds = 100000; // 100 second

More details here => https://github.com/aspnet/Docs/issues/6885

Answer 2

What @MahmoudFarhat mentioned in another answer is correct. But also take a look at this link and then read my comments below.

If signalR got disconnected, you should try re-establishing the connection again. The connection could drop for several other reasons, including the user switching networks. For example if the user is using a cell-phone and connected to the home/office Wifi but steps out which then connects to cellular data connection.

To reconnect you could use the following (works like a charm for me):

// re-establish the connection if connection dropped
connection.onclose(() => setTimeout(startSignalRConnection(connection), 5000));

where startSignalRConnection is :

const startSignalRConnection = connection => connection.start()
  .then(() => console.info('Websocket Connection Established'))
  .catch(err => console.error('SignalR Connection Error: ', err));

and connection is

const connection = new HubConnectionBuilder()
  .withUrl(connectionHub, options)
  .withHubProtocol(protocol)
  .build();

Answer 3

send a some message on some time interval time interval is less then serverTimeoutInMilliseconds so before time out it will send one message and connection is alive