{{ambox | type = delete | text = Prior to Debian Sid (Unstable) including Wheezy, Squeeze, and Lenny, the ZNC packages included in the repositories for those older releases are '''extremely old'''. There could be '''security issues and even bugs in the code'''. If you are having issues with ZNC from your Debian package manager (prior to Sid), it is recommended to uninstall that package and build from source, or use the third-party repository (noted below).}}

{{ambox | type = delete | text = Prior to Debian Sid (Unstable) including Wheezy, Squeeze, and Lenny, the ZNC packages included in the repositories for those older releases are '''extremely old'''. There could be '''security issues and even bugs in the code'''. If you are having issues with ZNC from your Debian package manager (prior to Sid), it is recommended to uninstall that package and build from source, or use the third-party repository (noted below).}}

−

−

{{ambox | type = notice | text = There is a third-party repository provided by [https://launchpad.net/~teward Thomas W.] which has updated Debian packages for Debian Wheezy and later. They are based directly off of the latest Debian packages in Debian's unstable or experimental repositories, and are built in a similar way to the PPAs. [http://wiki.znc.in/User:Resistance/Debian_Package_Repository_for_ZNC Details on the repository, and how to use it].}}

Debian provides [http://packages.debian.org/znc ZNC packages] which may be installed using:

Debian provides [http://packages.debian.org/znc ZNC packages] which may be installed using:

Source Tarball

If you want to compile ZNC with OpenSSL support, you need the OpenSSL development package. On Debian/Ubuntu this is called libssl-dev, on CentOS/Fedora/Red Hat it's openssl-devel, and on openSUSE it's libopenssl-devel.
A good way to install this and other dependencies is the build dependency feature of package managers (apt-get build-dep / yum-builddep / zypper source-install --build-deps-only).

./configure(use --prefix="$HOME/.local" if you don't want a system wide installation or simply don't have root access; use --with-openssl=/path/to/openssl if you have a non-standard SSL path)(use --help to see other configure options)

make(if you are on a dedicated server and your CPU has more than one core, you can use make -jX where X is the number of CPU cores to speed up compilation)

make install

Please note that compiling can take 5-10 minutes or more.

Once you have installed znc, you can use znc --makeconf to make a configuration file for ZNC. This config is stored in ~/.znc under the user you run it as. You should create a dedicated non root user to run znc under.

ZNC is run by just executing znc under the dedicated znc user, at which stage it goes to background. It does automatically not make an init.d service for itself (which can be done by following the instructions to running ZNC as a system daemon) nor does it need to be run in screen or something similar.

Linux

Docker

ZNC is available as an image in Docker Hub, and can be downloaded with:

docker pull znc

Follow the link above for additional instructions.

Debian

Prior to Debian Sid (Unstable) including Wheezy, Squeeze, and Lenny, the ZNC packages included in the repositories for those older releases are extremely old. There could be security issues and even bugs in the code. If you are having issues with ZNC from your Debian package manager (prior to Sid), it is recommended to uninstall that package and build from source, or use the third-party repository (noted below).

Ubuntu

You can either build ZNC from source, or use a PPA that was made by a community member to contain pre-built ZNC packages for all supported Ubuntu releases. Note that the PPA does not contain packages for every Ubuntu release, and the support dates for various Ubuntu versions is detailed here. If the release of Ubuntu you are on is not supported on the PPA, you will have to compile it from source yourself.

Build From Source

If you want to build znc from source to get a newer version than Ubuntu provides, you may need to determine capability of your system to build ZNC 1.6.0 (and newer) based on the version of Ubuntu.

Building from Git Master

If you are building from a source tarball for a stable release, skip this section. It is only needed for those building the development release (the master branch) on Git.

If you are trying to use the Git master version of the source code, then you will also need to ensure the following packages are also installed. You will not need to install these if you are using a stable release tarball, only if you are using Git master:

aclocal
pkg-config
automake
autoconf

After you have installed these packages, then continue onward for the additional dependencies you will need.

After installing dependencies, you will have to run autogen.sh to generate the configure script.

Add Build Dependency Sources

Older than Ubuntu 12.04

If you have any version of Ubuntu older than 12.04, you are incapable of building ZNC 1.6 or newer, due to the inability to install or build the ZNC build dependencies.

Ubuntu 12.04

If you are on Ubuntu 12.04, you will need to add three PPAs to your system, with the following commands:

rc.d scripts (deprecated)

You can read more about these scripts here. As of November 2012, initscripts support is being phased-out and expected to be totally deprecated in early 2013. Systemd scripts are already distributed in the package. The Archlinux wiki has some helpful information for new users who are getting started with znc.

Cygwin

If you don't want to use the provided packages, you can compile ZNC from source; for that you'll need the following packages installed: automake, gcc-g++, libicu-devel, make, mpfr, pkg-config, openssl-devel, zlib-devel. After installing these packages proceed to source tarball section (or git)