port forwarding in transmission docker

  • Ok, next problem. I can not get portforwarding to work with my transmission docker. When I test the port from within transmission Remote GUI I get this error message:



    This is the port I configured in the stack, so that is correct. Can it be that whatever magic UPnP or whatever does is not working through the boundaries of the container? I don't really know what to do next.

  • This is the port I configured in the stack, so that is correct.

    Without seeing the stack it's difficult to comment, but that message would suggest the port is not open on your router, or it's not being forwarded from point a to point b and has nothing to do with the container.

    Raid is not a backup! Would you go skydiving without a parachute?

  • Did you forward that port in your router? Also if you're running through a VPN, I think that could affect this.

    Air Conditioners are a lot like PC's... They work great until you open Windows.


  • No. When transmission was running as an extension in OMV4 I did not have to. The port would be opened by UPnP automatically. Thats what I wanted here also, as I wanted to use random ports at startup.

    I guess that's what I will have to do then and keep the port static.

  • No. When transmission was running as an extension in OMV4 I did not have to. The port would be opened by UPnP automatically. Thats what I wanted here also, as I wanted to use random ports at startup.

    I guess that's what I will have to do then and keep the port static.

    Sorry I just realized you said you don't have a VPN... irregardless, I'm pretty sure UPNP can't open a router port automatically

    Air Conditioners are a lot like PC's... They work great until you open Windows.


  • No VPN, no. Mainly hosting Linux images and programs, nothing to hide :-)

    I have this table on my router configuration page. It is called UPnP, and you can see that for every portchange there is a new entry in this table (.0.101 is the NAS).

    UPnP-Dienstliste

    Anzahl Clients: 11
    Neu laden

    IDDienstbeschreibungExterner PortProtokollInterne IP-AdresseInterner Port
    1Transmission at 1981819818TCP192.168.0.10119818
    2Transmission at 1981819818UDP192.168.0.10119818
    3Transmission at 5066550665TCP192.168.0.10150665
    4Transmission at 5066550665UDP192.168.0.10150665
    5WhatsApp (1610814412) ()38831UDP192.168.0.10338831
    6AnyDesk38992TCP192.168.0.1287070
    7Transmission at 4860248602TCP192.168.0.10148602
    8Transmission at 4860248602UDP192.168.0.10148602



    But I do not remember where my preference for random ports comes from, I just always had it like that. Maybe some installation guide trying to obfuscate traffic through that. Makes no sense to me today, I will just go with a static port and open that in the router.

  • Palladium

    Added the Label OMV 5.x
  • Palladium

    Added the Label resolved

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!