Сейчас 127 заметки.

Редактирование: Установка/настройка хостинг панели ISPConfig 3 на Debian

Материал из ЗАметки

Внимание! Вы не авторизовались на сайте. Ваш IP-адрес будет публично видимым, если вы будете вносить любые правки. Если вы войдёте или создадите учётную запись, правки вместо этого будут связаны с вашим именем пользователя, а также у вас появятся другие преимущества.

Правка может быть отменена. Пожалуйста, просмотрите сравнение версий, чтобы убедиться, что это именно те изменения, которые вас интересуют, и нажмите «Записать страницу», чтобы ваша отмена правки была сохранена.

Текущая версия Ваш текст
Строка 551: Строка 551:
  
 
To install ISPConfig 3 from the latest released version, do this:
 
To install ISPConfig 3 from the latest released version, do this:
<pre>
+
 
 
cd /tmp
 
cd /tmp
 
wget http://www.ispconfig.org/downloads/ISPConfig-3-stable.tar.gz
 
wget http://www.ispconfig.org/downloads/ISPConfig-3-stable.tar.gz
 
tar xfz ISPConfig-3-stable.tar.gz
 
tar xfz ISPConfig-3-stable.tar.gz
 
cd ispconfig3_install/install/
 
cd ispconfig3_install/install/
</pre>
+
 
 
The next step is to run
 
The next step is to run
php -q install.php
+
 
 +
php -q install.php
  
 
This will start the ISPConfig 3 installer. The installer will configure all services like Postfix, Dovecot, etc. for you. A manual setup as required for ISPConfig 2 (perfect setup guides) is not necessary.
 
This will start the ISPConfig 3 installer. The installer will configure all services like Postfix, Dovecot, etc. for you. A manual setup as required for ISPConfig 2 (perfect setup guides) is not necessary.
Строка 564: Строка 565:
 
root@server1:/tmp/ispconfig3_install/install# php -q install.php
 
root@server1:/tmp/ispconfig3_install/install# php -q install.php
  
[[Файл:ISP.jpg]]
+
 
 +
--------------------------------------------------------------------------------
 +
_____ ___________  _____              __ _        ____
 +
|_  _/  ___| ___ \ /  __ \            / _(_)      /__  \
 +
  | | \ `--.| |_/ / | /  \/ ___  _ __ | |_ _  __ _    _/ /
 +
  | |  `--. \  __/  | |    / _ \| '_ \|  _| |/ _` |  |_ |
 +
