Category: Plesk

Plesk autoinstaller GPG error on Ubuntu 14.04 Trusty

August 11, 2015 The Geek Decoder No Comments Plesk, Ubuntu

Getting error for Plesk auto installer on Ubuntu 12 Trusty:



Reading package lists...
W: GPG error: http://autoinstall.plesk.com trusty InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 227C38D6AF741DEB
W: GPG error: http://autoinstall.plesk.com trusty InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 227C38D6AF741DEB
W: GPG error: http://autoinstall.plesk.com trusty InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 227C38D6AF741DEB
W: GPG error: http://autoinstall.plesk.com trusty InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 227C38D6AF741DEB
W: GPG error: http://autoinstall.plesk.com trusty InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 227C38D6AF741DEB
Gathering information about installed license key...
Checking whether the package dependencies are resolved.
E: Unable to correct problems, you have held broken packages.
---X--- `apt-get` output ---------------------
Reading package lists...
Building dependency tree...
Reading state information...
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
plesk-base : Depends: sw-engine (>= 2.13.9) but it is not going to be installed
plesk-core : Depends: libmyodbc but it is not installable
Depends: pigz but it is not installable
plesk-php56-dba : Depends: libdb5.1 but it is not installable
plesk-php56-imap : Depends: libc-client2007e but it is not installable
plesk-php56-mcrypt : Depends: libmcrypt4 but it is not installable
plesk-service-node-utilities : Depends: libxml-dumper-perl but it is not installable
Depends: sysv-rc-conf but it is not installable
pp12.0.18-bootstrapper : Depends: sw-engine (>= 2.0) but it is not going to be installed
psa-courier-imap : Depends: libdb5.1 but it is not installable
Depends: libssl0.9.8 but it is not installable
psa-php5-configurator : Depends: php5-imap but it is not installable
psa-updates : Depends: sw-engine (>= 2.13.12) but it is not going to be installed

Check following:

1. /etc/apt/sources.list

2. uncomment the deb repos listed as universal/multiverse

3. re-run apt-get update

4. re-run plesk installer

I have also noticed that it tends to give an error about the hostname as well, which I resolved by temporarily setting the hostname to pretty much anything, such as newserver.

Other Information: http://forum.odin.com/threads/plesk-autoinstaller-gpg-error.332686/

HOW-TO How-to enable gzip support on nginx

August 3, 2015 The Geek Decoder No Comments Gzip, Plesk

APPLIES TO:

Plesk 12.0 for Linux
Plesk 11.0 for Linux
Plesk 11.5 for Linux

How to enable gzip support on nginx?

Create /etc/nginx/conf.d/gzip.conf with the following:


gzip         on;
gzip_disable "MSIE [1-6]\.(?!.*SV1)";
gzip_proxied any;
gzip_types   text/plain text/css application/x-javascript text/xml application/xml application/xml+rss text/javascript image/x-icon image/bmp image/svg+xml;
gzip_vary    on;

gzip_types to compress other file types can be obtained from /etc/nginx/mime.types

Imagemagick on CentOS and Plesk

August 2, 2015 The Geek Decoder No Comments CentOS 6, CentOS 7, PHP, Plesk 
root@server ~]# yum install ImageMagick
[root@server ~]# yum install ImageMagick-devel

PHP-imagick Installation:
[root@server ~]# yum install gcc
[root@server ~]# yum install make automake
[root@server ~]# yum install php-pear
[root@server ~]# yum install php-devel
[root@server ~]# pecl install imagick

On some servers

yum install php-pecl-imagick.x86_64

Test:

convert image.jpg -resize 64x64 resize_image.jpg

PLESK: How to create multiple Mysql DB’s with a Single User

August 1, 2015 The Geek Decoder No Comments MySQL, Plesk

Login with ssh

Login to mysql

# mysql -uadmin -p`cat /etc/psa/.psa.shadow`

use the mysql db.

mysql> use mysql;

mysql> SELECT* FROM db;

To add same user to another database, you have to insert that user into db table and give him same privileges he already has for his existing database.

mysql> INSERT INTO db VALUES(‘localhost’,’second_db’,’same_username_you_used_for_first_db’,’Y’,’Y’,’Y’,’Y’,’Y’,’Y’,’N’,’Y’,’Y’,’Y’,’Y’,’Y’,’Y’,’Y’,’Y’,’Y’,’Y’);

The second database is accessible to the same user as the first database, from command line but it will not appear yet in your Plesk admin panel. In order to have access to second database from Plesk interface you will have to link your database user to this second database in plesk table:


mysql> use psa;

First you must find out the database id Plesk internally assigned to your second database which we do with the following:


mysql> SELECT * FROM data_bases;

    +—-+—————————+——-+————-+————————+———————-+
    | id | name                             | type  | dom_id              | db_server_id    | default_user_id    |
    +—-+—————————+——-+————-+——————-+—————————+
    |  1 | first_db                         | mysql |      1              |            1 |               1       |
    |  2 | second_db                        | mysql |      1              |            1 |               0       |
    |  3 | test                             | mysql |      1              |            1 |               0       |
    |  4 | wordpress                        | mysql |      1              |            1 |               3       |
    +—-+—————————+——-+————-+——————+—————————–+

