Controller error: Gateway <ID> already connected

[checkymander]

Occasionally on gateways when I try to relaunch a gateway that was closed previously I'll receive the following error:

C3 Host: Docker container based on the mcr.microsoft.com/dotnet/core/aspnet:2.1-bionic image
Gateway Host: Separate Windows 10 1909 connected to the C3 instance
Channels: So far I've gotten the error with both OneDriveRest and Slack channels.

I've run process listings confirming that the gateway process is no longer running, and the C3 UI gateway indicator is yellow.

In response, I usually have to create a new gateway and start from scratch.

[IIDreII]

I have also received this error multiple times and can confirm that the only response I can usually end up taking is just making a new gateway.

C3 Host: Docker container based on the mcr.microsoft.com/dotnet/core/aspnet:2.1-bionic image
Gateway Host: Separate Windows 10 1909 connected to the C3 instance and in a Docker container containing the gateway
Channels: I've had the error occur with several channels, but I've even had it occur immediately with brand new gateways that have nothing attached to them yet.

Gateway|Info> Starting Gateway...
Gateway|Info> Gateway launched.
00f0:fixme:kernelbase:AppPolicyGetThreadInitializationType FFFFFFFFFFFFFFFA, 0000000000CDFE10
Gateway|Info> Starting API bridge on 192.168.2.27:2323
Gateway|Info> API bridge connection established on 192.168.2.27:2323
Gateway|Debug> Received message: {"SequenceNumber":0,"MessageType":"Error","MessageData":{"Message":"Gateway [ID: 11164652361747965922] already connected"}}
Gateway|Error> Controller error: Gateway [ID: 11164652361747965922] already connected```