This chapter describes all available modules at the end of installation. All modules outside this section must be installed from Software center, including backup and users support.
The Dashboard page is the landing page after a successful login. The page will display the status and configurations of the system.
This tool is used to visualize disk usage in a simply and nice graph in which you can interact with click and double click to navigate in the directories tree.
After installation go in Dashboard and then Disk usage tab and click Update to index the root directory and to display the graph. This process can take several minutes depending on occupied disk space.
Well known folders are:
- Shared folders:
- User home directories:
- Windows roaming profiles:
- MySQL databases:
The Network page configures how the server is connected to the local network (LAN) or other ones (i.e. Internet).
If the server has firewall and gateway functionality, it will handle extra networks with special function like DMZ (DeMilitarized Zone) and guests network.
NethServer supports an unlimited number of network interfaces. Any network managed by the system must follow these rules:
- networks must be physically separated (multiple networks can’t be connected to the same switch/hub)
- networks must be logically separated: each network must have different addresses
- private networks, like LANs, must follow address’s convention from RFC1918 document. See Address for private networks (RFC1918)
Every network interface has a specific role which determinates its behavior. Roles are identified by colors. Each role correspond to a well-known zone with special network traffic rules:
- green: local network. Hosts on this network can access any other configured network
- blue: guests network. Hosts on this network can access orange and red network, but can’t access to green zone
- orange: DMZ network. Hosts on this network can access red networks, but can’t access to blue, orange and green zones
- red: public network. Hosts on this network can access only the server itself
See Policy for more information on roles and firewall rules.
The server must have at least one network interface. When the server has only one interface, this interface must have green role.
If the server is installed on a public VPS (Virtual Private Server), it should must be configured with a green interface. All critical services should be closed using Network services panel.
Use alias IP to assign more IP addresses to the same NIC.
The most common use is with a red interface: when the ISP provides a pool of public IP addresses (within the same subnet) you can add some (or all) of them to the same red interface and manage them individually (e.g. in the port forward configuration).
Alias IP section can be found in the dropdown menu of the related network interface.
Alias IPs on PPPoE interface could not work properly, due to different implementations of the service made by internet providers.
In Network page press New interface button to create a logical interface. Supported logical interfaces are:
- bond: arrange two or more network interfaces, provides load balancing and fault tolerance
- bridge: connect two different networks, it’s often used for bridged VPN and virtual machine
- VLAN (Virtual Local Area Network): create two or more logically separated networks using a single interface
- PPPoE (Point-to-Point Protocol over Ethernet): connect to Internet through a DSL modem
Bonds allow you to aggregate bandwidth or tollerate link faults. Bonds can be configured in multiple modes.
Modes providing load balancing and fault tolerance:
- Balance Round Robin (recommended)
- Balance XOR
- 802.3ad (LACP): it requires support at driver level and a switch with IEEE 802.3ad Dynamic link aggregation mode enabled
- Balance TLB: it requires support at driver level
- Balance ALB
Modes providing fault tolerance only:
- Active backup (recommended)
- Broadcast policy
A bridge has the function to connect different network segments, for example by allowing virtual machines, or client connected using a VPN, to access to the local network (green).
When it is not possible to physically separate two different networks, you can use a tagged VLAN. The traffic of the two networks can be transmitted on the same cable, but it will be handled as if it were sent and received on separate network cards. The use of VLAN, requires properly configured switches.
The PPPoE logical interface must be assigned the red role, thus requires the gateway functionality. See Firewall and gateway for details.
Address for private networks (RFC1918)¶
TCP/IP private networks not directly connected to Internet should use special addresses selected by Internet Assigned Numbers Authority (IANA).
|Private network||Subnet mask||IP addresses interval|
|10.0.0.0||255.0.0.0||10.0.0.1 - 10.255.255.254|
|172.16.0.0||255.240.0.0||172.16.0.1 - 172.31.255.254|
|192.168.0.0||255.255.0.0||192.168.0.1 - 192.168.255.254|
A network service is a service running on the firewall itself.
These services are always available to hosts on green network (local network). Access policies can be modified from Network services page.
Available policies are:
- Access only from green networks (private): all hosts from green networks and from VPNs
- Access from green and red networks (public): any host from green networks, VPNs and external networks. But not guests (blue) and DMZ (orange) networks
- Access only from the server itself (none): no host can connect to selected service
If selected policy is private or public, it’s possible to add hosts and networks which are always allowed (or blocked) using Allow hosts and Deny hosts. This rule also apply for blue and orange networks.
Given the following configuration:
- Orange network: 192.168.2.0/24
- Access for NTP server set to private
If hosts from DMZ must access NTP server, add 192.168.2.0/24 network inside the Allow hosts field.
Trusted networks are special networks (local, VPNs or remote) allowed to access special server’s services.
For example, hosts inside trusted networks can access to:
- Server Manager
- Shared folders (SAMBA)
If the remote network is reachable using a router, remember to add a static route inside Static routes page.
This page allow to create special static routes which will use the specified gateway. These routes are usually used to connect private network.
Remember to add the network to Trusted networks, if you wish to allow remote hosts to access local services.
The Organization contacts page fields are used as default values for user accounts. The organization name and address are also displayed on the Server Manager login screen.
The Server certificate page shows the currently installed SSL certificate that is provided by all system services.
The Generate certificate button allows generating a new self-signed SSL certificate. When a new certificate is generated, all SSL services are restarted and network clients will be required to accept the new certificate.
To avoid problems while importing the certificate in Internet Explorer, the Common Name (CN) field should match the server FQDN.
Install a custom certificate¶
Custom certificates should be placed inside the following standard directories:
/etc/pki/tls/certs: public key
/etc/pki/tls/private: private key
Set the private key and certificate file paths:
db configuration setprop pki CrtFile '/path/to/cert/pem-formatted.crt' db configuration setprop pki KeyFile '/path/to/private/pem-formatted.key'
You can also set a SSL certificate chain file:
db configuration setprop pki ChainFile '/path/to/cert/pem-formatted-chain.crt'
Notify registered daemons about certificate update:
Custom certificate backup¶
Always remember to add custom certificates to configuration backup.
Just add the paths inside
For example, if the certificate is
/etc/pki/tls/certs/mycert.crt, simply execute:
echo "/etc/pki/tls/certs/mycert.crt" >> /etc/backup-config.d/custom.include
Let’s Encrypt certificate¶
Let’s Encrypt is a free, automated, and open certificate authority brought to you by the non-profit Internet Security Research Group (ISRG). It can create free valid SSL certificate for you server.
The Let’s Encrypt Client is a fully-featured, extensible client for the Let’s Encrypt CA (or any other CA that speaks the ACME protocol) that can automate the tasks of obtaining certificates and configuring webservers to use them.
The server must be reachable from outside at port 80.
Make sure your port 80 is open to the public Internet, you can check with sites like http://www.canyouseeme.org/
The fully qualified name (FQDN) of the server must be a public domain name associated to its own public IP.
Make sure you have a public DNS name pointing to your server, you can check with sites like http://viewdns.info/
How it works¶
The system will release a single certificate for server FQDN (Fully Qualified Domain Name).
When you want to access your server, you MUST always use the FQDN, but sometimes the server has multiple aliases. Let’s Encrypt can add extra valid names to the FQDN certificate, so you will be able to access the server with other names.
The server FQDN is: ‘’server.nethserver.org’’ with public IP ‘‘188.8.131.52’‘. But you want to access the server also using this names (aliases):’’ mail.nethserver.org’’ and ‘’www.nethserver.org’‘.
The server must:
- have the port 80 open to the public internet: if you access http://184.108.40.206 from a remote site you must see NethServer landing page
- have a DNS public record for ‘’server.nethserver.org’‘, ‘’mail.nethserver.org’’ and ‘’www.nethserver.org’‘. All DNS records must point to the same server (it may have multiple public IP addresses, though)
Install the package from command line:
yum install nethserver-letsencrypt
Let’s Encrypt configuration must be done from command line using the root user. Access the server with a monitor or connect to it with SSH.
Certificate for FQDN¶
Enable Let’s Encrypt globally, this will automatically enable the generation of a certificate for the FQDN. Execute:
config setprop pki LetsEncrypt enabled signal-event nethserver-letsencrypt-update
Certificate for server alias (optional)
The FQDN certificate can be extended to be valid also for extra domains configured as server alias. This feature is called SubjectAltName (SAN): https://en.wikipedia.org/wiki/SubjectAltName
Create a server alias inside the DNS page, then enable Let’s Encrypt on the newly created record.
Example for ‘’alias.mydomain.com’’ alias:
db hosts setprop alias.mydomain.com LetsEncrypt enabled
You can customize the following options by using config command:
LetsEncryptMail: if set, Let’s Encrypt will send notification about your certificate to this mail address (this must be set before executing the letsencrypt-certs script for the first time!)
LetsEncryptRenewDays: minimum days before expiration to automatically renew certificate (default: 30)
config setprop pki LetsEncryptMail firstname.lastname@example.org signal-event nethserver-letsencrypt-update
Test certificate creation¶
Since you can request the certificate maximum 5 times per week, make sure the configuration is correct by requesting a fake certificate. Execute:
/usr/libexec/nethserver/letsencrypt-certs -v -t
This command will try to generate a fake certificate using Let’s Encrypt server. If everything goes well, the output should be something like this:
INFO: Using main config file /tmp/3XhzEPg7Dt + Generating account key... + Registering account key with letsencrypt... Processing test1.neth.eu + Signing domains... + Creating new directory /etc/letsencrypt.sh/certs/test1.neth.eu ... + Generating private key... + Generating signing request... + Requesting challenge for test1.neth.eu... + Responding to challenge for test1.neth.eu... + Challenge is valid! + Requesting certificate... + Checking certificate... + Done! + Creating fullchain.pem... + Done!
Verify the presented certificate has been signed by Let’s Encrypt CA on all SSL-enabled services like: If something goes wrong, please make sure all prerequisites are met.
Obtaining a valid certificate¶
If your configuration has been validated by the testing step, you’re ready to request a new valid certificate. Execute the following script against the real Let’s Encrypt server:
Access your http server and check your certificate is valid.
Change user password¶
All users can login to Server Manager using their own credentials and access the user profile.
After login, a user can change the password and information about the account, like:
- Name and surname
- External mail address
The user can also overwrite fields set by the administrator:
The machine where NethServer is installed can be rebooted or halted from thepage. Choose an option (reboot or halt) then click on submit button.
Always use this module to avoid bad shutdown which can cause data damages.
All services will save operations inside files called logs. The log analysis is the main tool to find and resolve problems. To analyze log files click in.
This module allows to:
- start search on all server’s logs
- display a single log
- follow the content of a log in real time
Date and time¶
After installation, make sure the server is configured with the correct timezone. The machine clock can be configured manually or automatically using public NTP servers (preferred).
The machine clock is very important in many protocols. To avoid problems, all hosts in LAN can be configured to use the server as NTP server.
All packages inside the Server Manager contain an inline help. The inline help explains how the module works and all available options.
These help pages are available in all Server Manager’s languages.
A list of all available inline help pages can be found at the address:
If the server has address
192.168.1.2, and you want to see all English help pages, use this address: