Docker Tyk 1.8 Quickstart - Unable to access developer portal


#1

Imported Google Group message. Original thread at: https://groups.google.com/forum/#!topic/tyk-community-support/Jg2pVBq-HuY Import Date: 2016-01-19 21:25:52 +0000.
Sender:Jonathan Hamilton.
Date:Wednesday, 30 September 2015 19:42:03 UTC+1.

Hello!

I am excited to try out Tyk! But I have an issue that I would appreciate some help with. TIA

On an Azure Ubuntu VM I have successfully started up the containers, configured the gateway via the portal etc. However, I am unable to try to reach the Developer Portal, I’ve tried a couple permutations and can’t seem to get it resolved. Any suggestions?

  1. Default setup
    –> got “error”: “Authorization field missing”

  2. Setting the IP as part of ./setup.sh xxx.xxx.xxx.xxx
    –> page not found

  3. (longshot) Overriding hostname on tyk_analytics.conf
    –> page not found

From scanning the other messages, it appears that my issue is due to not having a domain setup for a hosted deployment. Is this still correct? Is quick setup only intended for local deployment (or a configured domain for hosted deployment)?

Thanks again, great looking product that I am eager to put through the paces.
Jonathan


#2

Imported Google Group message.
Sender:Martin Buhr.
Date:Thursday, 1 October 2015 03:35:30 UTC+1.

Hi Jonathan,
Yes, I think that would work (changing windows hosts file to point to VM), I wouldn’t include the IP after the QuickStart, this is just so the script can do the necessary API calls to bootstrap an empty stack (add a user etc) and it should be able to auto detect things in a Linux environment.
If you are using vagrant you could just follow our vagrant QuickStart where you install all the components yourself.
Cheers,
Martin


#3

Imported Google Group message.
Sender:Jonathan Hamilton.
Date:Wednesday, 30 September 2015 19:53:15 UTC+1.

Hi Jonathan,
That is correct - the QuickStart is specifically configured for a local deployment to get you up and running with the stack.
It also specifically uses the tyk.docker domain name to set up the portal and host routing.
To get things working for you, you will need to override the templates stored in the tyk_nginx container (suggest you look at the repo to see what files those are: https://github.com/lonelycode/tyk-host-manager-docker
The files are in the templates folder - you’ll see how the templates specify the domain name used to handle routing.
od suggest running the QuickStart locally to get a feel for things, then take a look at the wider docs (and the dockerfiles / repositories) to see how things can be set up. The host manager is the only one highly specialised.
We really don’t recommend using the QuickStart in alive environment, simply due to redis and mango being ephemeral :-/
Let me know how you get on :slight_smile:
Cheers,
Martin


#4

Imported Google Group message.
Sender:Martin Buhr.
Date:Wednesday, 30 September 2015 20:18:39 UTC+1.

Thanks for the prompt reply Martin! That makes sense.

Apologies that this is a silly follow up question, but I want to make sure I understand the local setup - as my networking skills are a bit weak & it’s not the same as just installing SW on a laptop!

In a “local” setup on a Windows laptop running Ubuntu VM w/ Docker + Tyk containers, then do I update the Windows hosts file to point to the IP of the VM (say 10.10.10.42)? And do I need to use the IP of the VM in quickstart script (i.e. ./setup.sh 10.10.10.42)?

10.10.10.42 testorg.tyk.docker
10.10.10.42 test-api.testorg.tyk.docker

Or are you saying I need to install a GUI / browser in my Ubuntu VM so that I can truly keep as localhost using 127.0.0.1?

Thanks again.

  • show quoted text -

#5

Imported Google Group message.
Sender:Jonathan Hamilton.
Date:Thursday, 1 October 2015 03:35:30 UTC+1.

Hi Jonathan,
Yes, I think that would work (changing windows hosts file to point to VM), I wouldn’t include the IP after the QuickStart, this is just so the script can do the necessary API calls to bootstrap an empty stack (add a user etc) and it should be able to auto detect things in a Linux environment.
If you are using vagrant you could just follow our vagrant QuickStart where you install all the components yourself.
Cheers,
Martin