Docker container for JDownloader 2

This project provides a Docker container for JDownloader 2.

The graphical user interface (GUI) of the application can be accessed through a modern web browser, requiring no installation or configuration on the client side, or via any VNC client.

JDownloader 2 is a free, open-source download management tool with a huge community of developers that makes downloading as easy and fast as it should be. Users can start, stop or pause downloads, set bandwith limitations, auto-extract archives and much more. It's an easy-to-extend framework that can save hours of your valuable time every day!

Quick Start

Important

The Docker command provided in this quick start is an example, and parameters should be adjusted to suit your needs.

Launch the JDownloader 2 docker container with the following command:

docker run -d \
    --name=jdownloader-2 \
    -p 5800:5800 \
    -v /docker/appdata/jdownloader-2:/config:rw \
    -v /home/user/Downloads:/output:rw \
    jlesage/jdownloader-2

Where:

/docker/appdata/jdownloader-2: Stores the application's configuration, state, logs, and any files requiring persistency.
/home/user/Downloads: This is where downloaded files are stored.

Access the JDownloader 2 GUI by browsing to http://your-host-ip:5800.

Usage

docker run [-d] \
    --name=jdownloader-2 \
    [-e <VARIABLE_NAME>=<VALUE>]... \
    [-v <HOST_DIR>:<CONTAINER_DIR>[:PERMISSIONS]]... \
    [-p <HOST_PORT>:<CONTAINER_PORT>]... \
    jlesage/jdownloader-2

Parameter	Description
-d	Runs the container in the background. If not set, the container runs in the foreground.
-e	Passes an environment variable to the container. See Environment Variables for details.
-v	Sets a volume mapping to share a folder or file between the host and the container. See Data Volumes for details.
-p	Sets a network port mapping to expose an internal container port to the host). See Ports for details.

Environment Variables

To customize the container's behavior, you can pass environment variables using the -e parameter in the format <VARIABLE_NAME>=<VALUE>.

