To create new wiki account, please join us on #znc at freenode and ask admins to create a wiki account for you. You can say thanks to spambots for this inconvenience.
- Installation Os Scripts
- Installation Steps Surprise Cake Rack
- Installation Os Mac
- Installation Os Scripts
Learn how to use NiceHash OS Flash Tool to prepare your USB drive for NiceHash OS installation.NiceHash OS Flash Tool will automatically download the latest. There are two ways to install ZNC on OS X, either using a package manager such as Homebrew or installing it yourself from source. See this blog post for a tutorial on how to compile ZNC from source. NOTE: If you are running on PPC architecture and cannot make the./configure && make && sudo make install dance work, you'll want to do the following.
| Languages: | English • Deutsch • русский • français • Bahasa Indonesia • italiano |
There are several possibilities to install ZNC on your machine. The latest version is always available using the source tarball from https://znc.in/releases.
A ChangeLog is available in the wiki.You can also read more about ZNC's portability.
- Which way should I choose for installing ZNC?
- If you don't have root access, the only way is to use source tarball. You'll need to use
./configure --prefix='$HOME/.local'as described. - If you have root access, you can use either source tarball or the convenient way for your distro. Check section about your distro for details, but be aware that these may contain old versions of ZNC!
Once you have installed ZNC, you can create a config file with znc --makeconf.
Development Versions[edit]
Read the git page if you want to get the current development version. Beware that this might have more bugs, more features, be a little unstable and eat your first born. You have been warned!
Source Tarball[edit]
Official source tarballs can be found here.
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).
- Download the latest source tarball
tar -xzvf znc-1.8.2.tar.gzcd znc-1.8.2mkdir buildcd buildcmake .
(usecmake . -DCMAKE_INSTALL_PREFIX='$HOME/.local'if you don't want a system wide installation or simply don't have root access; usecmake -DOPENSSL_ROOT_DIR=/path/to/opensslif you have a non-standard SSL path)
(useccmakeorcmake-guito see other configure options)make
(if you are on a dedicated server and your CPU has more than one core, you can usemake -jXwhere 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 not automatically 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.
- See the FAQ page if you encounter problems.
Linux[edit]
Docker[edit]
ZNC is available as an image in Docker Hub, and can be downloaded with:
docker pull znc
Follow the link above for additional instructions.
If you want to test great new features (and bugs!), unstable ZNC image is here.
Debian[edit]
Debian provides ZNC packages which may be installed using (stretch/stable, buster/testing, sid)
Debian Jessie LTS backports
If you want to build znc from source to get a newer version than Debian provides, you may need the following packages:
You can use the command
to install build dependencies automatically. Note that sometimes these build-depedencies are outdated and won't work with the current version of ZNC.
Fedora/CentOS/Red Hat Enterprise Linux[edit]
Fedora has znc packaged in it's main repository and their Extra Packages for Enterprise Linux (EPEL) repository provides them for CentOS/RHEL.
If using RHEL install the EPEL repository by downloading the appropriate package linked on EPEL's website.
Once you have EPEL installed (or are on Fedora), execute:
or dnf
Once installed you can configure znc by running:
Then finally to start it you can run:
Build from Source: CentOS 7+ only[edit]
If you really wish to build from source, then please follow the instructions here, written by Thomas Ward. Note that these instructions do utilize the EPEL repository in order to get all the necessary build dependencies (and there's a lot of them). These instructions work properly to create a basic ZNC installation. CentOS 7 or newer is needed because of the C++ standards being used, and older CentOS not having the required compilers for those standards.
Ubuntu[edit]
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[edit]
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[edit]
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:
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[edit]
Ubuntu 14.04[edit]If you are on Ubuntu 14.04, you will need to add one PPA to your system, with the following command:
Newer than Ubuntu 14.04[edit]You will not need any additional PPAs or sources for build dependencies.
Other Build Dependencies[edit]
After verifying you have the required build dependency sources, you will need to install the following packages:
After you have done this, you can follow the instructions on this page for compiling from the source tarball.
Install via PPA[edit]
A Personal Package Archive (PPA) has been created by Thomas W., and contains the latest stable ZNC release as exists in Debian. It contains packages for all releases of Ubuntu that are currently supported. Upgrade to mac os 10.11. It does not contain packages for versions of Ubuntu that are past their end of life dates. Click here if you wish to see the details of the packages in the PPA.
The versions of ZNC currently available in the PPA are detailed on the repository's information page but will only receive updates for currently-supported, non End of Life Ubuntu Releases.
First, make sure you have the python-software-properties package installed:
Then, add the PPA to your sources, and update the apt information:
Installation Os Scripts
Then, install the znc packages:
ZNC is now installed. You can create the configuration normally with this, when run on the user that you want to run ZNC as:
(open)SUSE[edit]
ZNC is part of the official repositories. To install, use the YaST GUI or install via commandline by typing
Gentoo[edit]
Gentoo provides ZNC packages which may be installed using:
Several USE Flags can be used for znc:
- daemon (local): (not offically supported) Allow znc to run as a system-wide service. Installs an init script and creates a znc user:group.
- debug (global): enable debug
- ipv6 (global): adds support for ipv6
- perl (global): adds support for writing perl modules
- python (global): adds support for writing python 3 modules
- ssl (global): enable secure socket layer connections
- sasl (global): sasl support
- tcl (global): adds support for writing tcl modules
Will print you a list of USE flags that will be used for znc
Slackware[edit]
Alpine Linux[edit]
To install znc from the package manager, enter the following command:
If you want to build znc from source to get a newer version than Alpine provides, you need to install packages with the following command:
If you want to run git, Debugging, perl, (requires swig), python, (requires swig), tcl, or cyrus then install the packages that correspond:
Archlinux[edit]
ZNC is part of the archlinux package repository, and can be installed with the following:
Additionally you can install the following optional dependencies to add support for additional modules.
- cyrus-sasl - saslauth module
- perl - modperl module
- python - modpython module
- tcl - modtcl module
Unstable/Testing[edit]
You can install the latest git snapshot from the Arch User Repository.
FreeBSD[edit]
ZNC is in FreeBSD ports, just do:
or pkg_add
Source Tarball[edit]
Official source tarballs can be found here.
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).
- Download the latest source tarball
tar -xzvf znc-1.8.2.tar.gzcd znc-1.8.2mkdir buildcd buildcmake .
(usecmake . -DCMAKE_INSTALL_PREFIX='$HOME/.local'if you don't want a system wide installation or simply don't have root access; usecmake -DOPENSSL_ROOT_DIR=/path/to/opensslif you have a non-standard SSL path)
(useccmakeorcmake-guito see other configure options)make
(if you are on a dedicated server and your CPU has more than one core, you can usemake -jXwhere 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 not automatically 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.
- See the FAQ page if you encounter problems.
Linux[edit]
Docker[edit]
ZNC is available as an image in Docker Hub, and can be downloaded with:
docker pull znc
Follow the link above for additional instructions.
If you want to test great new features (and bugs!), unstable ZNC image is here.
Debian[edit]
Debian provides ZNC packages which may be installed using (stretch/stable, buster/testing, sid)
Debian Jessie LTS backports
If you want to build znc from source to get a newer version than Debian provides, you may need the following packages:
You can use the command
to install build dependencies automatically. Note that sometimes these build-depedencies are outdated and won't work with the current version of ZNC.
Fedora/CentOS/Red Hat Enterprise Linux[edit]
Fedora has znc packaged in it's main repository and their Extra Packages for Enterprise Linux (EPEL) repository provides them for CentOS/RHEL.
If using RHEL install the EPEL repository by downloading the appropriate package linked on EPEL's website.
Once you have EPEL installed (or are on Fedora), execute:
or dnf
Once installed you can configure znc by running:
Then finally to start it you can run:
Build from Source: CentOS 7+ only[edit]
If you really wish to build from source, then please follow the instructions here, written by Thomas Ward. Note that these instructions do utilize the EPEL repository in order to get all the necessary build dependencies (and there's a lot of them). These instructions work properly to create a basic ZNC installation. CentOS 7 or newer is needed because of the C++ standards being used, and older CentOS not having the required compilers for those standards.
Ubuntu[edit]
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[edit]
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[edit]
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:
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[edit]
Ubuntu 14.04[edit]If you are on Ubuntu 14.04, you will need to add one PPA to your system, with the following command:
Newer than Ubuntu 14.04[edit]You will not need any additional PPAs or sources for build dependencies.
Other Build Dependencies[edit]
After verifying you have the required build dependency sources, you will need to install the following packages:
After you have done this, you can follow the instructions on this page for compiling from the source tarball.
Install via PPA[edit]
A Personal Package Archive (PPA) has been created by Thomas W., and contains the latest stable ZNC release as exists in Debian. It contains packages for all releases of Ubuntu that are currently supported. Upgrade to mac os 10.11. It does not contain packages for versions of Ubuntu that are past their end of life dates. Click here if you wish to see the details of the packages in the PPA.
The versions of ZNC currently available in the PPA are detailed on the repository's information page but will only receive updates for currently-supported, non End of Life Ubuntu Releases.
First, make sure you have the python-software-properties package installed:
Then, add the PPA to your sources, and update the apt information:
Installation Os Scripts
Then, install the znc packages:
ZNC is now installed. You can create the configuration normally with this, when run on the user that you want to run ZNC as:
(open)SUSE[edit]
ZNC is part of the official repositories. To install, use the YaST GUI or install via commandline by typing
Gentoo[edit]
Gentoo provides ZNC packages which may be installed using:
Several USE Flags can be used for znc:
- daemon (local): (not offically supported) Allow znc to run as a system-wide service. Installs an init script and creates a znc user:group.
- debug (global): enable debug
- ipv6 (global): adds support for ipv6
- perl (global): adds support for writing perl modules
- python (global): adds support for writing python 3 modules
- ssl (global): enable secure socket layer connections
- sasl (global): sasl support
- tcl (global): adds support for writing tcl modules
Will print you a list of USE flags that will be used for znc
Slackware[edit]
Alpine Linux[edit]
To install znc from the package manager, enter the following command:
If you want to build znc from source to get a newer version than Alpine provides, you need to install packages with the following command:
If you want to run git, Debugging, perl, (requires swig), python, (requires swig), tcl, or cyrus then install the packages that correspond:
Archlinux[edit]
ZNC is part of the archlinux package repository, and can be installed with the following:
Additionally you can install the following optional dependencies to add support for additional modules.
- cyrus-sasl - saslauth module
- perl - modperl module
- python - modpython module
- tcl - modtcl module
Unstable/Testing[edit]
You can install the latest git snapshot from the Arch User Repository.
FreeBSD[edit]
ZNC is in FreeBSD ports, just do:
or pkg_add
or pkgng
Mac OS X[edit]
There are two ways to install ZNC on OS X, either using a package manager such as Homebrew or installing it yourself from source. See this blog post for a tutorial on how to compile ZNC from source.
- NOTE: If you are running on PPC architecture and cannot make the ./configure && make && sudo make install dance work, you'll want to do the following:
- Make sure that you're using the --disable-perl switch for configure. Hence: ./configure --prefix=/usr/local --disable-perl
Homebrew[edit]
Installing Homebrew[edit]
For more information about Homebrew see here. The following command will install Homebrew to /usr/local
Homebrew requires Xcode and Mac OS X >= 10.5
Installing znc with Homebrew[edit]
Installing znc with MacPorts[edit]
Microsoft Windows[edit]
Warning: If you're going to install ZNC on your local Windows machine, it will probably be useless. You should run it on some machine (Windows or not), which is connected to internet 24/7.
Cygwin[edit]
Installation Steps Surprise Cake Rack
ZNC is available in list of cygwin packages.
Download Cygwin, install it. When choosing list of packages to install, search for 'znc'.
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)
WSL[edit]
Installation Os Mac
After ensuring that WSL (Windows Subsystem for Linux) itself works, follow the Linux instructions above.
Installation Os Scripts
