Thought I would post this one quickly…

Having trouble getting OpenVPN to start/work for you and you are seeing this error in your logs?

“TCP/UDP: Socket bind failed on local address”

The resolution is pretty simple. Try changing the port you have assigned to openVPN in your config file and restarting the service. Most likely you have bound it to a port already being used by another service. I ran into this problem because I tried to use port 443. I wasn’t running an SSL/HTTPS website on my server but what I had forgotten that I was running SSH through 443 temporarily.

It is generally good practice to use a port above 1000 for odd services if you aren’t using the default port for said service. I run into this a lot as I don’t like to use common ports as they tend to get targeted more often and hammered by bots/evil people trying to break in…

Anyhow, hope this helps!

I am attempting to integrate SSO (Single Sign On) with Facebook for one of my Drupal sites. ( After a bit of research and digging through modules I decided to give the “Drupal for Facebook” module a go. Talk about a PAIN IN THE AR$E…

I should have suspected when the description of the module was a page long and there are two different version of the module that require further description for each. A feature list showing what differed between the two module would have been nice… Nope…

I thought I would put this together quickly because in typical Linux fashion something that should be straightforward isn’t… Node.js – I am still not sure what it is :), however I am in the process of setting up drupalchat on one of my sites and when I tried using it with the AJAX option, which worked well for a couple of users, it made the site run extremely slowly. The server has plenty of grunt… dedicated Ubuntu 13 VM running 3 cores and 2 GB of RAM and this particular site was the only thing running on it. Furthermore, the MySQL database server was/is on a separate dedicated VM… so there is no way it was a lack of firepower. DrupalChat running with AJAX was causing problems. I am going to launch a fuller tutorial on getting drupal chat setup but I figured I would do the node.js thing here and now….

So you have just built your brand new Server 2012 box and need to download and install some software to get it up and running for the intended user. You open up IE because that is the only browser installed on a new box and hop on over to the download site, click the link to download and STOP…

“Security Alert: Your current security settings do not allow this file to be downloaded.”

Oh yes, you know the fix for this, go to server manager, fumble around and hit “local server” and then find the “IE Enhanced Security Configuration” and turn it off. Restart Internet Explorer…

It still won’t let you download and gives you the same message…

So what gives? You are a local admin on the box (at least, maybe even a Domain admin…), turned off Enhanced Security, and yet, Microsoft still says no. Do the following as turning off Enhanced Security Mode is part 1 but you need part 2.

  1. Open up Internet Explorer (IE)
  2. Click the “Gear” in the upper-right-hand corner
  3. Click Properties
  4. Click the Security Tab
  5. Click “custom level” button while “internet” up top is highlighted..
  6. Scroll Down and find the Downloads Section –> File Download
  7. Tick “enable” then “ok” and “Apply” and get out and back to work

Thank you Microsoft for babysitting us all until we absolutely lose our minds…

Ran into an issue to day installing Server 2012 R2 from an ISO file onto a fresh/brand new VM.

"0xE0000100: "Windows installation encountered an unexpected error. Verify that the installation sources are accessible, and restart the installation."

A little Google-Fu fixed me right up. New VM’s only have 512 MB of “startup memory” and you need to set it to at least 1024 MB to allow the installation to proceed without error.

I had Dynamic Memory setup with a range of 512 MB to 8192 MB and thought I would be okay. Not so. Anyhow, I just statically gave it 4 Gb for the install and changed it around once the install was finished. That being said, I am keeping the startup memory at 1024 MB now for all Server 2008R2+ VM’s.