Page 1 of 1

Connection from Client to indigo server remotly

PostPosted: Tue Jun 20, 2017 6:00 pm
by Radjin
I installed the client on my laptop, can connect via SSH and Back to My Mac, I forwarded the two ports, 1176 and 8176 to my server however I cannot connect with the indigo client.

Am I missing a step?

Re: Connection from Client to indigo server remotly

PostPosted: Tue Jun 20, 2017 6:32 pm
by johnfdl
Just to be sure we eliminate the obvious.....
  1. You've started Indigo first on the server?
  2. You haven't changed the default ports?
  3. You don't have a firewall blocking the traffic?
  4. From the client, you are entering the external IP address of your router?
  5. Does it work if you connect when the client and server are on the same local network?

Re: Connection from Client to indigo server remotly

PostPosted: Wed Jun 21, 2017 6:46 am
by Radjin
johnfdl wrote:
Just to be sure we eliminate the obvious.....
  1. You've started Indigo first on the server? Yes
  2. You haven't changed the default ports? Correct
  3. You don't have a firewall blocking the traffic? Correct
  4. From the client, you are entering the external IP address of your router? Host name (xxx.com)
  5. Does it work if you connect when the client and server are on the same local network? Yes

Re: Connection from Client to indigo server remotly

PostPosted: Wed Jun 21, 2017 7:09 am
by Different Computers
For the server address, are you using the external IP address or some dynamic DNS address? The prism reflector address does NOT work for the client to the server. This bit me in the ass 6 months or so ago.

Re: Connection from Client to indigo server remotly

PostPosted: Wed Jun 21, 2017 3:20 pm
by Radjin
I run a small web server and can access the website perfectly. So using that addresss to get to my server the client at my remote location tells me 'cannot connect to the indigo server, check my internet connection'. I don't use the prism reflector

Re: Connection from Client to indigo server remotly

PostPosted: Wed Jun 21, 2017 3:38 pm
by matt (support)
The Mac GUI Indigo client connects to port 1176 (by default), which is the native Indigo Server (which is not HTTP based).. Indigo Touch and Web browsers use the Indigo HTTP Web Server which is on port 8176 by default.

They are both just normal TCP sockets, so setting up TCP forwarding for those sockets is all you have to do. If it isn't working, then the problem is either the port forwarding isn't set up correctly or the Mac's firewall is blocking incoming connection.

Re: Connection from Client to indigo server remotly

PostPosted: Wed Jun 21, 2017 3:40 pm
by kwijibo007
Radjin wrote:
[*]From the client, you are entering the external IP address of your router? Host name (xxx.com)


For the sake of troubleshooting, have you tried entering the IP address directly? Maybe some strange DNS issue is causing the issue?


Sent from my iPad using Tapatalk

Re: Connection from Client to indigo server remotly

PostPosted: Wed Jun 21, 2017 5:31 pm
by Radjin
Of all things it turned out to be the VPN I use when traveling. Why it would be a problem I am not sure as all other services work perfectly.

Thanks everyone for the help.

Re: Connection from Client to indigo server remotly

PostPosted: Wed Jun 21, 2017 5:42 pm
by johnfdl
Radjin wrote:
[*]From the client, you are entering the external IP address of your router? Host name (xxx.com)

And here I thought it was the 'xxx.com' hostname you were putting in. Some spicy material on that hostname.. :twisted:

Re: Connection from Client to indigo server remotly

PostPosted: Wed Jun 21, 2017 6:47 pm
by Radjin
Next time I will use 555.com

Re: Connection from Client to indigo server remotly

PostPosted: Thu Jun 22, 2017 6:39 am
by johnfdl
Much more refined content on 555.com

Re: Connection from Client to indigo server remotly

PostPosted: Thu Jun 22, 2017 6:50 am
by Different Computers
I'm reminded of a story where (I think it was) Microsoft wrote a Win NT setup manual that used "http://example.com" throughout, and the copy editors never once checked to see what was at example.com or who owned it.

example.com ended up getting a lot of weird traffic.