Imported Google Group message.
Date:Friday, 15 May 2015 20:09:18 UTC+1.
We'll need to see the log output to really diagnose this, and it's a great way to see what's going wrong - you can see the logs in real time by running:
sudo docker logs -f tyk_gateway
(you may need to replace tyk_gateway with whatever is running the 'tyk' command (i.e. not the dashboard).
If you run that command you'll see Tyk's output (the gateway, which is also the service that creates the keys and assigns policies). To clarify, The dashboard and portal just remote into the gateway and use it's API to do things like create keys and register policies, so the workhorse for the operational stuff is at the gateway level, then the dashboard and portal are "business logic" that string things together.
The key you created as a developer, if you deleted the policy, that key will be defunct. Although if when you did a lookup and got an error on the results screen then that key may never have been created properly.
Now I would suggest watching the logs while doing the following:
1. Create a new policy
2. Sign up as a developer
3. Attempt to access an API with the key
When you do (1) the gateway shoudl reload, when you do #2 you should see a key request created message and the key that was created. What would be really interesting to see is what happens with (3) the gateway will tell you what's up
- show quoted text -