How it works
What happens when you press the button.
Clicking Generate SSL Configuration runs this pipeline against your live WAMP install, in order, on a background thread — with every line streamed to the on-screen log. It validates before it commits and rolls back if anything fails.
- 1
Backup
Timestamped copies of httpd-vhosts.conf and your Windows hosts file are written first, so there is always a clean restore point.
› [1/9] Backup vhosts + hosts backed up (.bak-20260530-1142)
- 2
Root CA
A local Certificate Authority is generated once — RSA-4096, SHA-256, 10-year validity — and reused on every future run.
› [2/9] Root CA RSA-4096 CA ready (reused)
- 3
Trust
The CA is installed into the Windows machine trust store (LocalMachine\Root). If it is already trusted, this step is skipped.
› [3/9] Trust CA present in LocalMachine\Root
- 4
Certificates
One certificate per domain is issued, signed by your CA, with a Subject Alternative Name, serverAuth EKU and 825-day validity. Still-valid certificates are reused.
› [4/9] Certs myapp.test issued (SAN, EKU, 825d)
- 5
Vhosts merge
Clean :80 → :443 redirect blocks and :443 SSL blocks are appended inside a marked section of httpd-vhosts.conf. Everything else is left exactly as it was.
› [5/9] Vhosts merged inside # WampSSL section
- 6
Hosts file
The domains are written to your Windows hosts file as 127.0.0.1 entries, atomically, inside BEGIN/END WampSSL markers.
› [6/9] Hosts 127.0.0.1 myapp.test
- 7
Validate
httpd -t checks the new configuration. If it would not start, the tool rolls back the backups and stops — without ever touching the running server.
› [7/9] Validate httpd -t: Syntax OK
- 8
Restart
The wampapache Windows service is restarted with status polling. If it does not come back, the tool restores the backups and restarts on the known-good config.
› [8/9] Restart wampapache running
- 9
Verify
Each domain is fetched over HTTPS using the same trust chain your browser uses, to confirm the certificate is trusted and Apache is serving.
› [9/9] Verify Verification: 3/3 OK
The safety net you would build yourself, if you had a spare afternoon.
The order is deliberate. Backups happen before any change. Validation happens before any restart. Verification happens after, so success is proven rather than assumed.
If a step fails, the tool does not leave you halfway. It restores the timestamped backups, restarts Apache on the configuration that was working a moment ago, and reports what went wrong — including the tail of the Apache error log — so you can fix the real cause.
Because the whole thing is idempotent, the fix is usually just to correct the input and press the button again.
See it run on your machine.
Download, add a domain, and watch the nine steps go by.