Hi I have Kong up and running on Railways environment. I try to configure admin gui manager to work on internal IPv6 network. For this I configured env variable:
KONG_ADMIN_GUI_LISTEN=[::0]:8002, [::0]:8445 ssl
However after redeployment I can see that in configuration json pulled from admin api there is nothing changed it still uses IPv4:
“admin_gui_listen”: [
“0.0.0.0:8002”,
“0.0.0.0:8445 ssl”
],
Other configs like KONG_ADMIN_LISTEN or KONG_PROXY_LISTEN applied with no problems to values passed by envs.
What I try to achieve is to access all: web, c-plane and d-plane on single port. Its because Railway exposes only one port per app. I have added services to kong to point on internal ports 8001 and 8002 (in Railway internal networking is IPv6 only).
So lets say under https://mykong.com/admin-api I am routed to 8001 port, and for https://mykong.com/manager I am routed to 8002 port. https://mykong.com is connected to port 8000
Basically it works fine for both d-plane and c-plane but for https://mykong.com/manager I got connection refuse (111). I think this could be because ADMIN_GUI_LISTEN is set to IPv4 only while Railway uses IPv6