8/4/21

Quick HTTP to HTTPS - Apache2

There are several methods for redirecting your Apache-based website visitors who might type your servers URL using the plain (non-secure) HTTP protocol to be sent to the encrypted HTTPS version of your website which effectively, forces any visitor to your website to HTTPS.

The method below is my favorite for its simplicity and my own experience with it that it worked 100% of the time.

Before adding the redirection code to your Apache's config file you'd obviously need to have a working Apache and SSL configuration for your website, preferably with a valid SSL certificate. Once that condition is satisfied, the next step is to make sure that you have Apache's rewrite module installed and loaded.

You could quickly find out if your serve has the rewrite module installed and loaded by running the following command: apache2ctl -M 

The above command will return a list of installed & loaded modules, look for the following entryrewrite_module

Or, you could run the command this way: apache2ctl -M|grep rewrite which will give you this output - assuming that you do have the rewrite module installed and loaded-

rewrite_module (shared)

if not, then you need to add this module by following the instructions for your particular O.S flavor

First and last step for sending HTTP to HTTPS:

All you need to do is insert the following 3 lines into the <virtual host> usually located in /etc/apache2/sites-enabled/000-default.conf on Ubuntu based servers and in  /etc/httpd/conf/httpd.conf in Redhat-based servers like CENTOS using your favorite editor:

RewriteEngine On
RewriteCond %{HTTPS} off
RewriteRule ^ https://%{HTTP_HOST}%{REQUEST_URI}

Save your conf file and run /usr/sbin/apache2ctl configtest to make sure that your conf file is free of syntax errors before you reload Apache. Once the configtest returns the result of "Syntax OK" you can run /usr/sbin/apache2ctl restart to apply your changes.

Finally, verify your work results by accessing the website you modified via your browser and make sure to call the website using http://your-server.com and watch your browser redirect you to the https://your-server.com




4/16/21

Windows Update Troubleshooting

Found this post after running into this error (8024401C) following error 0x80244007 which I received after scanning for Windows Updates.

after attempting to check for Windows updates on a Windows 2012R2 system and it helped me solve my issue. Thanks to the original poster.

The following outlines how to stop services pertaining to Windows Update, rename system folders, register related DLL files, and then restart the previously mentioned services. This troubleshooting generally applies to all Windows Update related issues.


 Stopping services pertaining to Windows Update


  1. Click Start, click All Programs, click Accessories, right-click Command Prompt, and select Run as Administrator.
  2. If you receive a notification from User Account Control simply click Continue.
  3. At the command prompt, type the following, commands and then press ENTER after each command.
    1. net stop wuauserv
    2. net stop bits
    3. net stop cryptsvc
      Please do not close the Command Prompt window.
  4. Renaming folders pertaining to Windows Update
  5. At the command prompt, type the following commands, and then press Enter after each command:
  6. ren %systemroot%\System32\Catroot2 Catroot2.old
  7. ren %systemroot%\SoftwareDistribution SoftwareDistribution.old

    Please do not close the Command Prompt window.


Registering DLL’s pertaining to Windows Update


  • Please copy and paste the following text into a new Notepad document, and save the file as WindowsUpdate.BAT
    If saved correctly the icon will change from a Notepad file to BAT file which has two blue cogs as its icon.


            -OR-


  • You can manually type each command at the command prompt:


regsvr32 c:\windows\system32\vbscript.dll /s

regsvr32 c:\windows\system32\mshtml.dll /s

regsvr32 c:\windows\system32\msjava.dll /s

regsvr32 c:\windows\system32\jscript.dll /s

regsvr32 c:\windows\system32\msxml.dll /s

regsvr32 c:\windows\system32\actxprxy.dll /s

regsvr32 c:\windows\system32\shdocvw.dll /s

regsvr32 wuapi.dll /s

regsvr32 wuaueng1.dll /s

regsvr32 wuaueng.dll /s

regsvr32 wucltui.dll /s

regsvr32 wups2.dll /s

regsvr32 wups.dll /s

regsvr32 wuweb.dll /s

regsvr32 Softpub.dll /s

regsvr32 Mssip32.dll /s

regsvr32 Initpki.dll /s

regsvr32 softpub.dll /s

regsvr32 wintrust.dll /s

regsvr32 initpki.dll /s

regsvr32 dssenh.dll /s

regsvr32 rsaenh.dll /s

regsvr32 gpkcsp.dll /s

regsvr32 sccbase.dll /s

regsvr32 slbcsp.dll /s

regsvr32 cryptdlg.dll /s

regsvr32 Urlmon.dll /s

regsvr32 Shdocvw.dll /s

regsvr32 Msjava.dll /s

regsvr32 Actxprxy.dll /s

regsvr32 Oleaut32.dll /s

regsvr32 Mshtml.dll /s

regsvr32 msxml.dll /s

regsvr32 msxml2.dll /s

regsvr32 msxml3.dll /s

regsvr32 Browseui.dll /s

regsvr32 shell32.dll /s

regsvr32 wuapi.dll /s

regsvr32 wuaueng.dll /s

regsvr32 wuaueng1.dll /s

regsvr32 wucltui.dll /s

regsvr32 wups.dll /s

regsvr32 wuweb.dll /s

regsvr32 jscript.dll /s

regsvr32 atl.dll /s

regsvr32 Mssip32.dll /s

  • Restarting services pertaining to Windows Update
  1. Click Start, click All Programs, click Accessories, right-click Command Prompt, and select Run as Administrator.
  2. If you receive a notification from User Account Control simply click Continue.
  3. At the command prompt, type the following, commands and then press ENTER after each command.
    1. net start wuauserv
    2. net start bits
    3. net start cryptsvc


      Type <exit> to leave the command prompt

You might want to try a clean boot once you're done with the above, then check for updates once your system is back up. Rebooting was what I had to do in my case.

  • Now please check for updates using Windows Update to see if the issue has been resolved.


Original Post:
https://answers.microsoft.com/en-us/windows/forum/all/access-denied-on-open-commands/2d31ce25-46a7-4ba0-838d-5b842e9991fa

Quick HTTP to HTTPS - Apache2

There are several methods for redirecting your Apache-based website visitors who might type your servers URL using the plain (non-secure) HT...