DiscordSocketClient throws every few hours an exception

[Suiram1701]

I've running a Discord.NET bot on a Raspberry PI and noticed in the logs that aroud every three hours the gateway disconnects with an exception und reconnects a few seconds later.

It disconnects with two possible exceptions:

1. A WebSocketException with the message WebSocket connection was closed and the stacktrace

System.Net.WebSockets.WebSocketException (0x80004005): WebSocket connection was closed
 ---> System.Net.WebSockets.WebSocketException (0x80004005): The remote party closed the WebSocket connection without completing the close handshake.
   at System.Net.WebSockets.ManagedWebSocket.ThrowEOFUnexpected()
   at System.Net.WebSockets.ManagedWebSocket.EnsureBufferContainsAsync(Int32 minimumRequiredBytes, CancellationToken cancellationToken)
   at System.Runtime.CompilerServices.PoolingAsyncValueTaskMethodBuilder`1.StateMachineBox`1.System.Threading.Tasks.Sources.IValueTaskSource.GetResult(Int16 token)
   at System.Net.WebSockets.ManagedWebSocket.ReceiveAsyncPrivate[TResult](Memory`1 payloadBuffer, CancellationToken cancellationToken)
   at System.Runtime.CompilerServices.PoolingAsyncValueTaskMethodBuilder`1.StateMachineBox`1.System.Threading.Tasks.Sources.IValueTaskSource<TResult>.GetResult(Int16 token)
   at System.Threading.Tasks.ValueTask`1.ValueTaskSourceAsTask.<>c.<.cctor>b__4_0(Object state)
--- End of stack trace from previous location ---
   at Discord.Net.WebSockets.DefaultWebSocketClient.RunAsync(CancellationToken cancelToken)
   at Discord.ConnectionManager.<>c__DisplayClass29_0.<<StartAsync>b__0>d.MoveNext()

2. A GatewayReconnectException with the message Server requested a reconnect and stacktrace

Discord.WebSocket.GatewayReconnectException: Server requested a reconnect
   at Discord.ConnectionManager.<>c__DisplayClass29_0.<<StartAsync>b__0>d.MoveNext()

In the second one I see that the server want's to reconnect but shouldn't Discord.NET handle instead of throwing an exception? Or do I have to fix something in configuration?

Here is also a screenshot from two of these events in the logs (on Gateway: (null) the excpetions occurr):