_| |_/\__/ / |    | \__/\ (_) | | | | | | | (_| | ___\ \
 +
\___/\____/\_|      \____/\___/|_| |_|_| |_|\__, | \____/
 +
                                              __/ |
 +
                                            |___/
 +
--------------------------------------------------------------------------------
 +
 
  
 
>> Initial configuration
 
>> Initial configuration
Строка 592: Строка 604:
  
 
Generating a 2048 bit RSA private key
 
Generating a 2048 bit RSA private key
 
 
....+++
 
....+++
 
 
............................+++
 
............................+++
 
 
writing new private key to 'smtpd.key'
 
writing new private key to 'smtpd.key'
 
-----
 
-----
Строка 606: Строка 615:
 
If you enter '.', the field will be left blank.
 
If you enter '.', the field will be left blank.
 
-----
 
-----
<pre>
 
 
Country Name (2 letter code) [AU]: <-- ENTER
 
Country Name (2 letter code) [AU]: <-- ENTER
 
 
State or Province Name (full name) [Some-State]: <-- ENTER
 
State or Province Name (full name) [Some-State]: <-- ENTER
 
 
Locality Name (eg, city) []: <-- ENTER
 
Locality Name (eg, city) []: <-- ENTER
 
 
Organization Name (eg, company) [Internet Widgits Pty Ltd]: <-- ENTER
 
Organization Name (eg, company) [Internet Widgits Pty Ltd]: <-- ENTER
 
 
Organizational Unit Name (eg, section) []: <-- ENTER
 
Organizational Unit Name (eg, section) []: <-- ENTER
 
 
Common Name (eg, YOUR name) []: <-- ENTER
 
Common Name (eg, YOUR name) []: <-- ENTER
 
 
Email Address []: <-- ENTER
 
Email Address []: <-- ENTER
 
 
Configuring Jailkit
 
Configuring Jailkit
 
 
Configuring Dovecot
 
Configuring Dovecot
 
 
Configuring Spamassassin
 
Configuring Spamassassin
 
 
Configuring Amavisd
 
Configuring Amavisd
 
 
Configuring Getmail
 
Configuring Getmail
 
 
Configuring Pureftpd
 
Configuring Pureftpd
 
 
Configuring BIND
 
Configuring BIND
 
 
Configuring Apache
 
Configuring Apache
 
 
Configuring Vlogger
 
Configuring Vlogger
 
 
Configuring Apps vhost
 
Configuring Apps vhost
 
 
Configuring Firewall
 
Configuring Firewall
 
 
Installing ISPConfig
 
Installing ISPConfig
 
 
ISPConfig Port [8080]: <-- ENTER
 
ISPConfig Port [8080]: <-- ENTER
 
  
 
Configuring DBServer
 
Configuring DBServer
 
 
Installing ISPConfig crontab
 
Installing ISPConfig crontab
 
 
no crontab for root
 
no crontab for root
 
 
no crontab for getmail
 
no crontab for getmail
 
 
Restarting services ...
 
Restarting services ...
 
 
Stopping MySQL database server: mysqld.
 
Stopping MySQL database server: mysqld.
 
 
Starting MySQL database server: mysqld.
 
Starting MySQL database server: mysqld.
 
 
Checking for corrupt, not cleanly closed and upgrade needing tables..
 
Checking for corrupt, not cleanly closed and upgrade needing tables..
 
 
Stopping Postfix Mail Transport Agent: postfix.
 
Stopping Postfix Mail Transport Agent: postfix.
 
 
Starting Postfix Mail Transport Agent: postfix.
 
Starting Postfix Mail Transport Agent: postfix.
 
 
Stopping amavisd: amavisd-new.
 
Stopping amavisd: amavisd-new.
 
 
Starting amavisd: amavisd-new.
 
Starting amavisd: amavisd-new.
 
 
Stopping ClamAV daemon: clamd.
 
Stopping ClamAV daemon: clamd.
 
 
Starting ClamAV daemon: clamd Bytecode: Security mode set to "TrustSigned".
 
Starting ClamAV daemon: clamd Bytecode: Security mode set to "TrustSigned".
 
 
.
 
.
 
 
If you have trouble with authentication failures,
 
If you have trouble with authentication failures,
 
enable auth_debug setting. See http://wiki.dovecot.org/WhyDoesItNotWork
 
enable auth_debug setting. See http://wiki.dovecot.org/WhyDoesItNotWork
Строка 683: Строка 656:
 
Restarting IMAP/POP3 mail server: dovecot.
 
Restarting IMAP/POP3 mail server: dovecot.
 
Restarting web server: apache2 ... waiting ..
 
Restarting web server: apache2 ... waiting ..
Restarting ftp server: Running: /usr/sbin/pure-ftpd-mysql-virtualchroot -l  
+
Restarting ftp server: Running: /usr/sbin/pure-ftpd-mysql-virtualchroot -l mysql:/etc/pure-ftpd/db/mysql.conf -l pam -Y 1 -8 UTF-8 -H -D -b -O clf:/var/log/pure-ftpd/transfer.log -E -u 1000 -A -B
mysql:/etc/pure-ftpd/db/mysql.conf -l pam -Y 1 -8 UTF-8 -H -D -b -O clf:/var/log/
 
pure-ftpd/transfer.log -E -u 1000 -A -B
 
 
Installation completed.
 
Installation completed.
 
root@server1:/tmp/ispconfig3_install/install#
 
root@server1:/tmp/ispconfig3_install/install#
</pre>
 
  
 
The installer automatically configures all underlying services, so no manual configuration is needed.
 
The installer automatically configures all underlying services, so no manual configuration is needed.
Строка 694: Строка 664:
 
Afterwards you can access ISPConfig 3 under http://server1.example.com:8080/ or http://192.168.0.100:8080/. Log in with the username admin and the password admin (you should change the default password after your first login):
 
Afterwards you can access ISPConfig 3 under http://server1.example.com:8080/ or http://192.168.0.100:8080/. Log in with the username admin and the password admin (you should change the default password after your first login):
  
[[Файл:40.png]]
 
  
[[Файл:41.png]]
 
  
 +
Click to enlarge
 +
 +
 +
Click to enlarge
 
The system is now ready to be used.
 
The system is now ready to be used.
  
 
   
 
   
  
====16.1 ISPConfig 3 Manual====
+
19.1 ISPConfig 3 Manual
 
 
 
In order to learn how to use ISPConfig 3, I strongly recommend to download the ISPConfig 3 Manual.
 
In order to learn how to use ISPConfig 3, I strongly recommend to download the ISPConfig 3 Manual.
  
Строка 710: Строка 681:
 
   
 
   
  
====16.2 ISPConfig Monitor App For Android====
+
19.2 ISPConfig Monitor App For Android
 
With the ISPConfig Monitor App, you can check your server status and find out if all services are running as expected. You can check TCP and UDP ports and ping your servers. In addition to that you can use this app to request details from servers that have ISPConfig installed (please note that the minimum installed ISPConfig 3 version with support for the ISPConfig Monitor App is 3.0.3.3!); these details include everything you know from the Monitor module in the ISPConfig Control Panel (e.g. services, mail and system logs, mail queue, CPU and memory info, disk usage, quota, OS details, RKHunter log, etc.), and of course, as ISPConfig is multiserver-capable, you can check all servers that are controlled from your ISPConfig master server.
 
With the ISPConfig Monitor App, you can check your server status and find out if all services are running as expected. You can check TCP and UDP ports and ping your servers. In addition to that you can use this app to request details from servers that have ISPConfig installed (please note that the minimum installed ISPConfig 3 version with support for the ISPConfig Monitor App is 3.0.3.3!); these details include everything you know from the Monitor module in the ISPConfig Control Panel (e.g. services, mail and system logs, mail queue, CPU and memory info, disk usage, quota, OS details, RKHunter log, etc.), and of course, as ISPConfig is multiserver-capable, you can check all servers that are controlled from your ISPConfig master server.
  
 
For download and usage instructions, please visit http://www.ispconfig.org/ispconfig-3/ispconfig-monitor-app-for-android/.
 
For download and usage instructions, please visit http://www.ispconfig.org/ispconfig-3/ispconfig-monitor-app-for-android/.
  
===17. Additional Notes===
+
  
====17.1 OpenVZ====
+
20 Additional Notes
 +
20.1 OpenVZ
 
If the Debian server that you've just set up in this tutorial is an OpenVZ container (virtual machine), you should do this on the host system (I'm assuming that the ID of the OpenVZ container is 101 - replace it with the correct VPSID on your system):
 
