Cannot use Direct connection when using bridge networking

[auanasgheps]

Output of docker inspect jdownloader --format='{{index .Config.Labels.version}}':

0.7.2-amd64

Description

Cannot use Direct connection when using bridge networking. I guess this is happening because the container is announcing the virtual docker IP, in my case 172.20.0.6, and my public IP. I can see these IP addresses from the android app. I have not opened a port from WAN access.

I want to use direct connection only in my LAN, but currently it is not possible.

Command line I used to start the container

services:
   jdownloader:
    image: jaymoulin/jdownloader
    container_name: jdownloader
    restart: unless-stopped
    user: 1029:100
    volumes:
        -/path/to/cfg/on/host:/opt/JDownloader/cfg
        -/path/to/logs/on/host::/opt/JDownloader/logs
        -/path/to/downloads/on/host:/downloads
        -/etc/localtime:/etc/localtime:ro
    ports:
        - 3129:3129 
    networks:
        default:
            ipv4_address: 172.20.0.6    
    
networks:
    default:
        external: 
            name: rete
### Note: "rete" is an already existing bridge network.

Steps to reproduce the issue:

1. Deploy the container with this configuration (bridge docker network)
2. Set Jdownloader to "Allow lan/wan connections with manual port forwarding"
3. Restart the container

Describe the results you received:
Connection will remain on Jdownloader servers

Describe the results you expected:
Direct connection to be enabled

Additional information you deem important (e.g. issue happens only occasionally):
I believe we need to tell the container that the real local IP is another one.

Provide some logs (docker logs jdownloader)
Do you really need logs for this? What file exactly?

(paste logs)

[jaymoulin]

As @jiaz83 (JDownloader developper) stated here #33 (comment)

short explanation what the direct connection mode does.
client(app,webinterface,tool...)<-....->JDownloader connections happens either

1.) client<-apiserver->JDownloader
in this(default,fallback) mode both(control- and data-) connections are using the api server.
Advantage: no need to forward ports/dyndns
Disadvantage: lower bandwidth and higher latency

2.) client<->JDownloader
in this (direct connection) mode, control connections are still using the api server while data connections are directly connecting to the running JDownloader instance without any relay server
Advantage: much higher bandwidth and reduced latency
Disadvantage: user might have to manually enable/allow port forwarding from LAN and/or WAN IP to JDownloader instance
On connection issues, the client will automatically fallback to 1.) and try to re-establish a direct connection again.

by default direct connection mode is set to LAN, so only clients from LAN can connect directly.
see https://support.jdownloader.org/Knowledgebase/Article/View/33/0/myjdownloader-advanced-settings
default port is 3129

I'm not really sure what you try to accomplish though.

[auanasgheps]

I want to use the 2nd mode: a direct connection, but jDownloader always reports I'm using API Server.

[jaymoulin]

I still don't understand the reason of using a bridge network as your container will not be available outside the defined network. Anyway, if you use host network, your container would be accessible in your LAN. BUT, looks like there's a bug in the mobile application that @jiaz83 may be aware of.

I was able to enable Direct connection and connect directly from LAN. This was working on the my.jdownloader.org desktop app but not from the Android mobile application despite the fact that both applications where on the same network.

[auanasgheps]

I wanted to use bridge networking since all of my containers are configured in this way, and are accessible from my real LAN. Even if I open the port 3129 in the docker LAN (like stated in the Docker config), I still can't access the container in direct connection, but it should work. At this point I don't know if it's a JDownloader bug or not.

I will probably have to settle with host networking.

[jiaz83]

Check Settings-Advanced Settings-MyJDownloaderSettings.lastlocalport, it contains the current used port. JDownloader tries to use MyJDownloaderSettings.manuallocalport but in case that port is not available, it chooses random one. You may change MyJDownloaderSettings.manuallocalport and restart JDownloader