We have successfully created a Dockerfile and deployed the Kong API Gateway to Railway. Here are the details:

Dockerfile

FROM kong/kong-gateway:3.8.0.0

ENV KONGDATABASE=postgres ENV KONGPGHOST=junction.proxy.rlwy.net ENV KONGPGPORT=45525 ENV KONGPGUSER=postgres ENV KONGPGPASSWORD=KJHSBdcJlvaFMOCiTXfvDGcqjpyUwPMX ENV KONGPGDATABASE=railway ENV KONGPGSSL=off ENV KONGPGSSLVERIFY=off
ENV KONGPROXYACCESSLOG=/dev/stdout ENV KONGADMINACCESSLOG=/dev/stdout
ENV KONGPROXYERRORLOG=/dev/stderr ENV KONGADMINERRORLOG=/dev/stderr
ENV KONGADMINLISTEN=0.0.0.0:8001
ENV KONGADMINGUI_URL=http://localhost:8002/

ENTRYPOINT ["/bin/sh", "-c", "set -e; kong migrations bootstrap; kong start && tail -f /dev/null"]

EXPOSE 8002

Kong API Gateway Deployed logs:

Starting Container
Database already bootstrapped
Kong started

However, when we attempt to access the Kong gateway GUI, we encounter an issue as shown in the attached image. Could someone help us understand what might be wrong?

Postsgres DB Deploy logs

2024-09-25 07:46:48.466 UTC [3882] LOG: could not receive data from client: Connection reset by peer
2024-09-25 07:46:48.578 UTC [3883] LOG: could not receive data from client: Connection reset by peer
2024-09-25 07:50:12.694 UTC [26] LOG: checkpoint starting: time
2024-09-25 07:50:13.186 UTC [26] LOG: checkpoint complete: wrote 4 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.327 s, sync=0.081 s, total=0.492 s; sync files=3, longest=0.072 s, average=0.027 s; distance=103 kB, estimate=148 kB; lsn=0/2EF61F8, redo lsn=0/2EF61C0

Any insights into this issue would be greatly appreciated. Thank you!

Kong API Gateway Project ID: 65aa3e03-02b4-41a1-af0c-5ef1454d2095
Postgres DB Project ID: bde6fd6c-3f1c-4f41-b7f0-6425796891c5