I am still learning docker so be patient please :)

I have created a docker-compose.yml file for “picsur”.

See:

version: '3'
services:
picsur:
image: ghcr.io/caramelfur/picsur:latest
container_name: picsur
ports:
- '8077:8044'
environment:
PICSUR_HOST: '0.0.0.0'
#PICSUR_PORT: 8044
PICSUR_DB_HOST: picsur_postgres
PICSUR_DB_PORT: 5432
PICSUR_DB_USERNAME: $dbuser
PICSUR_DB_PASSWORD: $dbpass
PICSUR_DB_DATABASE: picsur
## The default username is admin, this is not modifyable
PICSUR_ADMIN_PASSWORD: $adminpass
## Maximum accepted size for uploads in bytes
PICSUR_MAX_FILE_SIZE: 128000000
## No need to touch this, unless you use a custom frontend
# PICSUR_STATIC_FRONTEND_ROOT: "/picsur/frontend/dist"
## Warning: Verbose mode might log sensitive data
# PICSUR_VERBOSE: "true"
restart: unless-stopped
picsur_postgres:
image: postgres:14-alpine
container_name: picsur_postgres
networks:
- proxy
environment:
POSTGRES_DB: picsur
POSTGRES_PASSWORD: $dbpass
POSTGRES_USER: $dbuser
restart: unless-stopped
volumes:
- ./data:/var/lib/postgresql/data

I have created an entry in my Nginx Proxy Manager:

picsur.myowndomain.com => http://docker-IPv4:8077

The other dockers running through Nginx are working fine.

My problem is that picsur.myowndomain.com works (with SSL via Let’s Encrypt) BUT it show a blank page.

  • tschloss@alien.topB
    link
    fedilink
    English
    arrow-up
    1
    ·
    10 months ago

    No. This is the text I am referring to: „via http://internal-docker-IP:port. but picsur doesnt work via that way. Connection refused. so http://internal-docker-IP:8044/ (8077 also doesnt work)“

    I am unsure if I decode this meta information correctly.

    (Reddit drives me crazy: my answers appear on top level when I want to reply in thread and vice versa)

      • tschloss@alien.topB
        link
        fedilink
        English
        arrow-up
        1
        ·
        10 months ago

        Is this your LAN subnet? It looks very much as a docker virtual network? These addresses shouldn‘t be accessible from outside unless you tinker with the network settings of docker. Containers should be accessible on localhost:externalPort from the host docker is running on.