tyk portal missing

Support Setting up Tyk
1

Imported Google Group message. Original thread at: Redirecting to Google Groups Import Date: 2016-01-19 21:34:08 +0000.
Sender:Damoure.
Date:Wednesday, 9 December 2015 13:20:18 UTC.

Hi,

I had installed Tyk Docker, and i have the problem with the portal.

I followed the tutorial and just changed the portal domain name.

Any idea ?

Regards

Adamou

2

Imported Google Group message.
Sender:Martin Buhr.
Date:Wednesday, 9 December 2015 13:29:27 UTC.

Hi,

Have you set up some hosts entries for the domain you changed:

And when you ran this command you changed the portal URL from www.tyk-portal-test.com to your custom domain?

Did you run this command more than once?

Does the Tyk Gateway work as expected? (is it proxying requests?)

And now when you say “You have a problem with the portal” could you please be a little more specific:
What response are you getting in the browser exactly?
Are you trying to access the portal with the domain you defined? (You can’t use the drop-down link in docker)
Thanks,
Martin

3

Imported Google Group message.
Sender:Damoure.
Date:Wednesday, 9 December 2015 13:56:04 UTC.

Hi Martin,
thanks for your quick replay !

Have you set up some hosts entries for the domain you changed: ==> yes i do it

And when you ran this command you changed the portal URL from www.tyk-portal-test.com to your custom domain? ==> yes i do it

Did you run this command more than once? ==> yes (twice), but i stop && remove all docker containers

Does the Tyk Gateway work as expected? (is it proxying requests?) ==> yes it works fine

What response are you getting in the browser exactly? ==> No error, empty view
Are you trying to access the portal with the domain you defined? (You can’t use the drop-down link in docker) ==> yes
Have I miss some things ?

Thanks
Adamou

  • show quoted text -
4

Imported Google Group message.
Sender:Damoure.
Date:Wednesday, 9 December 2015 16:41:58 UTC.

When i try to acess to the portal, here is the error that i have in the Tyk Gateway container logs:

level=error msg=“http: proxy error: dial tcp: lookup tyk_dashboard.tyk_dashboard.docker on 172.17.42.1:53: no such host”

  • show quoted text -
5

Imported Google Group message.
Sender:Martin Buhr.
Date:Wednesday, 9 December 2015 17:06:53 UTC.

Yeah I managed to replicate it. Are you on OSX?

Our docker compose is optimised for linux docker installations. The OSX compatibility needs work because of how internal DNS binding and IPs are assigned. It’s quite frustrating because it changes on each reload.

Because Tyk Docker runs on one host, it also runs everything through port 80, which means it needs to have internal two-way visibility between the two instances, which docker doesn’t support out of the box, so you need this dnsdock workaround or ambassador pattern - still working on the latter, which should fix things.

Can I suggest, if you are testing on OSX to use the Vagrant tutorial instead?

Cheers,
Martin

6

Imported Google Group message.
Sender:Damoure.
Date:Wednesday, 9 December 2015 19:49:21 UTC.

I had installed Tyk on Ubuntu 15.04

Thanks
Adamou

  • show quoted text -
7

Imported Google Group message.
Sender:Martin Buhr.
Date:Wednesday, 9 December 2015 19:54:50 UTC.

Hi,
You installed Tyk in docker on Ubuntu 15.04?
What version of Docker are you using?
The issue you were facing is because Tyk can’t resolve the hostname of the dashboard docker image, you can actually get it all working without docker compose, it’s just that docker compose doesn’t support dual-way linking yet.
Did you get everything to work in the end?
Many thanks,
Martin

8

Imported Google Group message.
Sender:Damoure.
Date:Wednesday, 9 December 2015 20:36:28 UTC.

Hi Martin,

I had installed docker 1.9 on ubutu vivid .

Ok, will try it without docker compose and will come back to you.

Thanks very much
Adamou

  • show quoted text -
9

Imported Google Group message.
Sender:Martin Buhr.
Date:Wednesday, 9 December 2015 20:50:20 UTC.

I’ll take another look at our docker install to make sure things are more stable, this DNS workaround is obviously not a viable or reliable alternative… Am open to advice :wink:
If you are using the docker containers files individually, take a look at how they are linked, the rule is:

  • Tyk gateway needs to see the dashboard if you want to proxy the portal via it
  • Tyk dashboard needs to see the gateway always (otherwise keys can’t be created)
  • both need to see Redis and mongo always
    That means that the Tyk.conf and tyk_analytics.conf files need to reflect the above rules in both containers
    another option is to use the dashboard on port 3000 in which case you need to enable custom domains in the dashboard conf file.
    The last thing we could try is to fix the docker compose setup so that it binds the DNSdock container to the actual IP address of the container and make it assign the correct DNS to each linked container so that the internal lookups work.
    The default setup QuickStart has been tested against Docker 1.9 on Ubintu, so I’m not sure what’s going on there.
    Will investigate further.
    Cheers,
    Martin
10