Sunday, 26 February 2017 12:15

Hubsoft-specific warnings

Several warning messages can be shown when connecting to a hub that runs on hubsoft that contain security vulnerabilities or violates ADC protocol specifications in a way that may affect the user.

This hub uses an outdated cryptographic protocol that has known security issues

TLS 1.0 (released on 1999) is known to contain various security vulnarebilities. Due to such issues, TLS 1.0 is no longer accepted for various security-critical transactions, such as credit card payments. Unfortunately outdated hubsofts are still being used that lack support for modern security protocols.

Several Linux distributions also set system-wide defaults for the required TLS version, and some of them already require TLS 1.2 or newer which prevents connections with outdated hubsofts and clients.

The hubsoft used by this hub doesn't forward Advanced Direct Connect protocol messages according to the protocol specifications, which may silently break various client features. Certain client functionality may have been disabled automatically in this hub.

Advanced Direct Connect protocol is the successor of the old NMDC protocol, which pays much attention to extensibility. Unfortunately certain hubsofts have chosen to ignore protocol specifications and disallow all extensibility, making adding of various new client features practically impossible. All violating hubsofts may not even forward base protocol commands, such as file searches, correctly. Since this may cause various user actions to unexpectedly fail without any error messages from the hub, AirDC++ may disable user features on per-hubsoft basis to avoid confusion to the user.

Monday, 22 August 2016 14:32

Setting parameters

Download path variables

%[username] - Replace with the name of the web user who queued the item (or with the system username if the download is initiated from the Windows GUI)

Time formating variables are supported as well.

/home/%[username]/Downloads/%Y-%m-%d/ (will be replaced with /home/mywebuser/Downloads/2016-08-02/)

Log variables

See the DC++ help page for available variables

Thursday, 19 May 2016 16:24

Web server

Web server functionality is included in AirDC++ 3.10 and newer versions.


Web server enables you to use a web-based user interface which can be accessed from any device by using a web browser (mobile devices are supported as well). It also includes a JSON-based Web API which can be used for scripting.

View online demo of the Web UI

Configuring web server

Go to Settings -> Web server. Add a login account and start the server. After that you can access the client from http://REPLACE_WITH_YOUR_SERVER_IP:5600 (assuming that you use the default port). Try opening the address http://localhost:5600 with your web browser when connecting from the same computer.

If you have feature requests for the Web UI, please post them to Github for the AirDC++ Web Client project. Note that you may also vote for existing feature requests to increase their likelihood for being implemented (a Github account is required).

Tuesday, 26 November 2013 21:48

Running a hub

AirDC++ has been designed to work with the ADC protocol, so it's highly recommend to use an ADC hubsoft to take advantage of various useful client features (e.g. share profiles, multiple per-user connections and IPv6).


ADC hubsofts


A multi-platform hubsoft that ships with relatively many features. Allows running Ptokax scripts through a bridge script.

Custom version of ADCH++ with hybrid IPv4/IPv6 support

In order to allow hybrid IPv4/IPv6 client-client connections as supported by AirDC++, you need to run an extended version of ADCH++. Note that the hub server needs to have IPv6 connectivity available for the feature to work.

Download the hybrid version of ADCH++...

Last update: 18.10.2020

Windows (64-bit)

See the ADCH++ guides for information about using the hubsoft. To make the hubsoft perform authentication for both protocols, you need to specify "HubAddress4" and "HubAddress6" attributes in the file "config/adchpp.xml" (there is more information available in the XML file).


Contains lots of inbuilt features and is available for multiple operating systems. Contains support for the NMDC protocol as well. No encryption support on Windows, no scipting API. High resource usage.


A hubsoft with relatively many native LUA scripts available. Available for multiple operating systems.


A high-performance hubsoft for Unix-like operating systems. Offers significantly less features than the other ones.


NMDC hubsofts

See the Wikipedia arcticle for information about the available hubsofts

Tuesday, 29 October 2013 21:19

Information for Developers

Fetching the source

The latest source code is located on Github.

There's also a source package available with each release from 

Compiling on Windows

The Windows version can be compiled with Visual Studio 2013

Compiling on other operating systems

The core has also been tested to compile on various Linux distributions and on OS X. Build script for compiling the source on other operating systems is available at the Github repository of AirDC++ nanoSee the guide for AirDC++ nano to get an idea about the required rependencies for compiling the client.

The supported compilers are GCC 4.7+ and Clang 3.3+.

Monday, 28 October 2013 17:19

AirDC++ nano

General information about AirDC++ nano (usage cases, screenshots...)

Thursday, 24 October 2013 17:19

User Guide (AirDC++ nano)

User guide for AirDC++ nano