Category: Plesk

Adding a Location to PHP’s Open_BaseDir Restriction (Plesk 11)

February 19, 2015 The Geek Decoder No Comments Plesk

For reference, the web root of all websites on your server are in this format:


/var/www/vhosts/example.org/httpdocs

Now that we know the basics of where things are, we can make the changes.

Go into the PHP Settings page for the domain that needs access to the second domain (example.com in this case, use the guide at the top of this article if you’re not sure how to find this area in Plesk).

Then change the open_basedir option to Enter custom value and append your domain’s full path to the entries in the box. You should end up with something that looks like this :


{WEBSPACEROOT}/:{TMP}/:/var/www/vhosts/example.org/httpdocs/

What this means is that the domain you are currently modifying (example.com) can now access its own files (webspaceroot), the server’s temp folder (tmp) and the other domain you have added (/var/www/vhosts/example.org/httpdocs).

You can add as many locations as you need, separated by colons. Once you’ve done that, you should get something that looks like this:

Change Plesk Health Monitor Notifications

February 18, 2015 The Geek Decoder No Comments Plesk

How to add notifications email to Plesk Health Monitor

Edit the config file:

nano /usr/local/psa/var/custom-health-config.xml


Add the email notification

I added them just before the first line "<Hdd>":







Restart the services:
[bash]

# /etc/init.d/psa-health-monitor-notificationd restart

Roundcube error – Misconfiguration: Unregister markasjunk2 in ./config/main.inc.php

February 17, 2015 The Geek Decoder No Comments Plesk

This roundcube error happens after an update on a plesk panel


Error accessing roundcube after upgrade
ERROR- Plugin Manager Center -
Branch: http://dev.myroundcube.com
(Roundcube v1.0.5)

Misconfiguration: Unregister markasjunk2 in ./config/main.inc.php.

You can't register a plugin in main.inc.php which is configured to be loaded by Plugin Manager.

Fix:

Reinstall roundcube in the plesk panel under Update and upgrades

Plesk Postfix error – Delivery to the following recipient failed permanently

February 3, 2015 The Geek Decoder No Comments Plesk

An email sender to your server is getting a bounce message:


Delivery to the following recipient failed permanently".

Email logs show:


Feb  3 11:57:52 mail postfix/cleanup[21623]: D4153A20130: milter-reject: END-OF-MESSAGE from mail-ob0-f181.google.com[209.85.214.181]: 5.7.1 Command rejected; from=<user@domain.org> to=<user@domain2.org> proto=ESMTP helo=<mail-ob0-f181.google.com>

Resolution:

Check the logs as the email is being rejected for a non SPF record:


Feb 3 11:57:50 mail spf filter[22107]: Starting spf filter...
Feb 3 11:57:52 mail spf filter[22107]: SPF result: fail
Feb 3 11:57:52 mail spf filter[22107]: SPF status: REJECT
Feb 3 11:57:52 mail /usr/lib64/plesk-9.0/psa-pc-remote[1877]: handlers_stderr: REJECT
Feb 3 11:57:52 mail /usr/lib64/plesk-9.0/psa-pc-remote[1877]: REJECT during call 'spf' handler
Feb 3 11:57:52 mail /usr/lib64/plesk-9.0/psa-pc-remote[1877]: Message aborted.
Feb 3 11:57:52 mail postfix/cleanup[21623]: D4153A20130: milter-reject: END-OF-MESSAGE from mail-ob0-f181.google.com[209.xx.xx.xx]: 5.7.1 Command rejected; from= to= proto=ESMTP helo=

Postfix: mails sent through sendmail binary are blocked because of wrong HELO

February 3, 2015 The Geek Decoder No Comments Plesk, Postfix

My server is using Centos 6.5
I updated from Plesk 11.5 to 12 last week and postfix to 2.8.17.
Since then, all mails sent using the sendmail binary (notifications, mail forwards…) are being rejected with a wrong HELO hostname: localhost.
It seems that sendmail is using locahost as a HELO tag which is not accepted.

 

Qick Fix:

remove whole non_smtpd_milters from postfix main.cf in case you do not use commtouch.
If you would like to use commtouch then you can remove only “inet:127.0.0.1:12768” from non_smtpd_milters.
restart postfix.

 

Link: http://forum.sp.parallels.com/threads/postfix-mails-sent-through-sendmail-binary-are-blocked-because-of-wrong-helo.305216/

 

Disabling Recursive DNS in the Plesk Panel and No Panels

January 30, 2015 The Geek Decoder No Comments Administration, CentOS 6, CentOS 7, DNS, Plesk, Windows Server

