Kong 2.0 Compatibility Support

[thangaraja]

Kong 2.0 is released. Has anyone tested? Any known issues? Any update on when Konga will officially support Kong 2.0?

[gettoarun]

Doesn't work. Fails with HTTP 500/Internal Server Error and only an empty error object.

{"error":{}}

[larsnaesbye]

That's weird. We're running Kong 2.0.0 and the latest Konga...

[larsnaesbye]

But I suppose the Konga 2 repo is a WIP thing specifically for Kong 2?

[uleodolter]

I have kong 2.0.1 and 0.14.7 running, seems to work, maybe not all kong features are implemented but works for my configuration.

[jschirrmacher]

Works here (Kong 2.0.1 and Konga 0.14.7) as well, but doesn't offer all Plugins available in Kong, e.g. the ACME plugin, which would be extremely helpful.

[larsnaesbye]

Have any of you tried Konga 2?

[javaChip56]

Not sure if the question is specifically asking for 2.0, but I have Konga 0.14.7 and Kong 2.0.1 running in Docker containers. Apart from IP Restrictions, everything else work fine.

[larsnaesbye]

@javaChip56 Have you tried Konga 2 if it works as well?

[javaChip56]

@larsnaesbye I'm actually not aware that there already is a Konga 2. Mind if you can share the repo for that?

[larsnaesbye]

Sure. https://github.com/pantsel/konga2-ui and https://github.com/pantsel/konga2-server

I have not tried it myself.

[narinkaew]

I got an errors too (Kong 2.0.1 and Konga 0.14.7). I executed with docker image.

When create connection, got an error

Then inspect, got the message Error: got 503 response 503 Service Unavailable Failed to connect to server localhost

I got response from "http://localhost:8001" properly

Any suggest?

Thanks in advance Narin

[javaChip56]

@larsnaesbye I will try to check that out. Although I'm quite surprised to see that there's a v2.0. I didn't even see a v1.0.

@narinkaew are both Konga and Kong running in their respective containers? You may want to try using 172.17.0.1 instead of localhost to connect Konga to Kong.

[daddydrac]

I am having same issue; would like to know how to fix plz. Do I need to edit my etc/hosts file?

When I click activate I get this in my network tab:

Request URL: http://localhost:1337/kong?connection_id=2
Request Method: GET
Status Code: 500 Internal Server Error
Remote Address: [::1]:1337
Referrer Policy: no-referrer-when-downgrade

error: {errno: "EHOSTUNREACH", code: "EHOSTUNREACH", syscall: "connect", address: "172.17.0.1", port: 8001}
errno: "EHOSTUNREACH"
code: "EHOSTUNREACH"
syscall: "connect"
address: "172.17.0.1"
port: 8001

[daddydrac]

Also not sure if this matters, but on initial log in, there is no default connection:

[javaChip56]

@joehoeller are both Kong and Konga running in a docker container on your local host?

[narinkaew]

@javaChip56 Thanks for information but My Konga still can't connect to kong even though open browser with http://localhost:8001 is work perfectly.

Here is the new network name 'kong-net' Network : kong-net There are 3 container in the network

• kong-database (postgres), 172.24.0.2
• kong, 172.24.0.3
• konga, 172.24.0.4

I tried connect konga to kong with difference url but all can't connect.

Here is my docker-compose.yml

• Docker 19.03.8, build afacb8b
• Kong 2.0.1
• Konga 0.14.7

version: "3.7"

#volumes:
#  kong_data: {}

networks:
 kong-net:
    name: kong-net

