I've got 2 servers on my local network: rasp pi, and an ubuntu vm. I'm trying to use nginx proxy manager with pihole DNS records to give tubearchivist an easier address to remember. Tubearchivist itself is working great using the below docker compose file. However, I can't access it through it's pihole dns record. It simply gives a "Bad Request (400)" error. I've tried using the 192.168.1.8 & yt_dl.stuff separately, together, and between quotes, but no luck. Furthermore, using nslookup, I can tell the yt_dl.stuff is pointing to the correct address. Any ideas on what might be configured wrong in my docker compose below? Thanks!
version: '3.5'
services:
tubearchivist:
container_name: tubearchivist
restart: unless-stopped
image: bbilly1/tubearchivist
ports:
- 8000:8000
volumes:
- media:/youtube
- cache:/cache
environment:
- ES_URL=http://archivist-es:9200 # needs protocol e.g. http and port
- REDIS_HOST=archivist-redis # don't add protocol
- HOST_UID=1000
- HOST_GID=1000
- TA_HOST=192.168.1.8 yt_dl.stuff # set your host name
- TA_USERNAME=tubearchivist # your initial TA credentials
- TA_PASSWORD=verysecret # your initial TA credentials
- ELASTIC_PASSWORD=verysecret # set password for Elasticsearch
- TZ=America/Chicago # set your time zone
depends_on:
- archivist-es
- archivist-redis
archivist-redis:
image: redis/redis-stack-server
container_name: archivist-redis
restart: unless-stopped
expose:
- "6379"
volumes:
- redis:/data
depends_on:
- archivist-es
archivist-es:
image: bbilly1/tubearchivist-es # only for amd64, or use official es 8.9.0
container_name: archivist-es
restart: unless-stopped
environment:
- "ELASTIC_PASSWORD=verysecret" # matching Elasticsearch password
- "ES_JAVA_OPTS=-Xms512m -Xmx512m"
- "xpack.security.enabled=true"
- "discovery.type=single-node"
- "path.repo=/usr/share/elasticsearch/data/snapshot"
ulimits:
memlock:
soft: -1
hard: -1
volumes:
- es:/usr/share/elasticsearch/data # check for permission error when using bind mount, see readme
expose:
- "9200"
volumes:
media:
cache:
redis:
es:
Yep sounds the same. I do have pihole hole dns record (yt_dl.home) pointing to nginxproxy (my rasp pi) @ 192.168.1.19. And then in npm, I have yt_dl.home pointing to 192.168.1.8:8000. So I think that's all set up correctly. I have other apps I'm using in a similar configuration. Is there anything special you had to do for tubearchivist?