# Knowledge Base

A set of common issues and solutions

# Networking Stack

### Idle Time-Outs

#### Issue Overview

In some instances, the default time out for the Signal-R portal circuit may require increasing. This issue is caused by the default time out windows imposed by the Nginx reverse proxy.

#### Symptoms

- You routinely find the application shows "Attempting to connect to the server" without being idle for a reasonable period of time.
- You find the portal "flashes" a lot while working.

#### Solution

1\. Connect to the Docker host.

2\. Modify the Nginx configuration and add the following.

```bash
location / {
    proxy_pass http://cms_portal:8080;
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "upgrade";
    proxy_set_header Host $host;

    # Important for SignalR long-lived connections:
    proxy_read_timeout 3600s;
    proxy_send_timeout 3600s;
}
```

3\. When complete. Restart the Nginx container.

```bash
docker compose exec nginx nginx -t && docker compose exec nginx nginx -s reload
```