RisingHF light hotspot h2 protocol error: error reading a body from connection: timed out

[cappuccino5]

helium_gateway --version helium_gateway 1.2.1

2024-03-07T08:28:35.065439Z 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: timed out", source: Some(hyper::Error(Body, Error { kind: Io(Kind(TimedOut)) })) }))

Problem: The hotspot cannot be queried on the chain. Failed to query the hotspot information,I already have 10+ hotspots happend this condtion, I should why todo? please tell me.

https://app.hotspotty.net/hotspots/13QgEoA21cAUavhU1Rtn7kpysEqmPVuqbDxEV8hZLXGYueFm7vk/rewards

[cappuccino5]

https://app.hotspotty.net/hotspots/13QgEoA21cAUavhU1Rtn7kpysEqmPVuqbDxEV8hZLXGYueFm7vk/rewards there be one hotsopt alreadly have information.

But I can't find the information about another hotspot. I also have 10+ hotspots that have been added recently and I can't find the information about them.

for example： https://app.hotspotty.net/hotspots/14r6ymFdCZtQ1TEsMnmJuX9JP5RkQ3Xf5y6yq3SsFEGZsEckx1J/info

[madninja]

• Try upgrading to gateway-rs 1.3.0. See if that helps with the networking errors
• I don't know what you're saying about "can't find information about them. Please add more details as it seems unrelated to the h2 errors

[cappuccino5]

Fri Mar 8 02:47:19 2024 daemon.info helium_gateway[1373]: 2024-03-08T02:47:19.877526Z 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: timed out", source: Some(hyper::Error(Body, Error { kind: Io(Kind(TimedOut)) })) })) Fri Mar 8 02:47:26 2024 daemon.info helium_gateway[1373]: 2024-03-08T02:47:26.689125Z INFO run:run: gateway_rs::packet_router: initialized session session_key=13ScWPk8ZnfBkpKdFdVmybdDkyTRqKwWhj3czrU2WLMyE1xaYvc Fri Mar 8 03:03:44 2024 daemon.info helium_gateway[1373]: 2024-03-08T03:03:44.197513Z 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: timed out", source: Some(hyper::Error(Body, Error { kind: Io(Kind(TimedOut)) })) })) Fri Mar 8 03:03:51 2024 daemon.info helium_gateway[1373]: 2024-03-08T03:03:51.207212Z INFO run:run: gateway_rs::packet_router: initialized session session_key=141ZtnLdsZ6tz8pKoQLHCZseuEgpvami4mtmbdWykideoAsJ6bF root@rhf2s027:~# logread -e helium_gateway Fri Mar 8 02:47:19 2024 daemon.info helium_gateway[1373]: 2024-03-08T02:47:19.877526Z 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: timed out", source: Some(hyper::Error(Body, Error { kind: Io(Kind(TimedOut)) })) })) Fri Mar 8 02:47:26 2024 daemon.info helium_gateway[1373]: 2024-03-08T02:47:26.689125Z INFO run:run: gateway_rs::packet_router: initialized session session_key=13ScWPk8ZnfBkpKdFdVmybdDkyTRqKwWhj3czrU2WLMyE1xaYvc Fri Mar 8 03:03:44 2024 daemon.info helium_gateway[1373]: 2024-03-08T03:03:44.197513Z 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: timed out", source: Some(hyper::Error(Body, Error { kind: Io(Kind(TimedOut)) })) })) Fri Mar 8 03:03:51 2024 daemon.info helium_gateway[1373]: 2024-03-08T03:03:51.207212Z INFO run:run: gateway_rs::packet_router: initialized session session_key=141ZtnLdsZ6tz8pKoQLHCZseuEgpvami4mtmbdWykideoAsJ6bF Fri Mar 8 03:20:08 2024 daemon.info helium_gateway[1373]: 2024-03-08T03:20:08.517535Z 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: timed out", source: Some(hyper::Error(Body, Error { kind: Io(Kind(TimedOut)) })) })) Fri Mar 8 03:20:13 2024 daemon.info helium_gateway[1373]: 2024-03-08T03:20:13.936150Z INFO run:run: gateway_rs::packet_router: initialized session session_key=14ZwudEjpAGus5tubRuLvuQoGXxg8uFTzPgtt5PW3Vu91YiHuDi Fri Mar 8 03:27:30 2024 daemon.info helium_gateway[1373]: 2024-03-08T03:27:30.680136Z INFO run: gateway_rs::region_watcher: fetched config region_params pubkey=137oJzq1qZpSbzHawaysTGGsRCYTXG1MiTMQNxYSsQJp4YMDdN8 uri=http://mainnet-config.helium.io:6080/ default_region=EU868 region=EU868 I have updated to gateway-rs 1.3.0 and still have the same question

[cappuccino5]

see image :

[cappuccino5]

2 questions:

1. The hotspot has been added to the chain and IOT revenue has been generated, but the hotspot map cannot be found on the chain.
2. The hotspot has been on the chain for more than a week, and the map on the chain can be found, but there is no profit.