# GraphQL: Timeout waiting for session from proxy server **URL:** \ **Category:** Troubleshooting\ **Created:** [August 4, 2025, 4:36pm UTC](https://forum.remote.it/t/graphql-timeout-waiting-for-session-from-proxy-server/1401 "2025-08-04T16:36:27Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![izou3](https://avatars.discourse-cdn.com/v4/letter/i/e47774/32.png) [@izou3](https://forum.remote.it/u/izou3)\ **Post date:** [August 4, 2025, 4:36pm UTC](https://forum.remote.it/t/graphql-timeout-waiting-for-session-from-proxy-server/1401/1 "2025-08-04T16:36:27Z")
Hello, When trying to ssh to my remote raspberry pi 4 device, I keep getting this error GraphQL: Timeout waiting for session from proxy server I can verify that the device is online, has a -50dBM signal strength, and connected to the WiFi network. I do not get this issue and am able to connect properly for another RPI4 connected to the same WiFi network. I have tried the following troubleshooting: 1. remoteit logs on the raspberry pi indicate it receives the connection but it times out for whatever reason 2. I am able to ssh to this remote raspberry pi with no issues using RPI connect which I believe uses a similiar protocol as remoteit ([https://www.raspberrypi.com/software/connect/](https://www.raspberrypi.com/software/connect/)) 3. I have a total of 5 RPIs. Some I can ssh with remote it successfully or some I recieve the timeout error noted above. 4. I have tried restarting the Pi, restarting the WiFi network, etc. but have not had an success. Does any have a similar experience or help to debug this issue? Thanks ---
**Author:** ![bstrech](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.remote.it/bstrech/32/266_2.png) [@bstrech](https://forum.remote.it/u/bstrech)\ **Post date:** [August 4, 2025, 11:12pm UTC](https://forum.remote.it/t/graphql-timeout-waiting-for-session-from-proxy-server/1401/2 "2025-08-04T23:12:51Z")
Hello, Do all of the RPis have exactly the same spec? Can you tell me if you duplicated the SD card (specifically did you install remote.it on each device individually?) Do the devices have different host names on the network? The Raspberry Pi Connect Software is VNC and not using the same way of connect to devices as remote.it uses. You can try running the following commands on a device which you are having issues with. This one will check communications with our servers: ```auto /usr/share/remoteit/connectd -n ``` This command will help us determine if there are routing issues and will take a while to run. ```auto /usr/share/remoteit/connectd -nat ``` You can DM me the responses. ---
**Author:** ![izou3](https://avatars.discourse-cdn.com/v4/letter/i/e47774/32.png) [@izou3](https://forum.remote.it/u/izou3)\ **Post date:** [August 5, 2025, 11:23pm UTC](https://forum.remote.it/t/graphql-timeout-waiting-for-session-from-proxy-server/1401/3 "2025-08-05T23:23:24Z")
Hi Brenda, thanks for the prompt responses and your help! To address your questions, yes all the RPis have the same spec and OS and remoteit was installed on each device individually. There are a total of 5 devices connected to the same network and 2 of the 5 have no issues but the other 3 shows the online status on remoteit but I get the Timeout error in RemoteIT when I attempt to initiate an SSH connection. I have tried other services like Raspberry Pi Connect and Tailscale for a remote SSH connection to these devices without any issue. I have attached the output to your commands and there does not seem to be an issues or differences of these command outputted on the Pis that can intiate an SSH connection through RemoteIT. I have also attached the logs of the RemoteIT systemd services. AS you can see, it accepts an incoming connection request but just seems to timeout despite the strong signal strength. _ **re@raspberrypi:~ $ sudo /usr/share/remoteit/connectd -n** _ Connectd built Sep 26 2024 at 19:28:36 Now Starting Up Version 5.4.0.1727378915 - (c)2023 remot3.it, Inc. All Rights Reserved Built with aarch64-linux-gnu tools NATPMP BCASTER LINUX RESOLVE BIGBUF BACKTRACE NATIVE\_MALLOC AARM64 Version ## Running Network Diagnostics Checking if DNS works … [OK] Checking TCP connectivity to api.remote.it…\ [OK] Checking UDP connectivity to remote.it… Send to 52.38.107.102:5959 [5] [mip=128.61.164.187] [oport=44061 mport=26792] Send to 52.38.107.102:5960 [5] [mip=128.61.164.187] [oport=44061 mport=26792] [no remap] Send to 54.218.6.237:5961 [5] [mip=128.61.164.187] [oport=44061 mport=26792] [no remap] Send to 52.38.107.102:5962 [5] [mip=128.61.164.187] [oport=44061 mport=26792] [no remap] Send to 54.218.6.237:5963 [5] [mip=128.61.164.187] [oport=44061 mport=26792] [no remap] [OK] Check WS server Send to 52.38.107.102:46211 [ws] [mip=35.90.145.169] [oport=46211 mport=46211] [ok] Sanity Check Firewall Rules… Check FE servers Checking chat 52.38.107.102:5959 [mip=128.61.164.187] [oport=47938 mport=6006] [ok] Checking chat 52.38.107.102:5960 [mip=128.61.164.187] [oport=47938 mport=6006] [ok] Checking chat 54.218.6.237:5959 [mip=128.61.164.187] [oport=47938 mport=6006] [ok] Checking chat 54.218.6.237:5960 [mip=128.61.164.187] [oport=47938 mport=6006] [ok] Checking chat 52.38.107.102:5959 [mip=128.61.164.187] [oport=47938 mport=6006] [ok] Checking chat 52.38.107.102:5960 [mip=128.61.164.187] [oport=47938 mport=6006] [ok] Checking chat 54.218.6.237:5959 [mip=128.61.164.187] [oport=47938 mport=6006] [ok] Checking chat 54.218.6.237:5960 [mip=128.61.164.187] [oport=47938 mport=6006] [ok] Check CHAT servers Checking chat 44.236.76.190:443 [mip=128.61.164.187] [oport=47938 mport=6006] [ok] Checking chat 44.236.76.190:5960 [mip=128.61.164.187] [oport=47938 mport=6006] [ok] Checking chat 44.236.76.190:5961 [mip=128.61.164.187] [oport=47938 mport=6006] [ok] Checking chat 44.239.243.92:443 [mip=128.61.164.187] [oport=47938 mport=6006] [ok] Checking chat 44.239.243.92:5960 [mip=128.61.164.187] [oport=47938 mport=6006] [ok] Checking chat 44.239.243.92:5961 [mip=128.61.164.187] [oport=47938 mport=6006] [ok] Checking chat 44.240.35.27:443 [mip=128.61.164.187] [oport=47938 mport=6006] [ok] Checking chat 44.240.35.27:5960 [mip=128.61.164.187] [oport=47938 mport=6006] [ok] Checking chat 44.240.35.27:5961 [mip=128.61.164.187] [oport=47938 mport=6006] [ok] Firewall test discovered 0 ports blocked Checking if NAT-PMP Router is found…[NOT FOUND] This router doesn’t remap new connections to new ports. Endian : Little HKDF SHA512 test: Passed HKDF SHA1 test: Passed ChaCha20\Poly1305 test: Passed SHA1 test: Passed. XXTEA test: Passed. Looks compatible. _ **re@raspberrypi:~ $ sudo /usr/share/remoteit/connectd -nat** _ Connectd built Sep 26 2024 at 19:28:36 Now Starting Up Version 5.4.0.1727378915 - (c)2023 remot3.it, Inc. All Rights Reserved Built with aarch64-linux-gnu tools NATPMP BCASTER LINUX RESOLVE BIGBUF BACKTRACE NATIVE\_MALLOC AARM64 Version Running Nat UDP Reply Timeout Checker Checking 1 seconds on port 44470 (52.38.107.102)[good reply at 1 seconds] Checking 2 seconds on port 33623 (52.38.107.102)[good reply at 2 seconds] Checking 4 seconds on port 38755 (52.38.107.102)[good reply at 4 seconds] Checking 8 seconds on port 48721 (52.38.107.102)[good reply at 8 seconds] Checking 16 seconds on port 56945 (52.38.107.102)[good reply at 16 seconds] Checking 32 seconds on port 37686 (52.38.107.102)[good reply at 32 seconds] Checking 64 seconds on port 35924 (52.38.107.102)[good reply at 64 seconds] Checking 128 seconds on port 42141 (52.38.107.102)[good reply at 128 seconds] reply time \>=250seconds (measured 128) maximum test reached, exiting. Running UDP Nat MAP Timeout Checker Setting up NAT mapping _ **re@raspberrypi:~ $ sudo systemctl status remoteit@9d3bfc9.service** _ ● remoteit@9d3bfc9.service - Remote tcp connection service 9d3bfc9 Loaded: loaded (/lib/systemd/system/remoteit@.service; enabled; preset: enabled) Active: active (running) since Tue 2025-08-05 17:42:35 EDT; 5min ago Main PID: 746 (connectd) Tasks: 1 (limit: 3920) CPU: 392ms CGroup: /system.slice/system-remoteit.slice/remoteit@9d3bfc9.service └─746 /usr/share/remoteit/connectd -d /run/remoteit-9d3bfc9.pid -e bWF4X2RlcHRoIDM1CmFwcGxpY2F0aW9uX3R5cGUgMzUKcHJveHlfZGVzdF9pcCAxMjcuMC4wLjEKbWFud\> Aug 05 17:42:37 raspberrypi Connectd[746]: Waiting for IP address Aug 05 17:42:39 raspberrypi Connectd[746]: Process Identifier 0xf8c2bfba Aug 05 17:42:39 raspberrypi Connectd[746]: initialize TCP target 127.0.0.1 port 65535 Aug 05 17:42:42 raspberrypi Connectd[746]: 52276\> sending req auth to 52.38.107.102:5959 (WSE-!-0-FOff) Aug 05 17:42:42 raspberrypi Connectd[746]: 52277\> Status redirect to 44.239.243.92:5960 Aug 05 17:42:42 raspberrypi Connectd[746]: 52277\> sending req auth to 44.239.243.92:5960 (WSE-!-0-FOff) Aug 05 17:42:42 raspberrypi Connectd[746]: 52278\> NAT type selected at 3 with natmap 80 Aug 05 17:42:42 raspberrypi Connectd[746]: Server Connection changed to state 4 Aug 05 17:42:42 raspberrypi Connectd[746]: Server Connection changed to state 5 Aug 05 17:42:42 raspberrypi Connectd[746]: Connected to server is 44.239.243.92:5960 _ **re@raspberrypi:~ $ sudo systemctl status remoteit@4414058.service** _ ● remoteit@4414058.service - Remote tcp connection service 4414058 Loaded: loaded (/lib/systemd/system/remoteit@.service; enabled; preset: enabled) Active: active (running) since Tue 2025-08-05 17:42:35 EDT; 5min ago Main PID: 744 (connectd) Tasks: 1 (limit: 3920) CPU: 439ms CGroup: /system.slice/system-remoteit.slice/remoteit@4414058.service └─744 /usr/share/remoteit/connectd -d /run/remoteit-4414058.pid -e bWF4X2RlcHRoIDM1CmFwcGxpY2F0aW9uX3R5cGUgMjgKcHJveHlfZGVzdF9pcCAxMjcuMC4wLjEKbWFud\> Aug 05 17:42:42 raspberrypi Connectd[744]: Server Connection changed to state 5 Aug 05 17:42:42 raspberrypi Connectd[744]: Connected to server is 44.240.35.27:5960 Aug 05 17:46:17 raspberrypi Connectd[744]: Session Request grant OK, incoming session from remot3.it ID USERNAME Aug 05 17:46:26 raspberrypi Connectd[744]: Session Request grant OK, incoming session from remot3.it ID USERNAME Aug 05 17:46:35 raspberrypi Connectd[744]: Session Request grant OK, incoming session from remot3.it ID USERNAME Aug 05 17:46:43 raspberrypi Connectd[744]: Session Request grant OK, incoming session from remot3.it ID USERNAME Aug 05 17:47:36 raspberrypi Connectd[744]: Session from USERNAME Closed Aug 05 17:47:45 raspberrypi Connectd[744]: Session from USERNAME Closed Aug 05 17:47:54 raspberrypi Connectd[744]: Session from USERNAME Closed Aug 05 17:48:02 raspberrypi Connectd[744]: Session from USERNAME Closed _ **re@raspberrypi:~ $ sudo systemctl status remoteit-refresh.service** _ ○ remoteit-refresh.service - remoteit configuration refresh service Loaded: loaded (/lib/systemd/system/remoteit-refresh.service; enabled; preset: enabled) Active: inactive (dead) since Tue 2025-08-05 17:42:38 EDT; 17min ago Duration: 3.262s Process: 686 ExecStart=/usr/share/remoteit/refresh.sh boot (code=exited, status=0/SUCCESS) Main PID: 686 (code=exited, status=0/SUCCESS) CPU: 1.073s Aug 05 17:42:35 raspberrypi systemd[1]: Started remoteit-refresh.service - remoteit configuration refresh service. Aug 05 17:42:35 raspberrypi remoteit[706]: Updating remote.it configuration. Aug 05 17:42:35 raspberrypi refresh.sh[714]: curl: (6) Could not resolve host: install.remote.it Aug 05 17:42:35 raspberrypi remoteit[770]: Fail to update remote.it configuration with curl command failure. Aug 05 17:42:36 raspberrypi refresh.sh[686]: Start Services Aug 05 17:42:38 raspberrypi systemd[1]: remoteit-refresh.service: Deactivated successfully. Aug 05 17:42:38 raspberrypi systemd[1]: remoteit-refresh.service: Consumed 1.073s CPU time. ---
**Author:** ![bstrech](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.remote.it/bstrech/32/266_2.png) [@bstrech](https://forum.remote.it/u/bstrech)\ **Post date:** [August 11, 2025, 2:55pm UTC](https://forum.remote.it/t/graphql-timeout-waiting-for-session-from-proxy-server/1401/4 "2025-08-11T14:55:45Z")
> [@izou3](#): > > Aug 05 17:42:35 raspberrypi refresh.sh[714]: curl: (6) Could not resolve host: install.remote.it Based on this line here, there seems to be a problem with DNS. While the Raspberry pi can get to IP addresses for presense there seems to be some other issues with DNS. In this case, check if there is an override the network settings for DNS on the pi itself or check your router.