Source: https://www.ssl.com/how-to/create-a-pfx-p12-certificate-file-using-openssl/

The PKCS#12 or PFX format is a binary format for storing the server certificate, any intermediate certificates, and the private key into a single encryptable file. PFX files are usually found with the extensions .pfx and .p12. PFX files are typically used on Windows and macOS machines to import and export certificates and private keys.

tools:create_a_.pfx_or_.p12_certificate_file_using_openssl · 2020/02/19 20:13 · 2020/02/19 20:13

nginx is my preferred lightweight HTTP/HTTPS server and fairly easy to do reverse proxy for. In this example, I use a reverse proxy to expose an internal service running on port 82 to the Internet.

Here is an example config …

server {
        server_name example.vernon.wenberg.net; # must match the sub.host portion of the URL
        proxy_set_header Host   $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        client_max_body_size 100M; # increase size of uploaded files
        location / {
                proxy_pass http://internal-service.vernon.wenberg.net:82; # internal server address and port
        }
# Insert SSL certificate block here
}

example.vernon.wenberg.net is a sub-domain that exists on the public Internet while internal-service.vernon.wenberg is an internal system. This also allows the use of an SSL certificate on your nginx server instead of your internal server.

linux:quick_reverse_proxy_config_for_nginx · 2020/02/16 23:59 · 2020/02/17 00:11

How to resolve incorrect time with Windows Domain Controller

The Domain Controller should be the definitive source for time for the entire Windows Domain network. It needs to sync directly to NTP servers and not the hardware clock of the machine it's on whether it's a virtual machine or a physical server.

That means don't set VMware Tools to sync time for the guest. There are several frustating limitations to the VMware tools time sync that make it the wrong tool for the job. VMWare defaults to having time sync disabled on Windows Server guests for a good reason.

That does mean that you'll need to set your Domain Controller to get it's time synchronization directly from the Internet (or a definitive clock source).

Run the following from an escalated command line.

C:\net stop w32time
C:\> w32tm /config /syncfromflags:manual /manualpeerlist:”0.pool.ntp.org, 1.pool.ntp.org, 2.pool.ntp.org”

If the above command does not work, try this …

w32tm /config /update /manualpeerlist:"0.pool.ntp.org,0x8 1.pool.ntp.org,0x8 2.pool.ntp.org,0x8 3.pool.ntp.org,0x8" /syncfromflags:MANUAL
<code>C:\>w32tm /config /reliable:yes
C:\>net start w32time
C:\>w32tm /query /configuration

Those commands will set the appropriate registry keys so that your server will get the time directly from the Internet and not the hardware clock or VMware tools. Once you've gotten the DC time correct (including your timezone), then the other machines will update automatically over time. You can force an update using …

C:\>w32tm /resync

The command prompts the local computer to sync to it's configured time source. If it's a Domain Member, then it will sync to the previously configured and updated Domain Controller(s).

windows:how_to_resolve_incorrect_time_with_windows_domain_controller · 2020/02/16 10:41 · 2020/02/16 10:44