@kiyospace: probably it's the "usual" Issue with Docker/Podman localhost, isn't it ?
If not, at least with podman, using the default podman Network could also be an Issue (maybe also with docker) since DNS is disabled on the default Network.

I managed to get it working with Podman on a Subdomain with Caddy Reverse Proxy, although there was definitively something a bit special to do with regards to the EndPoints (/app needs a separate Rule).

Caddyfile:

# Example and Guide
# https://caddyserver.com/docs/caddyfile/options

# General Options
{
    # (Optional) Debug Mode
    debug

    # Disable Admin API
    admin off

    # TLS Options
    # (Optional) Disable Certificates Management (only if SSL/TLS Certificates are managed by certbot or other external Tools)
    auto_https disable_certs

    # (Optional) Default SNI
    # default_sni {$APPLICATION_HOSTNAME}
}

# localhost {
# 	reverse_proxy /api/* localhost:9001
# }

# (Optional) Only if SSL/TLS Certificates are managed by certbot or other external Tools and Custom Logging is required
{$APPLICATION_HOSTNAME} {
    tls /certificates/{$APPLICATION_CERTIFICATE_DOMAIN}/{$APPLICATION_CERTIFICATE_CERT_FILE:fullchain.pem} /certificates/{$APPLICATION_CERTIFICATE_DOMAIN}/{$APPLICATION_CERTIFICATE_KEY_FILE:privkey.pem}

    log {
	output file /var/log/{$APPLICATION_HOSTNAME}/access.json {
                roll_size 100MiB
                roll_keep 5000
                roll_keep_for 720h
                roll_uncompressed
        }

        format json
    }


    # Application Reverse Proxy goes to a different IP Address (use IPv4 Connection)
    reverse_proxy /app* http://127.0.0.1:6001

    # Application Reverse Proxy goes to a different IP Address (use IPv6 Connection)
    # reverse_proxy /app* http://[::1]:6001



    # Default Reverse Proxy (use IPv4 Connection)
    # reverse_proxy http://127.0.0.1:{$APPLICATION_PORT}

    # Default Reverse Proxy (use IPv6 Connection)
    reverse_proxy http://[::1]:{$APPLICATION_PORT}

}

Not sure if your 9191 Port is correct, I have 6001.

EDIT 1: you can try troubleshooting by, if running inside the container as root, apt-get update; apt-get install iproute2; ss -nlt and see to which Ports & Addresses the Application/Container is listening (from the inside).

Or you could build something like the Docker Image I wrote and attach that to the Docker Network / Podman Pod, and use that to inspect what is going on:

https://github.com/luckylinux/docker-network-troubleshooting

Once running:

ss -nlt

(it's basically a new "Version" of netstat Command)

[Feature Request] Native installation method & guide #482

Description

Activity

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions