How to test drive 200 Linux distros

If you’re like me, you’ve tried a number of different Linux flavors.

If you haven’t found “the one”, you can now visit distrotest.net to test any one of 200 different distributions. Click the link below on Forbes for all the details.

www.forbes.com/sites/jasonevangelho/2019/06/15/how-to-test-drive-200-linux-distributions-without-ever-downloading-or-installing-them/

Advertisements

Free Nginx E-Book

Here’s a cool freebie for you web server admins out there. Right now, you can download a free copy of the O’Reilly® Nginx Cookbook from here:

https://www.nginx.com/resources/library/complete-nginx-cookbook/

It’s a great resource for beginners and advanced users alike. Nothing is free you say?? Okay, you do have to supply your name, email address, etc. so that they can spam your inbox. Set your junk mail filters accordingly.

 

 

 

How-to install Nginx on Amazon Linux 2

*This is a quick how-to for installing Nginx. If you need more insight into launching Amazon instances, please visit the Amazon documentation page: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/concepts.html.

 

First, login into your  Amazon Linux 2  instance. Amazon maintains its’ own repository (amazon-linx-extras) of software packages for quick convenient installation on it’s instances.

To view what is available in the repo enter amazon-linux-extras list in the terminal window.

As you can see, there are a number of commonly used software packages available and nginx1.12 is fourth on the list.

 

ec2-nginx1

Next, we’ll run: sudo amazon-linux-extras install nginx1.12 (you must use the version number otherwise the install will fail). Once installed, you will see a screen similar to the one below. Nginx is now enabled in the repo and installed on my instance.

 

ec2-nginx-2

Now, we’ll verify the installation. At the prompt run: nginx –v and you’ll see that the server is now running version 1.12.2:

 

ec2-nginx-3

We can also browse to the default web page by using public DNS name:

 

ec2-nginx-4

 

IIS 7 : HTTP 500 Internal Server Error/Machine.Config Files

I recently ran into an issue while assisting my company’s web developers with a site that would not load. The general error was HTTP 500 Internal Server Error.

The site in question, had recently been copied from a staging server to a production server. While it worked in staging, it did not load in production. I logged into the production server to get more detailed information by loading the page in IE. IE threw the following message:

2015-11-12 15_46_03-10.164.1.62 - Remote Desktop Connection

This particular site runs on Server 2008 and the application was built for ASP.net 1.1. After doing some research and thanks to http://www.iis.net I found the answer. It was determined that the machine.config files did match up in staging and production.

Per IIS.net —

ASP.NET v1.1 will throw runtime exceptions out of the box if you have IIS configuration in the web.config files that are read by your ASP.NET v1.1 applications. To make ASP.NET v1.1 ignore IIS configuration sections, open the Framework v1.1 machine.config file (%windir%\Microsoft.NET\Framework\v1.1.4322\config\machine.config) and add the following section entry just above the bottom tag for the element:

<section name=”system.webServer” type=”System.Configuration.IgnoreSectionHandler,
System, Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b77a5c561934e089″ />

I added the aforementioned line to my machine.config file (C:\Windows\Microsoft.Net\Framework\v1.1.4322\Config) in production, the site now loads. Lesson learned. Always verify the machine.config files in both locations.

Lync/Skype for Business Certificate Error

File this under tips and tricks:

You are an Office 365 subscriber and trying to launch the Lync or Skype for Business client application. When attempting to login you receive the following error…

This happens due to server authentication failure. But you can set the server settings manually. Go to Tools -> Options -> Personal -> Select Manual Configuration -> Enter: sipdir.online.lync.com:443 -> Click OK -> Click OK on the Options window.

Go back to the login screen and enter your credentials. Usually this is your email address.

Now you should be able to successfully login.

If you still encounter issues, try using the Microsoft Remote Connectivity Analyzer.

https://testconnectivity.microsoft.com/?tabid=o365