bobcat 300 miner error from packet_router - h2 protocol error

[kallisti5]

I've been seeing the attached error for a few days on my Bobcat 300 miner:

STARTING GATEWAY-RS
2024-02-29T13:43:34.785903Z  INFO run: gateway_rs::server: starting server version=1.3.0 key=XXX
2024-02-29T13:43:34.786148Z  INFO run: gateway_rs::region_watcher: starting default_region=US915
2024-02-29T13:43:34.786389Z  INFO run: gateway_rs::beaconer: starting beacon_interval=21600 disabled=false uri=http://mainnet-pociot.helium.io:9080/
2024-02-29T13:43:34.786632Z  INFO run: gateway_rs::gateway: starting listen="0.0.0.0:1680"
2024-02-29T13:43:34.786793Z  INFO run:run: gateway_rs::packet_router: starting uri=http://mainnet-router.helium.io:8080/
2024-02-29T13:43:34.787342Z  INFO run: gateway_rs::api::server: starting listen=127.0.0.1:4467
2024-02-29T13:43:39.908342Z  INFO run: gateway_rs::gateway: new packet forwarder client mac=XXX addr=127.0.0.1:44490
2024-02-29T13:43:40.372490Z  WARN run:run: gateway_rs::packet_router: failed to reconnect err=crypto error: signature error
2024-02-29T13:43:44.826316Z  INFO run: gateway_rs::gateway: received uplink downlink_mac=XXX uplink=@396191599 us, 904300000 MHz, Sf10bw125, snr: 6.8, rssi: -96, len: 24 region=US915
2024-02-29T13:43:47.343481Z  INFO run: gateway_rs::region_watcher: fetched config region_params pubkey=XXX uri=http://mainnet-config.helium.io:6080/ default_region=US915 region=US915
2024-02-29T13:43:47.344196Z  INFO run: gateway_rs::beaconer: next beacon time beacon_time=2024-02-29 15:15:06.0 +00:00:00
2024-02-29T13:43:47.344320Z  INFO run: gateway_rs::beaconer: region updated region="US915"
2024-02-29T13:43:47.346276Z  INFO run: gateway_rs::gateway: region updated region="US915"
2024-02-29T13:43:48.383979Z  INFO run: gateway_rs::service::conduit: initialized session module="beaconer" session_key=XXX
2024-02-29T13:43:53.350532Z  INFO run:run: gateway_rs::service::conduit: initialized session module="packet_router" session_key=XXX
2024-02-29T13:49:00.814944Z  WARN run: gateway_rs::beaconer: ingest error err=Service(Rpc(Status { code: Unknown, message: "h2 protocol error: error reading a body from connection: connection reset", source: Some(hyper::Error(Body, Error { kind: Io(Kind(ConnectionReset)) })) }))
2024-02-29T13:49:00.825093Z  WARN run:run: gateway_rs::packet_router: router error err=Service(Rpc(Status { code: Unknown, message: "h2 protocol error: error reading a body from connection: connection reset", source: Some(hyper::Error(Body, Error { kind: Io(Kind(ConnectionReset)) })) }))
2024-02-29T13:49:06.383882Z  INFO run:run: gateway_rs::service::conduit: initialized session module="packet_router" session_key=XXX
2024-02-29T13:49:06.956543Z  INFO run: gateway_rs::service::conduit: initialized session module="beaconer" session_key=XXX

Miner status:

{
  "ota_version": "1.0.3.18",
  "region": "us915",
  "frequency_plan": "us915",
  "animal": "XXX",
  "pubkey": "XXX",
  "miner": {
    "State": "running",
    "Status": "Up 12 minutes",
    "Names": [
      "/miner"
    ],
    "Image": "quay.io/team-helium/miner:gateway-latest",
    "Created": 1709214214
  },
  "ports": {
    "192.168.10.22:22": "open",
    "XXX:22": "closed/timeout"
  },
  "private_ip": "192.168.10.22",
  "public_ip": "XXX",
  "temp0": "28 °C",
  "temp1": "28 °C",
  "timestamp": "2024-02-29 13:55:40 +0000 UTC",
  "errors": ""
}

[madninja]

This looks like it's having issues connecting or staying connected to the packet router? A deployment was done this week; can you see if you're still having this issue?