this post was submitted on 23 Oct 2023
1 points (100.0% liked)

Self-Hosted Main

515 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
 

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:

you are viewing a single comment's thread
view the rest of the comments
[–] Test_Glittering@alien.top 1 points 1 year ago (1 children)

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?

[–] t1nk3rz@alien.top 1 points 1 year ago

If you have other apps running correctly it means that is something with the archivist,have you tried changing the ip in docker compose file in the TA Host to change it to localhost or 127.0.0.1