2
submitted 10 months ago by Operations8@alien.top to c/main@selfhosted.forum

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.

top 5 comments
sorted by: hot top controversial new old
[-] tschloss@alien.top 1 points 10 months ago

Don‘t know picsur. But first step the service should work without reverse proxy. So try from docker host, then from same subnet.

Also the directive networks inside of the sb container makes no sense. Delete both lines.

After this look into the nginx log files (access and error)!

[-] Operations8@alien.top 1 points 10 months ago

The directive networks, i removed that (edited the start post). I did this the right way right?

my other dockers also work 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)

Docker logs NPM command, only shows me certifcate created and renew info.

So something is wrong but i cannot figure out what.

[-] tschloss@alien.top 1 points 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)

[-] Operations8@alien.top 1 points 10 months ago

Yes that part also drives me crazy :P

http://172.16.10.10:8077 gives me connection refused. When i try http://172.16.10.10:3100 (just one example) i get the openspeedtest docker.

[-] tschloss@alien.top 1 points 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.

this post was submitted on 28 Oct 2023
2 points (100.0% liked)

Self-Hosted Main

502 readers
1 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

For Example

We welcome posts that include suggestions for good self-hosted alternatives to popular online services, how they are better, or how they give back control of your data. Also include hints and tips for less technical readers.

Useful Lists

founded 1 year ago
MODERATORS