MiniWeb was chosen so we don’t need to change any IIS configuration (if you have TCP port 80 bound on your IIS server you can even use a workstation for this procedure) and we can start and stop it whenever we need to.<\/p>\n\n\n\n
Download and start MiniWeb making sure to specify port 80 or it will by default start listening on port 8000. miniweb.exe -p 80<\/p>\n\n\n\n
Make sure your Firewall is forwarding Tcp Port 80 to the PC running MiniWeb<\/p>\n\n\n\n
Download and run the WACS tool. It will show a simple list of available commands <\/p>\n\n\n\n M: Manual (Full Options)<\/p>\n\n\n\n 2: Manual Input<\/p>\n\n\n\n enter a comma separated list of Public DNS names that point to your firewall. Sign into GoDaddy to manage your DNS entries? Use whatsmyip.org to verify the public address of your firewall.<\/p>\n\n\n\n Enter a friendly name or just hit enter to use the DNS name<\/p>\n\n\n\n 1: save verification files to a path<\/p>\n\n\n\n enter the path to the miniWeb server. could look something like this C:\\Share\\miniweb\\htdocs HINT: you can paste the path from the clipboard by clicking the lock icon in the top left of the wacs.exe window and choosing Edit, Paste<\/p>\n\n\n\n Copy default web.config before validation = y<\/p>\n\n\n\n Encryption Type = 2 \/ Enter<\/p>\n\n\n\n 1: Store certificate as .pfx file<\/p>\n\n\n\n Path to cert store = whatever i used c:\\share<\/p>\n\n\n\n Password = whatever i used ByeByeMissAmericanPie<\/p>\n\n\n\n 3: No additional Storage<\/p>\n\n\n\n 4: Do not run any Extra installation steps<\/p>\n\n\n\n LetsEncrypt will now try to connect to your HTTP server and retrieve the verification files. If all is working well you should see a bunch of text fly past in the MiniWeb server window, and your Certificate will be created. <\/p>\n\n\n\n If MiniWeb is blank there is a problem with the DNS > FirewalIp > Vip\/PortForward > MiniWeb server<\/p>\n\n\n\n![\"\"](\"https:\/\/increasec.com\/wp-content\/uploads\/2020\/01\/image-6.png\")
<\/figure>\n\n\n\n