services:

  #######################################
  # Postgres: The database used by Kong
  #######################################
  kong-database:
    image: postgres:9.6
    container_name: kong-database
    restart: always
    networks:
      - kong-net
    environment:
      POSTGRES_USER: kong
      POSTGRES_PASSWORD: kong
      POSTGRES_DB: kong
      #POSTGRES_HOST_AUTH_METHOD: trust
    ports:
      - "5432:5432"
    #volumes:
    #  - ./pg_data:/var/lib/postgresql/data
    healthcheck:
      test: ["CMD", "pg_isready", "-U", "kong"]
      interval: 30s
      timeout: 30s
      retries: 3

  #######################################
  # Kong database migration
  #######################################
  kong-migration:
    image: kong:latest
    command: kong migrations up
    networks:
      - kong-net
    restart: on-failure
    environment:
      KONG_DATABASE: postgres
      KONG_PG_HOST: kong-database
      KONG_CASSANDRA_CONTACT_POINTS: kong-database
      KONG_PG_USER: kong
      KONG_PG_PASSWORD: kong
      KONG_PG_PORT: 5432
    depends_on:
      - kong-database

  #######################################
  # Kong: The API Gateway
  #######################################
  kong:
    image: kong:latest
    restart: always
    container_name: kong
    networks:
      - kong-net
    environment:
      KONG_DATABASE: postgres
      KONG_PG_HOST: kong-database
      KONG_CASSANDRA_CONTACT_POINTS: kong-database
      KONG_PG_USER: kong
      KONG_PG_PASSWORD: kong
      KONG_PROXY_ACCESS_LOG: /dev/stdout
      KONG_ADMIN_ACCESS_LOG: /dev/stdout
      KONG_PROXY_ERROR_LOG: /dev/stderr
      KONG_ADMIN_ERROR_LOG: /dev/stderr
      KONG_ADMIN_LISTEN: 0.0.0.0:8001, 0.0.0.0:8444 ssl
      #KONG_TRUSTED_IPS: 0.0.0.0/0,::/0
      #KONG_REAL_IP_RECURSIVE: "on"
    depends_on:
      - kong-database
      - kong-migration
    links:
      - "kong-database:kong-database"
    healthcheck:
      test: ["CMD", "kong", "health"]
      interval: 10s
      timeout: 10s
      retries: 10
    ports:
      - "8000:8000"
      - "8443:8443"
      - "8001:8001"
      - "8444:8444"

  #######################################
  # Konga database prepare
  #######################################
  konga-prepare:
    image: pantsel/konga
    command: "-c prepare -a postgres -u postgresql://kong:kong@kong-database:5432/konga_db"
    networks:
      - kong-net
    restart: on-failure
    depends_on:
      - kong-database

  #######################################
  # Konga: Kong GUI
  #######################################
  konga:
    image: pantsel/konga
    container_name: konga
    restart: always
    networks:
        - kong-net   
    environment:
      DB_ADAPTER: postgres
      DB_HOST: kong-database
      DB_USER: kong
      DB_PASSWORD: kong
      DB_DATABASE: konga_db
      KONGA_HOOK_TIMEOUT: 120000
      POOL_SIZE: 10
      #DB_URI: postgresql://kong:kong@kong-database:5432/konga_db
      NODE_ENV: production
    depends_on:
      - kong-database
      - kong
      - konga-prepare
    ports:
      - "1337:1337"
    links:
      - kong:kong

I'm trying to figure it out.

Thanks in advance

[javaChip56]

@narinkaew Have you tried using the Docker network bridge IP 172.17.0.1? Or you can also try using the Gateway IP assigned to your kong-net docker network.

[pantsel]

Try http://kong:8001

[larsnaesbye]

Works here (Kong 2.0.1 and Konga 0.14.7) as well, but doesn't offer all Plugins available in Kong, e.g. the ACME plugin, which would be extremely helpful.

@jschirrmacher Try Kong 2.0.2, where the ACME plugin is enabled by default (not Kongas fault). You'll find it under 'Other'.

[narinkaew]

@javaChip56 Already tried bridge default & gateway IP and also custom network IP & gateway IP are all not working on corporate network

@pantsel Already tried http://kong:8001, it's not working on corporate network At the same time, it is working perfectly on my home PC. It can connect between kong and konga with http://kong:8001.

More information, I tried run kong & konga on my home PC and working perfectly with http://kong:8001. I have no idea why it is not working on corporate network in spite of running on docker environment.

Do you have suggest on the corporate network issue like this?

[javaChip56]

@narinkaew I'm not sure, but could it be because your network has its own DNS and you're host is trying to resolve the IP addresses against it?

[narinkaew]

Update, It's working now after reinstall the docker (same version).

After I tried on my colleague machine on the same corporate network and it's worked. I realize that something wrong on my machine. Then I reinstalled the docker, run docker-compose, connect between kong & konga (with http://kong:8001) and it's worked!

I'm not sure what is the root cause but it is working now after stucked on this for days.

@javaChip56, @pantsel Thanks for your suggestion, it's help me a lot

[daddydrac]

@joehoeller are both Kong and Konga running in a docker container on your local host?

Yes on Docker compose to common network. I have the most recent version of Docker installed.

I can add you to the private project, temporarily, if you want to pull it down & see what’s wrong?

[daddydrac]

I’m still having this problem. Not solved as of today.

[daddydrac]

@ are both Kong and Konga running in a docker container on your local host?

yes, in docker compose

[daddydrac]

the image im pulling is pantsel/konga:next, is thet the correct one?

[larsnaesbye]

That's the newest, yes.

[daddydrac]

So.... its still broke; How do we fix?

[pantsel]

@joehoeller , please post your configuration so we can help. Are u using a docker compose file? Can u reach kongs admin api with curl? Are the ports 8001/8444 exposed to the network? Is konga in the same network as kong? Is the env var KONG_ADMIN_LISTEN set?

[gaganshera]

I had the same problem on my Mac. kong and konga on different containers running inside the same network, konga wasn't able to connect to http://localhost:8001. Figured out it was due to konga container not recognising localhost directly. Try it with docker.for.mac.localhost or docker.for.windows.localhost for mac or windows respectively. Or just host.docker.internal for docker 18.03 onwards.

[aaron-harvey]

host.docker.internal

this worked for me as well

[asilenkov]

doesn't work for me. Image: pantsel/konga:next Kong: latest (2.0) Postgres:12 NVM sorry I have to search before posting,
https://github.com/pantsel/konga/issues/545

[Gowtham029]

is there any update on 2.0? when Konga will support kong? any plans? any tentative dates?

[iankittomar]

For me work fine:)

Kong Version:- 2.1.3 Konga Version:- 0.14.9

[xrdavies]

Try http://kong:8001

This way solves my problem.

[fertab]

Does this Konga version already support Kong 2.x.x??