Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Custom DNS configuration sometimes required to get around certain Extensions bans #47

Open
ghost opened this issue Aug 16, 2023 · 0 comments
Labels
documentation Improvements or additions to documentation

Comments

@ghost
Copy link

ghost commented Aug 16, 2023

My ISP has soft banned MangaDex so I always need to use a DNS different from the one offered by my ISP to get around the block. On my phone it's easily done by using the "one.one.one.one" address in the Networking configs but I noticed the default compose file or the documentation itself didn't address the problem.

In docker, using a --dns "1.1.1.1" is all you have to do to make your container use a different DNS address. Maybe an environment variable or commented out line can be added somewhere? Here's my current compose file:

version: '3.7'
services:
  suwayomi:
    image: ghcr.io/suwayomi/tachidesk:stable
    environment:
      - TZ=Europe/Dublin # Use TZ database name from https://en.wikipedia.org/wiki/List_of_tz_database_time_zones
      - DEBUG=true
      - BIND_IP=0.0.0.0
      - BIND_PORT=4567
      - SOCKS_PROXY_ENABLED=false
      - DOWNLOAD_AS_CBZ=true
      - MAX_PARALLEL_UPDATE=3
      - BASIC_AUTH_ENABLED=true
      - BASIC_AUTH_USERNAME=admin
      - BASIC_AUTH_PASSWORD=ahJTmbg2xsj2BAc
    dns:
      - "1.1.1.1"
    volumes:
      - /opt/tachiyomi:/home/suwayomi/.local/share/Tachidesk
    ports:
      - "4567:4567"
    restart: on-failure:3
@Syer10 Syer10 added the documentation Improvements or additions to documentation label Feb 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

1 participant