To Disable Recursive DNS in the Parallels Plesk Panel

  1. Log in to the Parallels Plesk Panel as administrator.
  2. Click Tools & Settings.
  3. From the General Settings area, click DNS Template Settings.
  4. Click DNS Recursion.Select Localnets, and then click Ok.

For Windows Servers:

  1. Log in to your  Server  through a Remote Desktop Connection.
  2. From the Start menu, click Control Panel, Administrative Tools, then DNS.
  3. In the console tree, right-click the appropriate DNS server, and then click Properties.
  4. Click the Advanced tab.
  5. Under Server options, check Disable recursion, and then click OK.
  6. In the console tree, right-click the appropriate DNS server, and then click Clear Cache.

CentOS


# cd /etc
# nano named.conf

Change this line

# recursion yes;

to

# recursion no;

Restart

# service named restart

Ubuntu


# nano /etc/bind/named.conf.options

Set up like this

// global options apply to external clients
options {
    recursion no;
    additional-from-auth no;
    additional-from-cache no;
};

view "local" in {
    // view options enable recursion only for local clients
    match-clients { 172.16.45.80/23; 192.168.12.0/24; 127.0.0.1/8; ::1; };
    recursion yes;
    additional-from-auth yes;
    additional-from-cache yes;

    zone "." in {
            type hint;
            file "/etc/bind/db.root";
    };

    // put definitions for zones like "localhost" and "127.in-addr.arpa" here
}

// put definitions for real authoritative zones here.

Install Plesk CentOS 7

January 28, 2015 The Geek Decoder No Comments CentOS 7, Plesk

The Plesk one-click installer is a script that downloads itself and determines the correct Plesk version for your OS. You won’t accidentally pick the wrong version for your distribution.

# wget -O - http://autoinstall.plesk.com/one-click-installer | sh

If you get an error message, wget may not be installed. Rectify this pitiful situation like this:

# yum install wget

Opening Ports for Plesk

On CentOS 6 and prior the firewall rules were set via iptables. This service is gone and has been replaced with firewalld in CentOS 7. We still need to open ports to speak to Plesk via a browser. The two important ones to open here are 8443 and 8447:

# firewall-cmd --zone=public --add-port=8443/tcp --permanent
# firewall-cmd --zone=public --add-port=8447/tcp --permanent
# firewall-cmd --reload

Add Atomic Repo Power (optional)

Now’s a good time to install the Atomic repos. These will give you access to many additional tools such as pre-compiled OSSEC HIDS and additional PHP versions:

# wget -q -O - http://www.atomicorp.com/installers/atomic.sh | sh

Other Options

Obtain the installer script. Download the installer script:


# wget https://installer.plesk.com/plesk-installer

Enable execution mode for the downloaded installer script:


# chmod +x ./plesk-installer

Make sure port 8447 is open
Port 8447 is used for accessing the installer GUI. Make sure, this port is open.

Launch the installer with GUI
Run the script with option –web-interface to launch the interactive installer with web interface for the latest stable Plesk version:


# ./plesk-installer --web-interface

From Plesk Trial Signup:
Welcome aboard!

Linux console command:

You also can download your Plesk license for Linux directly from your console interface by running the following command:

# sh <(curl http://autoinstall.plesk.com/plesk-installer) [/bash] After install: Congratulations! The installation has been finished. Plesk is now running on your server. To complete the configuration process, browse either of URLs: * https://216.55.169.209:8443/login?secret=5bwVKsGqv7nDQS9AjQrVhWRY72yjsAthTEr5Ll4r%2Ff0%3D * https://plesk.geekdecoder.com:8443/login?secret=5bwVKsGqv7nDQS9AjQrVhWRY72yjsAthTEr5Ll4r%2Ff0%3D Use the username 'admin' to log in. To log in as 'admin', use the 'plesk login' command. You can also log in as 'root' using your 'root' password. Use the 'plesk' command to manage the server. Run 'plesk help' for more info. Use the following commands to start and stop the Plesk web interface: 'service psa start' and 'service psa stop' respectively. If you would like to migrate your subscriptions from other hosting panel or older Plesk version to this server, please check out our assistance options: https://www.plesk.com/professional-services/

nginx: [emerg] bind() to 68.xx.xx.xx:443 failed (99: Cannot assign requested address)

January 24, 2015 The Geek Decoder No Comments Nginx, Plesk

Apache is listening on port 7080. This usually means the server is running nginx on port 80 and forwarding script calls to apache. Restarting nginx and received the following error:

Starting nginx: nginx: [emerg] bind() to 68.xx.xx.xx:443 failed (99: Cannot assign requested address)

Run the following command to disable nginx and rebuild the apache configuration to use port 80:


# /usr/local/psa/admin/bin/nginxmng -d

You can enable nginx again if needed by running:


# /usr/local/psa/admin/bin/nginxmng -e