Variable	Description	Default
`USER_ID`	ID of the user the application runs as. See User/Group IDs for details.	`1000`
`GROUP_ID`	ID of the group the application runs as. See User/Group IDs for details.	`1000`
`SUP_GROUP_IDS`	Comma-separated list of supplementary group IDs for the application.	(no value)
`UMASK`	Mask controlling permissions for newly created files and folders, specified in octal notation. By default, `0022` ensures files and folders are readable by all but writable only by the owner. See the umask calculator at http://wintelguy.com/umask-calc.pl.	`0022`
`LANG`	Sets the locale, defining the application's language, if supported. Format is `language[_territory][.codeset]`, where language is an ISO 639 language code, territory is an ISO 3166 country code, and codeset is a character set, like `UTF-8`. For example, Australian English using UTF-8 is `en_AU.UTF-8`.	`en_US.UTF-8`
`TZ`	TimeZone used by the container. The timezone can also be set by mapping `/etc/localtime` between the host and the container.	`Etc/UTC`
`KEEP_APP_RUNNING`	When set to `1`, the application is automatically restarted if it crashes or terminates.	`0`
`APP_NICENESS`	Priority at which the application runs. A niceness value of -20 is the highest, 19 is the lowest and 0 the default. NOTE: A negative niceness (priority increase) requires additional permissions. The container must be run with the Docker option `--cap-add=SYS_NICE`.	`0`
`INSTALL_PACKAGES`	Space-separated list of packages to install during container startup. List of available packages can be found at https://pkgs.alpinelinux.org.	(no value)
`PACKAGES_MIRROR`	Mirror of the repository to use when installing packages. List of mirrors is available at https://mirrors.alpinelinux.org.	(no value)
`CONTAINER_DEBUG`	When set to `1`, enables debug logging.	`0`
`DISPLAY_WIDTH`	Width (in pixels) of the application's window.	`1920`
`DISPLAY_HEIGHT`	Height (in pixels) of the application's window.	`1080`
`DARK_MODE`	When set to `1`, enables dark mode for the application. See Dark Mode](#dark-mode) for details.	`0`
`WEB_AUDIO`	When set to `1`, enables audio support, allowing audio produced by the application to play through the browser. See Web Audio for details.	`0`
`WEB_FILE_MANAGER`	When set to `1`, enables the web file manager, allowing interaction with files inside the container through the web browser, supporting operations like renaming, deleting, uploading, and downloading. See Web File Manager for details.	`0`
`WEB_FILE_MANAGER_ALLOWED_PATHS`	Comma-separated list of paths within the container that the file manager can access. By default, the container's entire filesystem is not accessible, and this variable specifies allowed paths. If set to `AUTO`, commonly used folders 8000 and those mapped to the container are automatically allowed. The value `ALL` allows access to all paths (no restrictions). See Web File Manager for details.	`AUTO`
`WEB_FILE_MANAGER_DENIED_PATHS`	Comma-separated list of paths within the container that the file manager cannot access. A denied path takes precedence over an allowed path. See Web File Manager for details.	(no value)
`WEB_AUTHENTICATION`	When set to `1`, protects the application's GUI with a login page when accessed via a web browser. Access is granted only with valid credentials. This feature requires the secure connection to be enabled. See Web Authentication for details.	`0`
`WEB_AUTHENTICATION_TOKEN_VALIDITY_TIME`	Lifetime of a token, in hours. A token is assigned to the user after successful login. As long as the token is valid, the user can access the application's GUI without logging in again. Once the token expires, the login page is displayed again.	`24`
`WEB_AUTHENTICATION_USERNAME`	Optional username for web authentication. Provides a quick and easy way to configure credentials for a single user. For more secure configuration or multiple users, see the Web Authentication section.	(no value)
`WEB_AUTHENTICATION_PASSWORD`	Optional password for web authentication. Provides a quick and easy way to configure credentials for a single user. For more secure configuration or multiple users, see the Web Authentication section.	(no value)
`SECURE_CONNECTION`	When set to `1`, uses an encrypted connection to access the application's GUI (via web browser or VNC client). See Security for details.	`0`
`SECURE_CONNECTION_VNC_METHOD`	Method used for encrypted VNC connections. Possible values are `SSL` or `TLS`. See Security for details.	`SSL`
`SECURE_CONNECTION_CERTS_CHECK_INTERVAL`	Interval, in seconds, at which the system checks if web or VNC certificates have changed. When a change is detected, affected services are automatically restarted. A value of `0` disables the check.	`60`
`WEB_LISTENING_PORT`	Port used by the web server to serve the application's GUI. This port is internal to the container and typically does not need to be changed. By default, a container uses the default bridge network, requiring each internal port to be mapped to an external port (using the `-p` or `--publish` argument). If another network type is used, changing this port may prevent conflicts with other services/containers. NOTE: A value of `-1` disables HTTP/HTTPS access to the application's GUI.	`5800`
`VNC_LISTENING_PORT`	Port used by the VNC server to serve the application's GUI. This port is internal to the container and typically does not need to be changed. By default, a container uses the default bridge network, requiring each internal port to be mapped to an external port (using the `-p` or `--publish` argument). If another network type is used, changing this port may prevent conflicts with other services/containers. NOTE: A value of `-1` disables VNC access to the application's GUI.	`5900`
`VNC_PASSWORD`	Password required to connect to the application's GUI. See the VNC Password section for details.	(no value)
`ENABLE_CJK_FONT`	When set to `1`, installs the open-source font `WenQuanYi Zen Hei`, supporting a wide range of Chinese/Japanese/Korean characters.	`0`
`MYJDOWNLOADER_EMAIL`	Email address of the MyJDownloader account to use. Note that this can also be configured via the JDownloader GUI.	(no value)
`MYJDOWNLOADER_PASSWORD`	Password of the MyJDownloader account to use. Note that this can also be configured via the JDownloader GUI.	(no value)
`MYJDOWNLOADER_DEVICE_NAME`	The name of this JDownloader instance. Note that this can also be configured via the JDownloader GUI.	(no value)
`JDOWNLOADER_HEADLESS`	When set to `1`, JDownloader is running in headless mode, meaning that no GUI is available. In this mode, MyJDownloader should be used to remote control JDownloader.	`0`
`JDOWNLOADER_MAX_MEM`	Maximum amount of memory JDownloader is allowed to use. One of the following memory unit (case insensitive) should be added as a suffix to the size: `G`, `M` or `K`. When this variable is not set, the limit is automatically calculated based on the amount of RAM of the system.	(no value)

Deployment Considerations

Many tools used to manage Docker containers extract environment variables defined by the Docker image to create or deploy the container.

For example, this behavior is seen in:

The Docker application on Synology NAS
The Container Station on QNAP NAS
Portainer
etc.

While this is useful for users to adjust environment variable values to suit their needs, keeping all of them can be confusing and even risky.

A good practice is to set or retain only the variables necessary for the container to function as desired in your setup. If a variable is left at its default value, it can be removed. Keep in mind that all environment variables are optional; none are required for the container to start.

Removing unneeded environment variables offers several benefits:

Prevents retaining variables no longer used by the container. Over time, with image updates, some variables may become obsolete.
Allows the Docker image to update or fix default values. With image updates, default values may change to address issues or support new features.
Avoids changes to variables that could disrupt the container's functionality. Some undocumented variables, like PATH or ENV, are required but not meant to be modified by users, yet container management tools may expose them.
Addresses a bug in Container Station on QNAP and the Docker application on Synology, where variables without values may not be allowed. This behavior is incorrect, as variables without values are valid. Removing unneeded variables prevents deployment issues on these devices.

Data Volumes

The following table describes the data volumes used by the container. Volume mappings are set using the -v parameter with a value in the format <HOST_DIR>:<CONTAINER_DIR>[:PERMISSIONS].

Container path	Permissions	Description
`/config`	rw	Stores the application's configuration, state, logs, and any files requiring persistency.
`/output`	rw	This is where downloaded files are stored.

Ports

The following table lists the ports used by the container.

When using the default bridge network, ports can be mapped to the host using the -p parameter with value in the format <HOST_PORT>:<CONTAINER_PORT>. The internal container port may not be changeable, but you can use any port on the host side.

See the Docker Docker Container Networking documentation for details.

Port	Protocol	Mapping to Host	Description
5800	TCP	Optional	Port to access the application's GUI via the web interface. Mapping to the host is optional if web access is not needed. For non-default bridge networks, the port can be changed with the `WEB_LISTENING_PORT` environment variable.
5900	TCP	Optional	Port to access the application's GUI via the VNC protocol. Mapping to the host is optional if VNC access is not needed. For non-default bridge networks, the port can be changed with the `VNC_LISTENING_PORT` environment variable.
3129	TCP	Optional	Port used by MyJDownloader mobile applications and browser extensions to establish a direct connect to the JDownloader Docker container instance. Port needs to be exposed only if MyJDownloader is enabled and configured in Direct Connection mode. NOTE: Since this port is being reported to the MyJDownloader online service, the port mapped on the host side must be the same (i.e. 3129).

Changing Parameters of a Running Container

Environment variables, volume mappings, and port mappings are specified when creating the container. To modify these parameters for an existing container, follow these steps:

Stop the container (if it is running):

docker stop jdownloader-2

Remove the container:

docker rm jdownloader-2

Recreate and start the container using the docker run command, adjusting parameters as needed.

Note

Since all application data is saved under the /config container folder, destroying and recreating the container does not result in data loss, and the application resumes with the same state, provided the /config folder mapping remains unchanged.

Docker Compose File

Below is an example docker-compose.yml file for use with Docker Compose.

Adjust the configuration to suit your needs. Only mandatory settings are included in this example.

version: '3'
services:
  jdownloader-2:
    image: jlesage/jdownloader-2
    ports:
      - "5800:5800"
    volumes:
      - "/docker/appdata/jdownloader-2:/config:rw"
      - "/home/user/Downloads:/output:rw"

Docker Image Versioning and Tags

Each release of a Docker image is versioned, and each version as its own image tag. Before October 2022, the versioning scheme followed semantic versioning.

Since then, the versioning scheme has shifted to calendar versioning with the format YY.MM.SEQUENCE, where:

YY is the zero-padded year (relative to year 2000).
MM is the zero-padded month.
SEQUENCE is the incremental release number within the month (first release is 1, second is 2, etc).

View all available tags on Docker Hub or check the Releases page for version details.

Docker Image Update

The Docker image is regularly updated to incorporate new features, fix issues, or integrate newer versions of the containerized application. Several methods can be used to update the Docker image.

If your system provides a built-in method for updating containers, this should be your primary approach.

Alternatively, you can use Watchtower, a container-based solution for automating Docker image updates. Watchtower seamlessly handles updates when a new image is available.

To manually update the Docker image, follow these steps:

Fetch the latest image:

docker pull jlesage/jdownloader-2

Stop the container:

docker stop jdownloader-2

Remove the container:

docker rm jdownloader-2

Recreate and start the container using the docker run command, with the same parameters used during initial deployment.

Synology

For Synology NAS users, follow these steps to update a container image:

Open the Docker application.
Click Registry in the left pane.
In the search bar, type the name of the container (jlesage/jdownloader-2).
Select the image, click Download, and choose the latest tag.
Wait for the download to complete. A notification will appear once done.
Click Container in the left pane.
Select your JDownloader 2 container.
Stop it by clicking Action -> Stop.
Clear the container by clicking Action -> Reset (or Action -> Clear if you don't have the latest Docker application). This removes the container while keeping its configuration.
Start the container again by clicking Action -> Start. NOTE: The container may temporarily disappear from the list while it is recreated.

unRAID

For unRAID users, update a container image with these steps:

Select the Docker tab.
Click the Check for Updates button at the bottom of the page.
Click the apply update link of the container to be updated.

User/Group IDs

When mapping data volumes (using the -v flag of the docker run command), permission issues may arise between the host and the container. Files and folders in a data volume are owned by a user, which may differ from the user running the application. Depending on permissions, this could prevent the container from accessing the shared volume.

To avoid this, specify the user the application should run as using the USER_ID and GROUP_ID environment variables.

To find the appropriate IDs, run the following command on the host for the user owning the data volume:

id <username>

This produces output like:

uid=1000(myuser) gid=1000(myuser) groups=1000(myuser),4(adm),24(cdrom),27(sudo),46(plugdev),113(lpadmin)

Use the uid (user ID) and gid (group ID) values to configure the container.

Accessing the GUI

Assuming the container's ports are mapped to the same host's ports, access the application's GUI as follows:

Via a web browser:

http://<HOST_IP_ADDR>:5800

Via any VNC client:

<HOST_IP_ADDR>:5900

Security

By default, access to the application's GUI uses an unencrypted connection (HTTP or VNC).

A secure connection can be enabled via the SECURE_CONNECTION environment variable. See the Environment Variables section for details on configuring environment variables.

When enabled, the GUI is accessed over HTTPS when using a browser, with all HTTP accesses redirected to HTTPS.

For VNC clients, the connection can be secured using on of two methods, configured via the SECURE_CONNECTION_VNC_METHOD environment variable:

SSL: An SSL tunnel is used to transport the VNC connection. Few VNC clients supports this method; SSVNC is one that does.
TLS: A VNC security type negotiated during the VNC handshake. It uses TLS to establish a secure connection. Clients may optionally validate the server’s certificate. Valid certificates must be provided for this validation to succeed. See Certificates for details. TigerVNC is a client that supports TLS encryption.

SSVNC

SSVNC is a VNC viewer that adds encryption to VNC connections by using an SSL tunnel to transport the VNC traffic.

While the Linux version of SSVNC works well, the Windows version has issues. At the time of writing, the latest version 1.0.30 fails with the error:

ReadExact: Socket error while reading

For convenience, an unofficial, working version is provided here:

https://github.com/jlesage/docker-baseimage-gui/raw/master/tools/ssvnc_windows_only-1.0.30-r1.zip

This version upgrades the bundled stunnel to version 5.49, resolving the connection issues.

Certificates

The following certificate files are required by the container. If missing, self-signed certificates are generated and used. All files are PEM-encoded x509 certificates.

Container Path	Purpose	Content
`/config/certs/vnc-server.pem`	VNC connection encryption.	VNC server's private key and certificate, bundled with any root and intermediate certificates.
`/config/certs/web-privkey.pem`	HTTPS connection encryption.	Web server's private key.
`/config/certs/web-fullchain.pem`	HTTPS connection encryption.	Web server's certificate, bundled with any root and intermediate certificates.

Tip

To avoid certificate validity warnings or errors in browsers or VNC clients, provide your own valid certificates.

Note

Certificate files are monitored, and relevant services are restarted when changes are detected.

VNC Password

To restrict access to your application, set a password using one of two methods:

Via the VNC_PASSWORD environment variable.
Via a .vncpass_clear file at the root of the /config volume, containing the password in clear text. During container startup, the content is obfuscated and moved to .vncpass.

The security of the VNC password depends on:

The communication channel (encrypted or unencrypted).
The security of host access.

When using a VNC password, enable a secure connection to prevent sending the password in clear text over an unencrypted channel.

Unauthorized users with sufficient host privileges can retrieve the password by:

Viewing the VNC_PASSWORD environment variable via docker inspect. By default, the docker command requires root access, but it can be configured to allow users in a specific group.
Decrypting the /config/.vncpass file, which requires root or USER_ID permissions.

Caution

VNC password is limited to 8 characters. This limitation comes from the Remote Framebuffer Protocol RFC (see section 7.2.2).

Web Authentication

Access to the application's GUI via a web browser can be protected with a login page. When enabled, users must provide valid credentials to gain access.

Enable web authentication by setting the WEB_AUTHENTICATION environment variable to 1. See the Environment Variables section for details on configuring environment variables.

Important

Web authentication requires a secure connection to be enabled. See Security for details.

Configuring Users Credentials

User credentials can be configured in two ways:

Via container environment variables.
Via a password database.

Container environment variables provide a quick way to configure a single user. Set the username and password using:

WEB_AUTHENTICATION_USERNAME
WEB_AUTHENTICATION_PASSWORD

See the Environment Variables section for details on configuring environment variables.

For a more secure method or to configure multiple users, use a password database at /config/webauth-htpasswd within the container. This file uses the Apache HTTP server's htpasswd format, storing bcrypt-hashed passwords.

Manage users with the webauth-user tool:

Add a user: docker exec -ti <container name> webauth-user add <username>
Update a user: docker exec -ti <container name> webauth-user update <username>
Remove a user: docker exec <container name> webauth-user del <username>
List users: docker exec <container name> webauth-user list

Reverse Proxy

The following sections provide NGINX configurations for setting up a reverse proxy to this container.

A reverse proxy server can route HTTP requests based on the hostname or URL path.

Routing Based on Hostname

In this scenario, each hostname is routed to a different application or container.

For example, if the reverse proxy server runs on the same machine as this container, it would proxy all HTTP requests for jdownloader-2.domain.tld to the container at 127.0.0.1:5800.

Here are the relevant configuration elements to add to the NGINX configuration:

map $http_upgrade $connection_upgrade {
	default upgrade;
	''      close;
}

upstream docker-jdownloader-2 {
	# If the reverse proxy server is not running on the same machine as the
	# Docker container, use the IP of the Docker host here.
	# Make sure to adjust the port according to how port 5800 of the
	# container has been mapped on the host.
	server 127.0.0.1:5800;
}

server {
	[...]

	server_name jdownloader-2.domain.tld;

	location / {
	        proxy_pass http://docker-jdownloader-2;
	}

	location /websockify {
		proxy_pass http://docker-jdownloader-2;
		proxy_http_version 1.1;
		proxy_set_header Upgrade $http_upgrade;
		proxy_set_header Connection $connection_upgrade;
		proxy_read_timeout 86400;
	}

	# Needed when audio support is enabled.
	location /websockify-audio {
		proxy_pass http://docker-jdownloader-2;
		proxy_http_version 1.1;
		proxy_set_header Upgrade $http_upgrade;
		proxy_set_header Connection $connection_upgrade;
		proxy_read_timeout 86400;
	}
}

Routing Based on URL Path

In this scenario, the same hostname is used, but different URL paths route to different applications or containers. For example, if the reverse proxy server runs on the same machine as this container, it would proxy all HTTP requests for server.domain.tld/filebot to the container at 127.0.0.1:5800.

Here are the relevant configuration elements to add to the NGINX configuration:

map $http_upgrade $connection_upgrade {
	default upgrade;
	''      close;
}

upstream docker-jdownloader-2 {
	# If the reverse proxy server is not running on the same machine as the
	# Docker container, use the IP of the Docker host here.
	# Make sure to adjust the port according to how port 5800 of the
	# container has been mapped on the host.
	server 127.0.0.1:5800;
}

server {
	[...]

	location = /jdownloader-2 {return 301 $scheme://$http_host/jdownloader-2/;}
	location /jdownloader-2/ {
		proxy_pass http://docker-jdownloader-2/;
		# Uncomment the following line if your Nginx server runs on a port that
		# differs from the one seen by external clients.
		#port_in_redirect off;
		location /jdownloader-2/websockify {
			proxy_pass http://docker-jdownloader-2/websockify;
			proxy_http_version 1.1;
			proxy_set_header Upgrade $http_upgrade;
			proxy_set_header Connection $connection_upgrade;
			proxy_read_timeout 86400;
		}
		# Needed when audio support is enabled.
		location /jdownloader-2/websockify-audio {
			proxy_pass http://docker-jdownloader-2/websockify-audio;
			proxy_http_version 1.1;
			proxy_set_header Upgrade $http_upgrade;
			proxy_set_header Connection $connection_upgrade;
			proxy_read_timeout 86400;
		}
	}
}

Web Audio

The container supports streaming audio from the application, played through the user's web browser. Audio is not supported for VNC clients.

Audio is streamed with the following specification:

Raw PCM format
2 channels
16-bit sample depth
44.1kHz sample rate

Enable web audio by setting WEB_AUDIO to 1. See the Environment Variables section for details on configuring environment variables.

Web File Manager

The container includes a simple file manager for interacting with container files through a web browser, supporting operations like renaming, deleting, uploading, and downloading.

Enable the file manager by setting WEB_FILE_MANAGER to 1. See the Environment Variables section for details on configuring environment variables.

By default, the container's entire filesystem is not accessible. The WEB_FILE_MANAGER_ALLOWED_PATHS environment variable is a comma-separated list that specifies which paths within the container are allowed to be accessed. When set to AUTO (the default), it automatically includes commonly used folders and any folders mapped to the container.

The WEB_FILE_MANAGER_DENIED_PATHS environment variable defines which paths are explicitly denied access by the file manager. A denied path takes precedence over an allowed one.

Shell Access

To access the shell of a running container, execute the following command:

docker exec -ti CONTAINER sh

Where CONTAINER is the ID or the name of the container used during its creation.

MyJDownloader

MyJDownloader is an online service providing remote access to your JDownloader with Web Interface, Android App, iPhone App, Windows Phone App and Browser Extensions. It allows to check download status, add links and solve captchas from everywhere.

To activate, open the JDownloader UI and click the My.JDownloader tab.

Direct Connection

When using MyJDownloader from a device on the same local network as the JDownloader Docker container instance, Direct Connection mode can be enabled to reduce the latency and increase the bandwidth. With this mode, instead of going through the cloud, the communication is done through a direct connection between the device and JDownloader.

The default container's network being in bridge mode, the Direct Connection mode is not automatically detected/activated and the following steps are required:

Make sure the container's port 3129 is mapped to the host port 3129. This is done by adding the parameter -p 3129:3129 to the docker run command.
Open the JDownloader UI.
Go to Settings->Advanced Settings.
Search for MyJDownloaderSettings.
Set Custom Device IPs to the IP address of the host running the container, using double quotes and brackets like this example: ["192.168.1.1"].
Change the Direct Connection Mode to Allow lan/wan connections with manual port forwarding.
Restart JDownloader (File->Restart).

Click'n'Load

The easiest way to use the Click'n'Load feature is by installing the MyJDownloader browser extension. With this method, the browser extension handles POST requests to http://127.0.0.1:9666 and forward the links to JDownloader via the MyJDownloader service.

Troubleshooting

JDownloader Fails to Start

If JDownloader displays an error indicating that it is unable to start, following these instruction might help fixing the problem.

Create the file .fix_jd_install, under the directory that has been mapped to /config. The content of the file is not important. However, if the latest JDownloader installer is required, setting the content to download causes the installer to be downloaded.
Restart the container.

The presence of the file causes the container to attempt fixing the installation during its startup. The repair process follows the instructions provided at:

https://support.jdownloader.org/en/knowledgebase/article/fix-jdownloader-installation

Support or Contact

Having troubles with the container or have questions? Please create a new issue.

For other Dockerized applications, visit https://jlesage.github.io/docker-apps.

Name		Name	Last commit message	Last commit date
Latest commit History 278 Commits
.github		.github
rootfs		rootfs
DOCKERHUB.md		DOCKERHUB.md
Do 8000 ckerfile		Dockerfile
LICENSE		LICENSE
README.md		README.md
appdefs.yml		appdefs.yml

Uh oh!

License

jlesage/docker-jdownloader-2

Folders and files

Latest commit

History

Repository files navigation

Docker container for JDownloader 2

Table of Contents

Quick Start

Usage

Environment Variables

Deployment Considerations

Data Volumes

Ports

Changing Parameters of a Running Container

Docker Compose File

Docker Image Versioning and Tags

Docker Image Update

Synology

unRAID

User/Group IDs

Accessing the GUI

Security

SSVNC

Certificates

VNC Password

Web Authentication

Configuring Users Credentials

Reverse Proxy

Routing Based on Hostname

Routing Based on URL Path

Web Audio

Web File Manager

Shell Access

MyJDownloader

Direct Connection

Click'n'Load

Troubleshooting

JDownloader Fails to Start

Support or Contact

About

Resources

License

Uh oh!

Stars

Watchers

Forks

Releases 55

Sponsor this project

Uh oh!

Packages 0

Uh oh!

Uh oh!

Contributors 2

Uh oh!

Languages

Packages