You can submit a support ticket. We can assist you more easily if you supply the following information:
What OS version are you using?
cat /etc/os-releaseWhich version of connectd is installed?
sudo dpkg --status connectd
Which connectd daemons are currently running?
ps ax | grep connectd
will show all running connectd processes.
Example:
~$ ps ax | grep connectd
19256 pts/14 S+ 0:00 sudo connectd_installer
19257 pts/14 S+ 0:00 /bin/sh /usr/bin/connectd_installer
19721 ? S 0:01 /usr/bin/connectd.x86_64-ubuntu16.04 -f /etc/connectd/services/Connectdrmt365535.conf -d /var/run/Connectdrmt365535.pid
19744 ? S 0:00 /usr/bin/connectd_schannel.x86_64-ubuntu16.04 -f /etc/connectd/schannel.conf -d /var/run/connectd_schannel.x86_64-ubuntu16.04.pid
20683 ? S 0:01 /usr/bin/connectd.x86_64-ubuntu16.04 -f /etc/connectd/services/Connectdssh22.conf -d /var/run/Connectdssh22.pid
22019 pts/2 S+ 0:00 grep --color=auto connectd
~$
Note
The name of the daemon in this example and for the rest of this post is connectd.x86_64-ubuntu16.04. That is the name of the Ubuntu daemon, but if you are using a different OS, it may have a different extension (suffix). Please check the name of your system's daemon and adjust accordingly.
Have any of these services been set up with a port or IP address override?
grep proxy /etc/connectd/services/*.conf
will show if the default port was overridden on any of these during installation, e.g.:
/etc/connectd/services/Connectd_programmer1217.conf:proxy_dest_port 1217
/etc/connectd/services/Connectd_web8080.conf:proxy_dest_port 8080
What tcp listeners (servers) are currently running?
If you run
sudo netstat -lpn | grep tcp
you will see all the running tcp servers on your device. The remote.it connectd daemon needs to communicate with a corresponding tcp listener, which we do NOT manage. If a program such as VNC or a web server is not already installed, you will have to do that yourself.
For example:
pi@raspberrypi ~$ sudo netstat -lpn | grep tcp
tcp 0 0 0.0.0.0:5900 0.0.0.0:* LISTEN 2211/vncserver-x11-
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 2200/sshd
This shows a VNC server running on port 5900 and the default ssh server running on port 22.
Please confirm:
- Is the service you're trying to connect to with remote.it (e.g. ssh) running on the default port?
- If not, did you enter the correct port during installation of remote.it?
If remote.it is installed, and you used an address like http://192.168.1.103:8080 to connect on the LAN, you did not connect using remote.it. You connected directly to the server using the explicit IP address and port.
Run the network test of the daemon:
Finally, running
/usr/bin/connectd -n
will output some useful information about your network, e.g.
$ connectd -n
Connectd built Sep 13 2018 at 11:05:25 Now Starting Up
Version 4.3 - (c)2018 remote.it All Rights Reserved
Built with BCASTER MALLOC_POOL LINUX RESOLVE BIGBUF BACKTRACE pool=262144
x86_64 Version
alloc pool
Running Network Diagnostics
---------------------------------
Checking if DNS works ... .[OK]
Checking TCP connectivity to remote.it...<oip=192.168.1.72> [OK]
Checking UDP connectivity to remote.it...
Send to 174.36.235.146:5959 [] [mip=67.170.223.206] [oport=59612 mport=59612] [preserve port]
Send to 174.36.235.146:5960 [] [mip=67.170.223.206] [oport=59612 mport=59612] [no remap] [preserve port]
Send to 69.64.84.174:5961 [] [mip=67.170.223.206] [oport=59612 mport=59612] [no remap] [preserve port different IP] [OK]
This router preserves ports, this is optimal.
This router doesn't remap new connections to new ports.
Static Pool Free
Endian : Little
SHA1 test:
passed.
RC4 test:
passed
XXTEA test:
passed.
Looks compatible.
~$
Check for any errors or warnings. Send this information to support@remote.it if the problem cannot be resolved.