Hello! I’ll be brief. I have the remoteit server running on a Raspberry PI that sits behind a NAT. I can connect through SSH with putty to it, no problem. The thing is I have another server running on it that I’d wish to connect to, but I can’t do that through remoteit. It’s a component that is controllable from a browser application, so I’ve tried the xming way, but it is horribly laggy - actually it is unusable.
So my question is - what solution would I have in this case? Some tunneling application?
Why cannot you connect to the other server? Is it a service on the the pi or some other local resource to the pi? Remote.it should be able to do both out of the box.
It’s a server on the pi. To be more specific, this is a Chilipeppr server running on the pi which is used to connect to serial device (so a local service). This works on a different port than the generated [host]:[port] we use to connect through SSH.
The NAT was introduced by my ISP. Before that, I used to connect to the PI, find out my public IP address, and just connecto that Chilipeppr server using [publicIP]:[port] (with the port forwarding set up in the router).
I’m not sure how remoteit can facilitate my connection to the chilipeppr server. I’m thinking it cannot.
I’m not sure how chilipeppr works, but if it is running from your local machine (IE connections from their UI is actually running in the javascript code on your browser directly to the endpoint) then it should work fine with the desktop.
Not sure what remote.it package you are using on the PI or if your using the remote.it desktop, but just create a remote.it TCP service that points to your chilipeppr server port, then use the desktop to create an on demand connection on the local port you want and point chilipeppr to this.
Their documentation is not obvious with a 5 min look, so I am assuming alot.
after looking at the github repo looks like it is running at http://localhost:8989, so create an TCP or http endpoint pointing to 8989, http might be better or not in this case.
you can even create the local socket to be 8989 with the desktop on your connecting machine.
Then you just need to add service(s) in Remote.It pointing to the port(s) you need. For example, if the server is a webserver hosting HTTP. See this article on adding services. Support Services