Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ

54669 readers

689 users here now

⚓ Dedicated to the discussion of digital piracy, including ethical problems and legal advancements.

Rules • Full Version

1. Posts must be related to the discussion of digital piracy

2. Don't request invites, trade, sell, or self-promote

3. Don't request or link to specific pirated titles, including DMs

4. Don't submit low-quality posts, be entitled, or harass others

Loot, Pillage, & Plunder

📜 c/Piracy Wiki (Community Edition):

💰 Please help cover server costs.


Ko-fi	Liberapay

founded 1 year ago

MODERATORS

[email protected]

qBit is showing and acting as firewalled but setup is correct in Gluetun (self.piracy)

submitted 8 months ago* (last edited 8 months ago) by jws_shadotak to c/[email protected]

14 comments fedilink hide all child comments

Setup:

Debian running podman. Containers and compose files are managed with Dockge. qBit and Gluetun are on a single compose file and all qBit traffic is routed through Gluetun.

qBit seems to starts first before Gluetun is fully set up and qBit doesn't see the open port. Every time I start them together, I have to manually restart qBit again once Gluetun is ready. Once it's restarted, it shows as open and connected again.

I tried looking for ways to delay startup in a compose file but I didn't get any results.

Is there a solution to this?

https://pastebin.com/kgqt8aJ7

you are viewing a single comment's thread
view the rest of the comments

[–] jws_shadotak 1 points 8 months ago (1 children)

I added this to my qBit section:

    depends_on:
      gluetun:
        condition: service_healthy
        restart: true

It caused an error with gluetun somehow

[–] [email protected] 1 points 8 months ago (1 children)

You only need depends_on: gluetun. Did you observe the logs at boot? Do they still show that qbit starts first?

[–] jws_shadotak 1 points 8 months ago

qBit starts second but Gluetun isn't finished and doesn't open the port for another few seconds, causing this problem