Having set up Tyk Gateway for the first time (deploying using Docker containers onto Mesosphere DC/OS) and configured a Redis master/slave setup for the Gateway + Dashboard to use, I can login to the Dashboard after running the bootstrap shell script to create the initial admin user, but the ‘Nodes and Licenses’ section shows ‘No nodes running’
From my reading, this often happens when Redis is not available from either the Gateway or the Dashboard, but both seem to be the case here - e.g. here’s the whole list of keys from the Redis:
Nope - everything is running across the Mesos cluster manager. Almost everything is working now - e.g. I can see the Pump moving Redis records to both ElasticSearch and MongoDB.
The Dashboard is still elusive. Do I need to tell the Tyk Gateway that the Dashboard exists in order to ‘register’ with it? I thought it was enough for both the Gateway and Dashboard to use the same Redis instance (i.e. discovery by proxy)
If I want to deploy API’s using .json files, can I still use the Dashboard to manage users / permissions / quotas?
The bootstrap was run against the public AWS ELB hostname of the Dashboard, and that came back with the default user/pass test123 which worked fine.
I noticed that ‘node_secret’ was not set on the Tyk Gateway node, so I added it, rebuilt and then saw the following network traffic… the Gateway is still failing to register…
If you ran the dashboard bootstrap against the public hostname and set a hostname for the dashboard, then it will have bound to that and the gateway will need to use that hostname to access the gateway.
Can you share your tyk_analytics.conf? Specifically the bit about the dashboard hostname.