clears throat
Thanks for your patience Martin. This was totally a ID 10 T operator error.
PORT 5000 was for some reason being eaten by another process. I changed that and everything stabilised. Nodes are being picked up. For those who follow this path.
check you /var/log/tyk-gateway.stderr file
if you are getting something that looks like this:
'time="May 14 08:08:22" level=info msg="Setting up Server"
time="May 14 08:08:22" level=info msg="--> Standard listener (http)"
time="May 14 08:08:22" level=info msg="Registering node."
time="May 14 08:08:22" level=error msg="Request failed: Get 1/register/node: unsupported protocol scheme \"\""
time="May 14 08:08:27" level=error msg="Request failed: Get 1/register/node: unsupported protocol scheme \"\""
time="May 14 08:08:32" level=info msg="Starting Poller"
time="May 14 08:08:32" level=error msg="Request failed: Get 1/register/node: unsupported protocol scheme \"\""
time="May 14 08:08:37" level=error msg="Request failed: Get 1/register/node: unsupported protocol scheme \"\""
time
you most likely have something fighting with tyke on the ports.
check the processes you have running and on which ports. I would recommend you stop the tyk-gateway and tyk-dashboard services first just so the results are definitive.
[ec2-user@ip-XXX-XXX-XXX-XXX log]$ netstat -lntu
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:10000 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:27017 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:6379 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:48748 0.0.0.0:* LISTEN
tcp 0 0 :::111 :::* LISTEN
tcp 0 0 :::22 :::* LISTEN
tcp 0 0 :::3000 :::* LISTEN
tcp 0 0 :::49316 :::* LISTEN
tcp 0 0 :::5000 :::* LISTEN
udp 0 0 0.0.0.0:111 0.0.0.0:*
udp 0 0 0.0.0.0:626 0.0.0.0:*
udp 0 0 172.31.28.181:123 0.0.0.0:*
udp 0 0 127.0.0.1:123 0.0.0.0:*
udp 0 0 0.0.0.0:123 0.0.0.0:*
udp 0 0 127.0.0.1:659 0.0.0.0:*
udp 0 0 0.0.0.0:10000 0.0.0.0:*
udp 0 0 0.0.0.0:68 0.0.0.0:*
udp 0 0 0.0.0.0:50250 0.0.0.0:*
udp 0 0 :::111 :::*
udp 0 0 :::626 :::*
udp 0 0 :::41029 :::*
created a new port for the gateway (5000 on this install is used by something else for some reason). Update tyk.conf and tyke_analytics.conf
restarted the services and everything came together really well.
Finally just check your rewrite rules on NGINX to make sure they are pointing everything in the right direction.