If the Debian server that you've just set up in this tutorial is an OpenVZ container (virtual machine), you should do this on the host system (I'm assuming that the ID of the OpenVZ container is 101 - replace it with the correct VPSID on your system):
  
<pre>
 
 
VPSID=101
 
VPSID=101
for CAP in CHOWN DAC_READ_SEARCH SETGID SETUID NET_BIND_SERVICE NET_ADMIN
+
for CAP in CHOWN DAC_READ_SEARCH SETGID SETUID NET_BIND_SERVICE NET_ADMIN SYS_CHROOT SYS_NICE CHOWN DAC_READ_SEARCH SETGID SETUID NET_BIND_SERVICE NET_ADMIN SYS_CHROOT SYS_NICE
SYS_CHROOT SYS_NICE CHOWN DAC_READ_SEARCH SETGID SETUID NET_BIND_SERVICE NET_
 
ADMIN SYS_CHROOT SYS_NICE
 
 
do
 
do
 
   vzctl set $VPSID --capability ${CAP}:on --save
 
   vzctl set $VPSID --capability ${CAP}:on --save
 
done
 
done
</pre>
 
  
====17.2 SquirrelMail====
+
 +
 
 +
20.2 SquirrelMail
 
Lots of people have reported problems (such as getting 404 Not Found errors) using the SquirrelMail webmail package in their web sites created through ISPConfig 3. This guide explains how to configure SquirrelMail on a Debian Squeeze server so that you can use it from within your web sites (created through ISPConfig).
 
