Have you deployed Tyk? Post your API here (if appropriate), we're keen to know who's using the software

Support Setting up Tyk
1

Imported Google Group message. Original thread at: Redirecting to Google Groups Import Date: 2016-01-19 21:44:51 +0000.
Sender:Martin Buhr.
Date:Thursday, 14 August 2014 09:29:21 UTC+1.

As the authors of an open source project, we have little idea of what people are doing with it, we’d therefore be really keen to know what and how you’re using tyk, and if there’s anything we can do to help?

2

Imported Google Group message.
Sender:Burhaan Targett.
Date:Wednesday, 17 September 2014 09:21:39 UTC+1.

Yes please. Help. I really like Tyk more so that any of the competitors (WSO2, ApiAxle, etc). I’m not a linux guru, but getting this installed was really easy all - saying that means alot because I’m more of a windows guy. I am having some issues with the core and the dashboard kinda highlighted it. I get this constantly on tyk itself:

Error trying to get all keys:
ERR Client sent AUTH, but no password is set

I think its something to do with Redis, but that setup appears to be correct. I’ve tried setting/removing the password on Redis with no effect. I think because of this, the dashboard wont log me in, and on that I get:
ERRO[0082] Error trying to get value:
ERRO[0082] ERR Client sent AUTH, but no password is set
ERRO[0082] Key not found

I’ve been battling with this for a few days, we’d really like to get into the product and possible buy the license, but we cant do that if we cant get it running… Can you help?
I’ve attached the config for tyk and tyk_analytics

3

Imported Google Group message.
Sender:Martin Buhr.
Date:Wednesday, 17 September 2014 09:36:23 UTC+1.

@Burghaan - this is a known bug that is actually fied in the master branch (Allow passwordless redis connection by alexwhitman · Pull Request #6 · TykTechnologies/tyk · GitHub). You can get around this in your installation by simply ensuring that your Redis database has a password set. this is pretty straightforward, simply edit the redis.conf
file and uncomment this line:

masterauth

And replace with an actual password, then make sure your tyk and dashboard files are using this password too and the error should go away. This will be fixed in a future release.

Let me know how it goes!

Cheers,
Martin

4

Imported Google Group message.
Sender:Burhaan Targett.
Date:Wednesday, 17 September 2014 10:25:27 UTC+1.

Awesome. That did the trick. Thanks so much.

5