Add Usenet Capability

[rkabrick]

Hey!

Love this repo... wondering how I would go about modifying it such that I have a sabnzbd container that can be resolved via 'nas.mydomain.com/sabnzbd'

Unsure which parts of the config need to change and how but would appreciate any guidance :)

[AdrienPoupa]

Hello, I'm glad you like it! I would create a sabnzbd folder and add the following service:

  sabnzbd:
    image: lscr.io/linuxserver/sabnzbd:latest
    container_name: sabnzbd
    environment:
      - PUID=${USER_ID}
      - PGID=${GROUP_ID}
      - TZ=${TIMEZONE}
    volumes:
      - ./sabnzbd:/config
      - ${DATA_ROOT}:/data
    restart: always
    labels:
      - traefik.enable=true
      - traefik.http.routers.sabnzbd.rule=(Host(`${HOSTNAME}`) && PathPrefix(`/sabnzbd`) || PathPrefix(`/sabnzbd`))
      - traefik.http.routers.sabnzbd.tls=true
      - traefik.http.routers.sabnzbd.tls.certresolver=myresolver
      - traefik.http.services.sabnzbd.loadbalancer.server.port=8080

In Sabnzbd you will also need to set the url_base param to /sabnzbd. I haven't tried it, let me know if it works :)

https://sabnzbd.org/wiki/configuration/3.7/special

[rkabrick]

Hey! So I used that service however I get "Bad Gateway" when I go to connect to nas.mydomain.com/sabnzbd. Is this perhaps an issue with qbittorrent also using port 8080?

[AdrienPoupa]

There is no option to change the web UI port in this image I'm afraid. But given it's not exposed to the host it should work. Did you change the url_base?

[rkabrick]

Unfortunately I did change the urlbase but to no avail...

When you refer to 'this image' do you mean qbit? When I've configured the two together (not using traefik) I've always had

ports:
- 8081:8081

and then left qbit as 8080.

Is this possible? If not, is it possible for me to spin up a second vm and connect it to the same domain? ie. having two ubuntu vms (currently only have one) and then have it still be resolvable from the same domain? This is something I'd like to do regardless of if I can work out sab on the same host for something like notifiarr.

[AdrienPoupa]

I tried the service configuration I pasted in the previous comment, I can access sabnzbd's wizard:

Also, checking sabnzbd.ini, I can see the url_base parameter was already filled: url_base = /sabnzbd.

Thus I'm not sure where the Bad Gateway is coming from, maybe check Traefik's logs?

For good measure, you could try to recreate the whole stack, including networks: docker compose down && docker compose up -d

[rkabrick]

I really appreciate your time. I was finally able to solve it by doing an rm -rf ./sabnzbd. It must've been pulling some cached value or something... but once I deleted that and did docker compose down && docker compose up -d it finally worked. Thank you!

[AdrienPoupa]

That's great, thanks for testing. I'll add it as an optional service!

[mikenholt]

I was able to get this up and running , thanks.

I wanted to leave a comment to say that when the service first started, SABnzbd was reporting an unknown host error with a link to this page: https://sabnzbd.org/wiki/extra/hostname-check.html

To fix, I edited /sabnzbd/sabnzbd.ini by adding my host value (nas.example.com) to host_whitelist. Be sure to use a comma separator if some other value is currently there and restart the container after the change.