Note: We are going to get second_db to use first_db’s user so we are going to need the id “2”. Now we have to find out what id plesk has signed internally to the Database user:


mysql> SELECT * FROM db_users;

    +—-+—————–+—————-+———+
    | id | login          | account_id    | db_id     |
    +—-+—————–+—————-+———+
    |  1 | first_db_user  |       3       |    1      |
    |  2 | worpress_user  |       4       |    4      |
    +—-+—————–+—————-+———+

Note: We are going to use first_db’s account ID above which is “3”. Now you have to link the user to the second database using the command below


mysql> INSERT INTO db_users VALUES(”,’first_db_user’,’3′,’2′);

Note: For people who do not like to copy an paste those are single quotes at the start.
You should run the select db_users command again to check for your changes then exit mysql and restart MySQL:


# service mysqld restart

SMTP Error -1 Connection to server failed on Roundcube

July 27, 2015 The Geek Decoder No Comments Plesk, Roundcube

Issue: Please server with postfix and roundcube

Pots changed for SMTP mail.

Edit the roundcube config:

 /usr/share/psa-roundcube/config

Check that the config is correct:

SMTP server host

// SMTP server host (for sending mails).
// To use SSL/TLS connection, enter hostname with prefix ssl:// or tls://
// If left blank, the PHP mail() function is used
// Supported replacement variables:
// %h - user's IMAP hostname
// %n - hostname ($_SERVER['SERVER_NAME'])
// %t - hostname without the first part
// %d - domain (http hostname $_SERVER['HTTP_HOST'] without the first part)
// %z - IMAP domain (IMAP hostname without the first part)
// For example %n = mail.domain.tld, %t = domain.tld
$rcmail_config['smtp_server'] = 'smtp.domain.com';

Port

// SMTP port (default is 25; use 587 for STARTTLS or 465 for the
// deprecated SSL over SMTP (aka SMTPS))
$rcmail_config['smtp_port'] = 9025;

FTP error on plesk server

July 22, 2015 The Geek Decoder No Comments FTP, Plesk

Getting an ftp connection error on a plesk server:

15:04:41 Status: Resolving address of 66.226.xx.xx
15:04:41 Status: Connecting to 66.226.72.xx.xx
15:04:41 Status: Connection established, waiting for welcome message...
15:04:48 Status: Initializing TLS...
15:04:50 Status: Verifying certificate...
15:04:53 Status: TLS connection established.
15:04:59 Status: Connected
15:04:59 Status: Retrieving directory listing...
15:05:02 Command: PWD
15:05:02 Response: 257 "/" is the current directory
15:05:02 Command: TYPE I
15:05:02 Response: 200 Type set to I
15:05:02 Command: PASV
15:05:02 Response: 227 Entering Passive Mode (66,226,xx,xx1,46,242).
15:05:02 Command: MLSD
15:05:02 Error: The data connection could not be established: ECONNREFUSED - Connection refused by server
15:05:21 Error: Connection timed out after 20 seconds of inactivity
15:05:21 Error: Failed to retrieve directory listing
15:05:21 Status: Disconnected from server

Edit your configuration file and comment out MasqueradeAddress:

# nano /etc/proftpd.conf

#MasqueradeAddress 66.226.xx.xx

Restart xinetd

# service xinetd restart

Block IP with Plesk Firewall

July 20, 2015 The Geek Decoder No Comments Plesk

Plesk 9.x

1. Login to Plesk control panel.
2. Click on Modules >> Firewall >> Edit Firewall Configuration.
3. Click on ‘Add Custom Rule’.
4. Enter a name for the rule.
5. Select the option ‘Incoming’ for ‘Match direction’.
6. Select ‘Deny’ for Action.
7. If you wish to add port, you can enter the port or port range in text box beside the option ‘Add port or port range’. Click Add. Select TCP or UDP protocol. If you do not wish to add port, leave it as it is.
8. Add the IP address to be blocked in the text box beside the option ‘Add IP address or network’. Click Add.
9. Click OK.
10. Click Activate.

Plesk 10.x

1. Login to Plesk control panel.
2. Click on Tools & Settings >> Firewall >> Edit Firewall Configuration.
3. Click on ‘Add Custom Rule’.
4. Enter a name for the rule.
5. Select the option ‘Incoming’ for ‘Match direction’.
6. Select ‘Deny’ for Action.
7. If you wish to add port, you can enter the port or port range in text box beside the option ‘Add port or port range’. Click Add. Select TCP or UDP protocol. If you do not wish to add port, leave it as it is.
8. Add the IP address to be blocked in the text box beside the option ‘Add IP address or network’. Click Add.
9. Click OK.
10. Click Activate.

Plesk 12.x

1. Login to Plesk control panel.
2. Click on Tools & Settings >> Firewall
3. Click on Modify Plesk Firewall Rules >> Add Custom Rule
4. Enter a name for the rule.
5. Select the option ‘Incoming’ for ‘Match direction’.
6. Select ‘Deny’ for Action.
7. If you wish to add port, you can enter the port or port range in text box beside the option ‘Add port or port range’. Click Add. Select TCP or UDP protocol. If you do not wish to add port, leave it as it is.
8. Add the IP address to be blocked in the text box beside the option ‘Add IP address or network’. Click Add.
9. Click OK.
10. Apply Changes.