Lots of people have reported problems (such as getting 404 Not Found errors) using the SquirrelMail webmail package in their web sites created through ISPConfig 3. This guide explains how to configure SquirrelMail on a Debian Squeeze server so that you can use it from within your web sites (created through ISPConfig).
  
 
SquirrelMail's Apache configuration is in the file /etc/squirrelmail/apache.conf, but this file isn't loaded by Apache because it is not in the /etc/apache2/conf.d/ directory. Therefore we create a symlink called squirrelmail.conf in the /etc/apache2/conf.d/ directory that points to /etc/squirrelmail/apache.conf and reload Apache afterwards:
 
SquirrelMail's Apache configuration is in the file /etc/squirrelmail/apache.conf, but this file isn't loaded by Apache because it is not in the /etc/apache2/conf.d/ directory. Therefore we create a symlink called squirrelmail.conf in the /etc/apache2/conf.d/ directory that points to /etc/squirrelmail/apache.conf and reload Apache afterwards:
  
<pre>
 
 
cd /etc/apache2/conf.d/
 
cd /etc/apache2/conf.d/
 
ln -s ../../squirrelmail/apache.conf squirrelmail.conf
 
ln -s ../../squirrelmail/apache.conf squirrelmail.conf
 
/etc/init.d/apache2 reload
 
/etc/init.d/apache2 reload
</pre>
 
  
 
Now open /etc/apache2/conf.d/squirrelmail.conf...
 
Now open /etc/apache2/conf.d/squirrelmail.conf...
vi /etc/apache2/conf.d/squirrelmail.conf
+
 
 +
vi /etc/apache2/conf.d/squirrelmail.conf
  
 
... and add the following lines to the <Directory /usr/share/squirrelmail></Directory> container that make sure that mod_php is used for accessing SquirrelMail, regardless of what PHP mode you select for your website in ISPConfig:
 
... and add the following lines to the <Directory /usr/share/squirrelmail></Directory> container that make sure that mod_php is used for accessing SquirrelMail, regardless of what PHP mode you select for your website in ISPConfig:
  
<pre>
 
 
[...]
 
[...]
 
<Directory /usr/share/squirrelmail>
 
<Directory /usr/share/squirrelmail>
Строка 757: Строка 725:
 
     php_value include_path .
 
     php_value include_path .
 
     php_admin_value upload_tmp_dir /var/lib/squirrelmail/tmp
 
     php_admin_value upload_tmp_dir /var/lib/squirrelmail/tmp
     php_admin_value open_basedir /usr/share/squirrelmail:/etc/squirrelmail:
+
     php_admin_value open_basedir /usr/share/squirrelmail:/etc/squirrelmail:/var/lib/squirrelmail:/etc/hostname:/etc/mailname:/var/spool/squirrelmail
/var/lib/squirrelmail:/etc/hostname:/etc/mailname:/var/spool/squirrelmail
 
 
     php_flag register_globals off
 
     php_flag register_globals off
 
   </IfModule>
 
   </IfModule>
Строка 772: Строка 739:
 
</Directory>
 
</Directory>
 
[...]
 
[...]
</pre>
+
Create the directory /var/lib/squirrelmail/tmp...
  
Create the directory /var/lib/squirrelmail/tmp...
+
mkdir /var/lib/squirrelmail/tmp
mkdir /var/lib/squirrelmail/tmp
 
  
 
... and make it owned by the user www-data:
 
... and make it owned by the user www-data:
chown www-data /var/lib/squirrelmail/tmp
+
 
 +
chown www-data /var/lib/squirrelmail/tmp
  
 
Reload Apache again:
 
Reload Apache again:
/etc/init.d/apache2 reload
+
 
 +
