Updates from November, 2014 Toggle Comment Threads | Keyboard Shortcuts

  • Jay Versluis 3:59 pm on November 25, 2014 Permalink | Reply

    Categories: macOS ( 37 )   

    How to launch Mac Apps on your External Display by default 

    Screen Shot 2014-11-25 at 13.53.03

    Even on the best computers there are some things you only do every once in a blue moon – at which point you’ve forgotten what you did last time to make it work. Setting up a second display with your MacBook is such a case. Here’s what worked for me when I installed my Thunderbolt Display last year. We’ve just added another one in our office – here’s to doing it again in the future.

    When you plug that beautiful 27″ puppy into your MacBook Pro or Air it works without any trouble: the dock is at the bottom of both displays, and even the menu bar seems to follow you onto whichever monitor you click. Magic!

    Apps however remember which monitor they were launched on last, and if you’ve never had a second display attached to your system then most of them will default to that little laptop screen instead of your new desktop centre piece. This is not an issue if you simply close the lid on your laptop because your graphics card only sees a single display.

    If you do use both displays though, there is a way to tell your Mac which one to launch an app on by default. And here’s how to do that:

    (More …)

  • Jay Versluis 11:10 am on November 18, 2014 Permalink | Reply  
    Categories: Windows ( 22 )   

    How to restart Windows via RDP 

    Windows IconWhen you’re connected via RDP to a remote Windows machine, the Restart and Shutdown options are not there. Instead they’ve been replaced with only a lonely disconnect option to end your session.

    To restart or shutdown your remote machine we’ll have to use the command line’s shutdown command. Here’s how.


    At the Command Prompt (searching usually brings it right up) type

    shutdown /r /t 0

    This will restart Windows. /r means “restart”, and /t specifies the time in seconds (zero in our case).

    If you’d like to shutdown the machine instead, type

    shutdown /s


  • Jay Versluis 11:50 am on November 2, 2014 Permalink | Reply

    Categories: Linux ( 101 ), Plesk ( 76 )   

    How to install Plesk on CentOS 7 

    Plesk-LogoInstalling Plesk on CentOS 7 hasn’t changed drastically from earlier versions, however CentOS is different than its predecessors. I’ve written an article about how to install Plesk on CentOS 6, but that was 3 years ago and thought it’s time for an updated version.

    Well here it is: Plesk 12, meet CentOS 7.


    Plesk Documentation

    Much of what I’m telling you and more is documented on the Parallels Plesk website:

    On the left hand side you’ll find a link to the current documentation, as well as handy links to purchase a license if you need to. The link will also answer your questions about the different editions of Plesk and direct you to the Parallels Forum.


    One-Click Installer

    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. Paste this and the installer will download the latest version of Plesk (12 at the time of writing):

    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


    To download older versions of Plesk you can download the one-click-installer file and run it with the option –show-all-releases. This will give you the option to specify your desired Plesk version with –select-release-id. For more information, run the file with the –help option.

    I’ve noticed that the installer is much quicker than on previous versions of Plesk and is finished in under 10 mins (as opposed to half an hour previously). This is presumably due to many packages that are pre-installed with CentOS 7, so not much time is spent downloading stuff. Nice!

    Once finished the installer will give you a URL to login with – usually consisting of your IP, like


    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

    The –permanent option makes these rules “stick” upon restart.

    These are not the only ports Plesk needs to function, for a full list please see this KB article:

    There is usually no need to open other ports if you install the Firewall extension in Plesk, as this will manage the underlying service for you (and apply the necessary open ports). To do this, head over to Tools and Settings – Updates and Upgrades and install the Firewall Extension (under Additional Plesk extensions).

    Next head over to Extensions select the Firewall Module. Select “Enable Firewall Rules Management”, followed by another enable button. Now Plesk will manage the firewall for you and open all ports ready for web and email traffic.


    Add Atomic Repo Power (optional)

    If you’d like to supercharge your server, 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


    Loggin in for the first time

    With your dedicated IP handy, the installer script will have given you something like Surf there and be presented with the Plesk login screen.

    But what are your credentials? I’m glad you asked: the first time you login to Plesk you can do so with your server root credentials. This even works on subsequent sessions, however Plesk creates an admin user for which you will specify the password during your first session.

    It is strongly recommended that you use that admin user for Plesk administrative tasks. You can also create additional administrators in Plesk once you’re up and running – so there’s no need to share your super secret password with colleagues and clients.


    Correcting your IP address (optional)

    It can happen that Plesk does not detect the correct IP address on your server. This was never the case in CentOS 6, but I’ve noticed this in CentOS 7. In my case the Plesk installer thought that the local loopback address was my main one ( – which of course it was not.

    You can usually correct this on first login, but just in case you need to do this from the command line, check this helpful KB article:


    License Key and Additional Components

    You need a license to operate Plesk. You’ll get this either from your server provider (if Plesk is part of your deal), or you can buy one directly from Parallels. You can also run Plesk as a 14 day trial version. If you don’t enter this you can still use the Plesk interface but you’ll be limited to a single domain and several options are unavailable.

    In case you’re missing menu items that you had expected to be there, it’s probably a license issue.

    I find it helpful to head over to Tools and Settings (or the Server Tab) – Plesk – Updates and Upgrades and install several additional components, such as

    • Health Monitor
    • Migration Manager
    • Firewall (under Additional Plesk Extensions)
    • Watchdog (under Additional Plesk Extensions)
    • Spam Assassin (under Mail hosting features)
    • Kapersky Anti Virus (under Mail hosting features)

    You can also install Fail2ban from this menu if you like – I personally rely on OSSEC to deal with intrusion detection and choose not to use Fail2ban at this point.


    That’s it! Have fun with Plesk 😉

    • Jason William 3:11 pm on November 3, 2014 Permalink | Reply

      Thanks for sharing the tutorial.

      • Jay Versluis 5:50 pm on November 3, 2014 Permalink | Reply

        You’re welcome, Jason!

    • Denis 10:18 am on April 4, 2015 Permalink | Reply

      “Once finished the installer will give you a URL to login with – usually consisting of your IP, like

      here the error, corrected to

      • Jay Versluis 11:11 am on April 4, 2015 Permalink | Reply

        Thanks for bringing this typo to my attention Denis, I’ve corrected the article.

    • Jay Versluis 7:51 am on April 21, 2015 Permalink | Reply

      Quick note for WordPress installations

      Note that Plesk 12.0.8 on CentOS 7 currently has an issue that makes the wp-content folder for WordPress websites unaccessible via FTP. It appears that SELinux is preventing that folder from being listed. WordPress itself works fine, and the folder can be accessed from both Plesk and WordPress, just not via FTP.

      If this is important to you, set SELinux to “permissive” as described in this article: https://wpguru.co.uk/2014/12/how-to-control-selinux-in-centos-7/

      The issue is full fixed in Plesk 12.1.x

    • Oliver Burkill 7:31 am on July 6, 2015 Permalink | Reply

      On a fresh Centos 7 install you also need to turn off SELinux before you install Plesk.

      • Jay Versluis 9:14 am on July 6, 2015 Permalink | Reply

        I guess it’s philosophical, it certainly doesn’t hurt to turn off SELinux during the installation, but I don’t think it’s a requirement. I’ve installed Plesk on CentOS 7 several times successfully with SELinux turned on. Is this an official Parallels/Odin recommendation? Just curious.

        Thanks for the tip though, next time I’ll turn it off and see if there’s a difference.

        • James Fernandez 12:23 am on February 26, 2017 Permalink | Reply

          can you help me I am stuck

    • Kingsley 4:26 pm on September 4, 2015 Permalink | Reply


      thanks for this tutorial, i am looking for a way to set a particular NS for all listed domains

    • Ben 3:18 pm on September 7, 2015 Permalink | Reply

      When I ran: firewall-cmd… It stated: -bash: firewall-cmd: command not found

      The install went fine and it didn’t show any errors. Is there a workaround?

      • Ben 4:19 pm on September 7, 2015 Permalink | Reply

        I figured it out. I needed to install and activate firewalld. I did and now they are added. 🙂

        • Jay Versluis 6:38 pm on September 7, 2015 Permalink | Reply

          Great, glad to hear you got it working!

    • Kingsley 5:44 am on September 16, 2015 Permalink | Reply


      I did everything but the hostname or the ip wont work. nothing is accessible

      • Jay Versluis 3:44 pm on September 18, 2015 Permalink | Reply

        Sounds like the firewall or additional security in front of the server is keeping you from logging in. It depends on your infrastructure: on Amazon AWS for example, you need to open ports in the Security Group before connections are allowed. Make sure nothing is blocking port 22 so you can reach your server via SSH.

    • deedee 12:22 pm on December 13, 2015 Permalink | Reply

      please remove the “enable the atomic repo” advise, it completely conflicts with the default plesk packages and screwed over my installation.

      • Jay Versluis 2:25 pm on December 13, 2015 Permalink | Reply

        Nope, I won’t! It’s clearly marked as an optional step, besides it is the Plesk 12 recommended way if you’d like to use the php-fpm module that’s part of the Plesk installer (Plesk 12.5 supports php-fpm without Atomic).

Compose new post
Next post/Next comment
Previous post/Previous comment
Show/Hide comments
Go to top
Go to login
Show/Hide help
shift + esc