# I get a connection error “Remote.It connected, but there is no service running on the remote machine. “

**URL:** <https://forum.remote.it/t/i-get-a-connection-error-remote-it-connected-but-there-is-no-service-running-on-the-remote-machine/1166>\
**Category:** Troubleshooting\
**Created:** [August 26, 2024, 6:54pm UTC](https://forum.remote.it/t/i-get-a-connection-error-remote-it-connected-but-there-is-no-service-running-on-the-remote-machine/1166 "2024-08-26T18:54:40Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**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 26, 2024, 6:54pm UTC](https://forum.remote.it/t/i-get-a-connection-error-remote-it-connected-but-there-is-no-service-running-on-the-remote-machine/1166/1 "2024-08-26T18:54:40Z")

</div>

What happened and how do I fix this?

---

<div class="post-metadata">

**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 26, 2024, 6:59pm UTC](https://forum.remote.it/t/i-get-a-connection-error-remote-it-connected-but-there-is-no-service-running-on-the-remote-machine/1166/2 "2024-08-26T18:59:19Z")

</div>

According to the error message, the Remote.It daemon was able to connect, but the service on the device either isn’t running or it is not running on the configured port.

In this case, the troubleshooting would be as follows.  
Verify that the service reachable and listening on the configured port device locally.  
You can do this by using netstat or telnet from the device command line. If you are using a Pi, this should work with default tools installed. (Replace the port in this example (22) with the port you have configured in Remote.It for the service.

```auto
curl -v telnet://127.0.0.1:22

```

If you get a timeout, then the device is not listening at that address and port.  
Do the following:

- Check that the service is enabled or still running
- Check that the service is listening on the port

These things usually resolve the issue.