/etc/init.d/apache2 reload
  
 
That's it already - /etc/apache2/conf.d/squirrelmail.conf defines an alias called /squirrelmail that points to SquirrelMail's installation directory /usr/share/squirrelmail.
 
That's it already - /etc/apache2/conf.d/squirrelmail.conf defines an alias called /squirrelmail that points to SquirrelMail's installation directory /usr/share/squirrelmail.
Строка 794: Строка 762:
  
 
If you'd like to use the alias /webmail instead of /squirrelmail, simply open /etc/apache2/conf.d/squirrelmail.conf...
 
If you'd like to use the alias /webmail instead of /squirrelmail, simply open /etc/apache2/conf.d/squirrelmail.conf...
vi /etc/apache2/conf.d/squirrelmail.conf
+
 
 +
vi /etc/apache2/conf.d/squirrelmail.conf
  
 
... and add the line Alias /webmail /usr/share/squirrelmail:
 
... and add the line Alias /webmail /usr/share/squirrelmail:
  
<pre>
 
 
Alias /squirrelmail /usr/share/squirrelmail
 
Alias /squirrelmail /usr/share/squirrelmail
 
Alias /webmail /usr/share/squirrelmail
 
Alias /webmail /usr/share/squirrelmail
 
[...]
 
[...]
</pre>
+
Then reload Apache:
  
Then reload Apache:
+
/etc/init.d/apache2 reload
/etc/init.d/apache2 reload
 
  
 
Now you can access Squirrelmail as follows:
 
Now you can access Squirrelmail as follows:
Строка 813: Строка 780:
  
 
If you'd like to define a vhost like webmail.example.com where your users can access SquirrelMail, you'd have to add the following vhost configuration to /etc/apache2/conf.d/squirrelmail.conf:
 
If you'd like to define a vhost like webmail.example.com where your users can access SquirrelMail, you'd have to add the following vhost configuration to /etc/apache2/conf.d/squirrelmail.conf:
vi /etc/apache2/conf.d/squirrelmail.conf
 
  
<pre>
+
vi /etc/apache2/conf.d/squirrelmail.conf
 +
 
 
[...]
 
[...]
 
<VirtualHost 1.2.3.4:80>
 
<VirtualHost 1.2.3.4:80>
Строка 821: Строка 788:
 
   ServerName webmail.example.com
 
   ServerName webmail.example.com
 
</VirtualHost>
 
</VirtualHost>
</pre>
 
 
 
Make sure you replace 1.2.3.4 with the correct IP address of your server. Of course, there must be a DNS record for webmail.example.com that points to the IP address that you use in the vhost configuration. Also make sure that the vhost webmail.example.com does not exist in ISPConfig (otherwise both vhosts will interfere with each other!).
 
Make sure you replace 1.2.3.4 with the correct IP address of your server. Of course, there must be a DNS record for webmail.example.com that points to the IP address that you use in the vhost configuration. Also make sure that the vhost webmail.example.com does not exist in ISPConfig (otherwise both vhosts will interfere with each other!).
  
 
Now reload Apache...
 
Now reload Apache...
/etc/init.d/apache2 reload
+
 
 +
/etc/init.d/apache2 reload
  
 
... and you can access SquirrelMail under http://webmail.example.com!
 
... and you can access SquirrelMail under http://webmail.example.com!
  
===18. Links===
+
 +
 
 +
21 Links
 
Debian: http://www.debian.org/
 
Debian: http://www.debian.org/
 
 
ISPConfig: http://www.ispconfig.org/
 
ISPConfig: http://www.ispconfig.org/

Пожалуйста, учтите, что любой ваш вклад в проект «ЗАметки» может быть отредактирован или удалён другими участниками. Если вы не хотите, чтобы кто-либо изменял ваши тексты, не помещайте их сюда.
Вы также подтверждаете, что являетесь автором вносимых дополнений, или скопировали их из источника, допускающего свободное распространение и изменение своего содержимого (см. ЗАметки:Авторские права). НЕ РАЗМЕЩАЙТЕ БЕЗ РАЗРЕШЕНИЯ ОХРАНЯЕМЫЕ АВТОРСКИМ ПРАВОМ МАТЕРИАЛЫ!