Jump to content


  • Content count

  • Joined

  • Last visited

  • Time Online

    1d 20h 4m 23s

Community Reputation

5 Neutral

About Basher

  • Rank
    The Basher

Contact Methods

  • Website URL

Profile Information

  • Gender

Recent Profile Visitors

6,805 profile views
  1. Closed Install eggdrop 1.8.3 cap coada

    Salut, ai urmat intocmai pasii de AICI si nu ai reusit?
  2. VPS servers may not be deployed with the timezone/date/time that you need on your server. Luckily, we can manually set the timezone to prevent issues with your server. Step 1: Check current timezone First off, check the date and time your server is currently set to: date This will return one line, such as: Tue Sep 1 17:31:29 UTC 2015 Tue being the day, Sep being the month, 1 being the day, 17:31:29 being the time, UTC being the timezone, and 2015 being the year. Step 2: Changing the timezone In order to change the timezone, we'll need to reconfigure the package tzdata. We can do this by typing: dpkg-reconfigure tzdata This will open a menu. Select the timezone you want to use by using your arrow keys and pressing tab to select the "OK" button. For example, say that we changed our timezone to "GMT-4", you will see the following message confirming that you changed the timezone: Current default time zone: 'Etc/GMT-4' Local time is now: Tue Sep 1 21:35:42 GMT-4 2015. Universal Time is now: Tue Sep 1 17:35:42 UTC 2015. You can double-check by executing the date command again: Tue Sep 1 21:38:37 GMT-4 2015 Step 3: Installing ntpd Ntpd is a daemon that synchronizes the time to remote NTP time servers so that the time on your server is always correct. Ntpd is installed on Ubuntu by default. To check the version you're currently using, type: ntpd --version If NTP is not installed yet, install it with apt-get: apt-get install ntp Step 4: Configuring ntpd You will now need to add a remote NTP time server. Open the config file: vi /etc/ntp.conf You can add servers in this format: server 0.pool.ntp.org server 1.pool.ntp.org server 2.pool.ntp.org server 3.pool.ntp.org Servers can be found on the NTP website. Step 5: Opening the port 123 ntpd requires being able to communicate over the port 123. Open this port with iptables: iptables -A INPUT -m state --state NEW -m udp -p udp --dport 123 -j ACCEPT Or, if you use ufw: ufw allow 123 Congratulations! You have now installed and configured ntpd.
  3. LAMP includes Apache, MySQL, PHP, and Ubuntu. This guide was written for Ubuntu 14.04. Step One: Install Apache Apache is a free open source software for web servers. To install Apache on Ubuntu, type these commands: sudo apt-get update sudo apt-get install apache2 Or just copy and paste this: sudo apt-get update; sudo apt-get install apache2 Tahhda. Let's check if Apache was installed correctly. Run the command: hostname -I and note down that IP. Open up your Internet Browser and direct your browser to that IP (Example: ). The page should load and say "It Works!". Step Two: Install MySQL MySQL is a database management system. Let's install MySQL on Ubuntu. Type these commands: sudo apt-get install mysql-server php5-mysql During the install, MySQL will request for you to setup a password. Once that has been installed, run these commands: sudo mysql_install_db Then write: sudo /usr/bin/mysql_secure_installation Step Three: Install PHP Now write these commands: sudo apt-get install php5 libapache2-mod-php5 php5-mcrypt Done.
  4. Let's Encrypt is a new certificate authority that allows you to issue SSL certificates for free. You can now use SSL without any extra costs. When using an SSL certificate, all traffic between the client and the server is encrypted -- which drastically improves your website security. This guide covers the installation of a Let's Encrypt certificate and automatic renewal on Ubuntu. By the end of this tutorial you will have an Apache server setup on Ubuntu 14.04 with Let's Encrypt. Step 1: Prerequisites You will need a Vultr SSD cloud server with Ubuntu 14.04 installed. You will also need a LAMP stack (Apache, PHP, etc.). If you do not yet have a LAMP stack installed on your Vultr server, please refer to the following knowledge base article: How to Install Apache, MySQL, and PHP on Ubuntu. Once you have a working LAMP Stack on your Ubuntu Server, you can proceed with with installing Let's Encrypt. In order to generate and install your SSL certificate, you will need Git to clone the Let's Encrypt repository: $[ubuntu] apt-get install git $[ubuntu] git clone https://github.com/letsencrypt/letsencrypt /opt/letsencrypt This will download the Let's Encrypt installer to /opt/letsencrypt. Step 2: Generating a Let's Encrypt SSL certificate Let's Encrypt verifies your domain by setting up a temporary web server process on your Ubuntu server. This process will run independently of your Apache server. After the SSL certificate has been generated, the temporary web server process will be automatically terminated by the Let's Encrypt installer. The installer will then install your newly created certificate on the Apache web server. $[ubuntu] ./letsencrypt-auto --apache -d yourubuntuserver.example If you want Let's Encrypt to generate an SSL certificate for even more domains, simply add those domains to the command. $[ubuntu] ./letsencrypt-auto --apache -d yourubuntuserver.example -d mysslcertificate.example This feature is very handy for securing your www subdomain. Right now, users who visit your website with the www prefix will get an SSL error. This kind of error will hurt your reputation. In order to resolve it, use a command like this: $[ubuntu] ./letsencrypt-auto --apache -d yourubuntuserver.example -d www.yourubuntuserver.example The Let's Encrypt client will now create a Let's Encrypt SSL certificate not only for yourubuntuserver.example but also for www.yourubuntuserver.example! Step 3: Forcing SSL You can now force your Apache server to route all HTTP requests to HTTPS. The best way to do this by creating an .htaccess file in your "www root" folder and appending the following rewrite code: RewriteEngine On RewriteCond % 80 RewriteRule ^(.*)$ https://letsencrypt.example/$1 [R,L] All incoming traffic on the HTTP port 80 will now automatically be redirected to port 443, which utilizes your LE SSL certificate. Step 4: Automatically renewing Let's Encrypt certificates As Let's Encrypt is a free certificate authority, SSL's can't be provided for one year or longer. All Let's Encrypt certificates are valid for 90 days. However, if you want to automatically renew them, this can be automated using a cron job. You can choose to renew certificates when they're about to expire. Open your crontab: $[ubuntu] crontab -e Append the following line to the crontab: 15 5 * * 5 /opt/letsencrypt/letsencrypt-auto renew >> /var/log/le-renew.log This cron job runs the /opt/letsencrypt/letsencrypt-auto renew command every Friday at 5:15 A.M. We have chosen to renew the certificates at this time because this is typically a period with little to no traffic on most sites. Therefore, visitors will not notice any delays because the server is under heavy load during the renewal and checking of all Let's Encrypt certificates. Your Ubuntu Server is now running a fully functional LAMP Stack and your website is using an SSL Certificate form Let's Encrypt with automatic renewal setup. It is possible to use more than one Let's Encrypt SSL certificate on your server; simply follow step #2 again for each domain. This concludes our tutorial, thank you for reading.
  5. PHP and related packages are the most commonly used components when deploying a web server. In this article, we will learn how to setup PHP 7.0 or PHP 7.1 on Ubuntu 16.04 LTS. Prerequisites An up-to-date Ubuntu 16.04 server instance. A sudo user. See instructions for Debian in this topic. Install and configure PHP 7.0 Since Ubuntu 16.04, PHP 7.0 has replaced PHP 5.x and become the default version of PHP in the official Ubuntu application repository. You can install and configure PHP 7.0 on your Ubuntu 16.04 system as follows. First of all, you can list all of the available PHP 7.0-related packages for review: apt-cache pkgnames | grep php7.0 Then you can install the package your to-be-deployed application requires. For example, if you want to deploy your application based on the LAMP stack, usually, you can install the below packages after installing Apache: sudo apt-get install -y apache2 sudo apt-get install -y php7.0 libapache2-mod-php7.0 php7.0-cli php7.0-common php7.0-mbstring php7.0-gd php7.0-intl php7.0-xml php7.0-mysql php7.0-mcrypt php7.0-zip Alternatively, if you want to deploy your application based on the LEMP stack, you can install the following packages after installing Nginx: sudo apt-get install -y nginx sudo apt-get install -y php7.0 php7.0-fpm php7.0-cli php7.0-common php7.0-mbstring php7.0-gd php7.0-intl php7.0-xml php7.0-mysql php7.0-mcrypt php7.0-zip After the installation, you can confirm that with: php -v The output should resemble: PHP 7.0.15-0ubuntu0.16.04.4 (cli) ( NTS ) Copyright (c) 1997-2017 The PHP Group Zend Engine v3.0.0, Copyright (c) 1998-2017 Zend Technologies with Zend OPcache v7.0.15-0ubuntu0.16.04.4, Copyright (c) 1999-2017, by Zend Technologies The main config file of PHP 7.0 will be saved as /etc/php/7.0/apache2/php.ini (Apache) or /etc/php/7.0/fpm/php.ini (Nginx). You can use the vi text editor to modify relevant settings in that file. sudo vi /etc/php/7.0/apache2/php.ini or: sudo vi /etc/php/7.0/fpm/php.ini Remember to restart Apache or Nginx if you make any changes to that file or any other PHP config files: sudo systemctl restart apache2.service or: sudo systemctl restart nginx.service php7.0-fpm.service Install and configure PHP 7.1 If you want to install PHP 7.1, the latest stable release of PHP at the time of writing this article, on Ubuntu 16.04, a convenient method is to use the PPA (Personal Package Archives) repository. First of all, you need to add specified PPA to the system apt repository: sudo apt-get install -y python-software-properties sudo add-apt-repository -y ppa:ondrej/php sudo apt-get update -y Then you can list all of the available PHP 7.1-related packages for review: apt-cache pkgnames | grep php7.1 From now on, you can install and configure PHP 7.1 in the same fashion as mentioned in the chapter about PHP 7.0 above. Basically, replacing 7.0 with 7.1 in relevant commands will get your job done. That's it. Thanks for reading.
  6. When deploying a web site or a web app, the most common web service solution for that is to setup a LAMP stack which consists of Linux, Apache, MySQL, and PHP. In this article, we will learn how to setup an up-to-date LAMP stack by installing the latest stable releases of Apache 2.4.x, MariaDB 10.x, and PHP 7.x on Ubuntu 16.04. Prerequisites An up-to-date Ubuntu 16.04 x64 server instance. A sudo user. See instructions for Debian in this topic. Step 1: Install Apache 2.4.x Install the latest stable release of Apache 2.4.x using the following command: sudo apt-get install apache2 -y Use the below command to confirm the installation: apache2 -v The output should resemble: Server version: Apache/2.4.18 (Ubuntu) Server built: 2016-07-14T12:32:26 In a production environment, you will want to remove the default Ubuntu Apache welcome page: sudo mv /var/www/html/index.html /var/www/html/index.html.bak For security purposes, you should prevent Apache from exposing files and directories within the web root directory /var/www/html to visitors: sudo cp /etc/apache2/apache2.conf /etc/apache2/apache2.conf.bak sudo sed -i "s/Options Indexes FollowSymLinks/Options FollowSymLinks/" /etc/apache2/apache2.conf Note: In accordance with your specific requirements, you can customize more settings in that file later. Start the Apache service and make it start on system boot: sudo systemctl start apache2.service sudo systemctl enable apache2.service Step 2: Install MariaDB 10.x At the time of writing this article, the current stable release of MariaDB is 10.1. You can use the following commands to install MariaDB 10.1 on your Ubuntu 16.04 x64 system. Setup the system apt repo: sudo apt-get install software-properties-common sudo apt-key adv --recv-keys --keyserver hkp://keyserver.ubuntu.com:80 0xF1656F24C74CD1D8 sudo add-apt-repository 'deb [arch=amd64,i386,ppc64el] http://mirror.jmu.edu/pub/mariadb/repo/10.1/ubuntu xenial main' Install MariaDB: sudo apt update -y sudo apt install -y mariadb-server During the installation process, the MariaDB package configuration wizard will automatically pop up and ask you to setup a new password for the MariaDB rootuser. For now, just press Enter every time the wizard pops up to skip this step because we will setup a password for the MariaDB root user in the following securing MariaDB procedure. Having MariaDB installed, you can confirm the installation with: mysql -V The output should be similar to: mysql Ver 15.1 Distrib 10.1.22-MariaDB, for debian-linux-gnu (x86_64) using readline 5.2 Start the MariaDB service: sudo systemctl start mariadb.service sudo systemctl enable mariadb.service Secure the installation of MariaDB: sudo /usr/bin/mysql_secure_installation During the interactive process, answer questions one by one as follows: Enter current password for root (enter for none): <Enter> Set root password? [Y/n]: Y New password: <your-MariaDB-root-password> Re-enter new password: <your-MariaDB-root-password> Remove anonymous users? [Y/n]: Y Disallow root login remotely? [Y/n]: Y Remove test database and access to it? [Y/n]: Y Reload privilege tables now? [Y/n]: Y Note: Be sure to replace <your-MariaDB-root-password> with your own MariaDB root password. In this fashion, MariaDB 10.1 has been securely installed onto your system. In the future, you can setup designated users and databases for your web apps as follows: Log into the MySQL shell as root: mysql -u root -p Type the MariaDB root password you set earlier when prompted. Create a MariaDB database webapp, a database user webappuser, and the database user's password yourpassword: CREATE DATABASE webapp; CREATE USER 'webappuser'@'localhost' IDENTIFIED BY 'yourpassword'; GRANT ALL PRIVILEGES ON webapp.* TO 'webappuser'@'localhost' IDENTIFIED BY 'yourpassword' WITH GRANT OPTION; FLUSH PRIVILEGES; EXIT; If necessary, you can customize MariaDB by reviewing and editing the main MariaDB config file which is /etc/mysql/my.cnf: sudo cp /etc/mysql/my.cnf /etc/mysql/my.cnf.bak sudo vi /etc/mysql/my.cnf Remember to restart the MariaDB service if you make any modifications to that file: sudo systemctl restart mariadb.service Step 3: Install PHP 7.0 or 7.1 When dealing with PHP 7.x, please refer to another topic which describes the process in detail. Step 4: Setup the UFW firewall By default, the UFW firewall on Ubuntu 16.04 is inactive. You should enable the UFW firewall in order to enhance security: sudo ufw app list sudo ufw allow OpenSSH sudo ufw allow in "Apache Full" sudo ufw enable That's all. After going through the above procedures, the LAMP stack would have been up and running on your Ubuntu 16.04 system. You can then deploy your own web app on the basis of the LAMP stack. Enjoy it!
  7. This tutorial explains how to setup a DNS server using Bind9 on Debian or Ubuntu. Throughout the article, substitute your-domain-name.com accordingly. At the end of the tutorial, you will have a functional Ubuntu DNS server. Install Bind9 apt-get install bind9 Configuration Backup current Bind9 settings. cp /etc/bind/named.conf.options /etc/bind/named.conf.options.bak Edit /etc/bind/named.conf.options and replace the content to following: options { directory "/var/cache/bind"; auth-nxdomain no; listen-on-v6 { any; }; statistics-file "/var/cache/bind/named.stats"; rrset-order {order cyclic;}; allow-transfer {; }; }; logging { channel b_query { file "/var/log/bind9/query.log" versions 2 size 1m; print-time yes; severity info; }; category queries { b_query; }; }; Create the log directory for Bind9. mkdir /var/log/bind9 chown bind:bind /var/log/bind9 Edit /etc/bind/named.conf to configure your domain zone file location. Append the following lines: zone "your-domain-name.com" { type master; file "/etc/bind/zones/your-domain-name.com.db"; }; Create your domain zone file at /etc/bind/zones/your-domain-name.com.db. Insert your DNS records by following this template: $TTL 86400 @ IN SOA ns1.your-domain-name.com. root.your-domain-name.com. ( 2014100801 ; Serial 43200 ; Refresh 3600 ; Retry 1209600 ; Expire 180 ) ; Minimum TTL ; Nameservers IN NS ns1.your-domain-name.com. IN NS ns2.your-domain-name.com. IN NS ns3.your-domain-name.com. ; Root site IN A 123.456.78.90 ; Hostname records * IN A 123.456.78.90 sub1 IN A 123.456.78.91 sub2 IN A 123.456.78.92 ; Aliases www IN CNAME your-domain-name.com. webmail IN CNAME ghs.google.com. ; MX records @ IN MX 1 aspmx.l.google.com. @ IN MX 3 alt1.aspmx.l.google.com. @ IN MX 3 alt2.aspmx.l.google.com. @ IN MX 5 aspmx2.googlemail.com. @ IN MX 5 aspmx3.googlemail.com. @ IN MX 5 aspmx4.googlemail.com. @ IN MX 5 aspmx5.googlemail.com. ; SPF records @ IN TXT "v=spf1 ip4: include:_spf.google.com ~all" Restart Bind9: /etc/init.d/bind9 restart You're all set. At this point, you may want to register your DNS server with your domain registrar. After doing that, you can change your existing name server to your own DNS server. If you come across problems and need to view errors, you may use the following command. /etc/init.d/bind9 status
  8. Install VestaCP on Debian

    Introduction VestaCP is a simple and clever hosting control panel with many features. Its installation is simple, and requires just one command. Vesta CP is beneficial for shared hosting, because one of its core features is that packages commonly used for shared hosting get installed automatically. This includes DNS server, mail server, and so forth. Requirements Debian 7 (Wheezy) Curl 512MB+ RAM 10 Minutes Installation As mentioned above, the installation process is done using a single command which installs all of the required packages, then configures them. First, we need to download the install script using the following command: curl -O http://vestacp.com/pub/vst-install.sh After we've downloaded the installation script, we have to set the permissions to run it: chmod +x vst-install.sh As of now, we can proceed with the installation of VestaCP using three different modes: Nginx with PHP-FPM bash vst-install.sh --nginx yes --phpfpm yes --apache no --vsftpd yes --proftpd no --exim yes --dovecot yes --spamassassin yes --clamav yes --named yes --iptables yes --fail2ban yes --mysql yes --postgresql no --remi yes --quota no --hostname <SERVER_HOSTNAME> --email <ADMIN_EMAIL> --password <ADMIN_PASSWORD> Nginx with Apache bash vst-install.sh --nginx yes --apache yes --phpfpm no --vsftpd yes --proftpd no --exim yes --dovecot yes --spamassassin yes --clamav yes --named yes --iptables yes --fail2ban yes --mysql yes --postgresql no --remi yes --quota no --hostname <SERVER_HOSTNAME> --email <ADMIN_EMAIL> --password <ADMIN_PASSWORD> Apache only bash vst-install.sh --nginx no --apache yes --phpfpm no --vsftpd yes --proftpd no --exim yes --dovecot yes --spamassassin yes --clamav yes --named yes --iptables yes --fail2ban yes --mysql yes --postgresql no --remi yes --quota no --hostname <SERVER_HOSTNAME> --email <ADMIN_EMAIL> --password <ADMIN_PASSWORD> Conclusion Your VestaCP panel is installed and ready for use. Happy hacking!
  9. Version


    This module converts the log files of your eggdrop to the html format. It also creates a page-calendar with links to that created files.


  10. zapdnsbl.tcl

    Version 0.6-dev


    ZAP DNS Blacklist is a script that take the host of a user joining a channel and check it against configured DNS blacklists (RBL). The configuration file is very similar to the format of BOPM. Author: Stefan Wold <ratler@stderr.eu> # Packages package require Tcl 8.5 package require inifile package require dns zapdnsbl-0.5.tar.bz2


  11. Bomba.tcl

    Version 0.4


    This is a small TCL script for Eggdrop. Timebomb is a game where one person asks the Eggdrop bot to plant a timebomb in another users pants.


  12. BogusTrivia-ro.tcl



    Scriptul Bogus Trivia (v2.06.4.6) tradus in romana de catre BaNdYt. Enjoy


  13. DuckHunt.zip

    Version 2.11


    Duck Hunt is a FPS script game for IRC. Duck Hunt is a remake of the classic arcade game by Nintendo. From time to time, a duck flies and players have to shoot it the most quickly possible.


  14. Flash Policy setup instructions When you can't connect to a server and the client shows a security sandbox violation message, the server the IRCd is running on does not allow connections from a Flash client. Due to the socket security policy Adobe introduced with Flash Player 9,0,124 you are forced to have a daemon that delivers a crossdomain.xml to allow establishing a connection. It is not a restriction of lightIRC, but one of Adobe Flash! Install Flash Policy without root access: wget http://www.lightirc.com/assets/policy/flashpolicyd.zip unzip flashpolicyd.zip cd flashpolicyd chmod a+x flashpolicyd.rb ./flashpolicyd.rb --xml flashpolicy.xml --logfile flashpolicyd.log --port 9009 Change port 9009 to any port that you prefer from 1024 to 60000. Verify that flashpolicyd is running: tail flashpolicyd.log If you see this message the flashpolicyd started succesfully: "Starting server on port xxx in process xxx" Sometime flashpolicyd might crash and to prevent it, you have to start it without generating logfile using: ./flashpolicyd.rb --xml flashpolicy.xml --logfile /dev/null --port 9009 NOTE: Make sure you have Ruby installed. If you have not, you can maybe install it with one of the following commands depending on your Linux distribution or through compiling the Ruby sources: apt-get install ruby (requires root access) Have fun!
  15. 1. First you need to update and upgrade your OS: root@radio:~# apt-get update root@radio:~# apt-get upgrade 2. Install the package that will be needed root@server:~# apt-get install nano gcc make zip openvpn build-essential pkg-config libxml2-dev icecast2 ezstream 3. After installations finished, we have to configure the icecast2 server, open and edit file /etc/icecast2/icecast.xml root@radio:~# nano /etc/icecast2/icecast.xml edit and adjust with the real condition and then restart service the icecast2 root@radio:~# /etc/init.d/icecast2 restart 4. Icecast will run at default port 8000, so try to visit: http://Server-IP:8000 (E,g or http://myradiodomain.com:8000) And you'll get a page like this, that icecast is running on your vps: 5. Install ezstream and there packages needed : 5a. Need to install libogg: root@radio:~# wget http://downloads.xiph.org/releases/ogg/libogg-1.3.2.tar.gz root@radio:~# tar xf libogg-1.3.2.tar.gz root@radio:~# cd libogg* root@radio:~# ./configure root@radio:~# make && make install 5.b. Need to install libvorbis: root@radio:~# wget http://downloads.xiph.org/releases/vorbis/vorbis-tools-1.4.0.tar.gz root@radio:~# tar xf libvorbis-1.4.0.tar.gz root@radio:~# cd libvorbis-1.4.0 root@radio:~# ./configure root@radio:~# make && make install 5.c. Need to install libshout: root@radio:~# wget http://downloads.xiph.org/releases/libshout/libshout-2.4.1.tar.gz root@radio:~# tar xf libshout-2.4.1.tar.gz root@radio:~# cd libshout-2.4.1 root@radio:~# ./configure root@radio:~# make && make install 5.d. And then install ezstream: root@radio:~# wget http://downloads.xiph.org/releases/ezstream/ezstream-0.6.0.tar.gz root@radio:~# tar xf ezstream-0.6.0.tar.gz root@radio:~# cd ezstream* root@radio:~# ./configure root@radio:~# make && make install 6. Make a directory to save playlist: E.g /home/mp3 root@radio:~# mkdir /home/mp3 7. And now you need to create .txt file root@radio:~# nano /home/mp3/playlist.txt And fill in the name of the song that is /home/mp3/namefile1.mp3 /home/mp3/namefile.mp3 /home/mp3/namefile.mp3 /home/mp3/namefile.mp3 etc, Then upload your MP3 files into /home/mp3 7. Configuring ezstream Copy file ezstream_mp3.xml to /root/ root@radio:~# cp /usr/share/doc/ezstream/examples/ezstream_mp3.xml /root/ezstream_mp3.xml And edit file /root/ezstream_mp3.xml root@radio:~# nano /root/ezstream_mp3.xml And please change as you want/real condition, then change permision: root@radio:~# chmod 0755 /root/ezstream_mp3.xml 8. Now run the ezstream by using screen: root@radio:~# screen -S "stream" root@radio:~# ezstream -c /root/ezstream_mp3.xml 9. To make a autoDJ on fallback mount and live on mount make 2 mount points. Open and edit file /etc/icecast2/icecast.xml root@radio:~# nano /etc/icecast2/icecast.xml Add this code after : <relay> --- </relay> < mount> < mount-name>/autodj< /mount-name> < password>my-password< /password> < max-listeners>500< / max-listeners> < max-listener-duration>3600< / max-listener-duration> < dump-file>/tmp/dump-live.mp3< / dump-file> < intro>< / intro> < charset>ISO8859-1< / charset> < public>1< / public> < stream-name>Radio< / stream-name> < stream-description> Radio< / stream-description> < stream-url>< / stream-url> < genre>Top40< / genre> < bitrate>64< / bitrate> < type>application/mp3< / type> < subtype>mp3< / subtype> < burst-size>65536< / burst-size> < mp3-metadata-interval>4096< / mp3-metadata-interval> < /mount> < mount> < mount-name>/live< / mount-name> < password>my-password< / password> < max-listeners>500< / max-listeners> < max-listener-duration>3600< / max-listener-duration> < dump-file>/tmp/dump-live.mp3< / dump-file> < intro>< / intro> < fallback-mount>/autodj< / fallback-mount> < fallback-override>1< / fallback-override> < fallback-when-full>1< / fallback-when-full> < charset>ISO8859-1< / charset> < public>1< / public> < stream-name>My Radio Server< / stream-name> < stream-description>Radio< / stream-description> < stream-url>< / stream-url> < genre>Top40< / genre> < bitrate>64< / bitrate> < type>application/mp3< / type> < subtype>mp3< / subtype> < burst-size>65536< / burst-size> < mp3-metadata-interval>4096< / mp3-metadata-interval> < / mount> And then save. Done (Configure server). You’re now streaming live on the Internet!