- Home
- SSL & security
HTTPS on virtualhost
Some frameworks refuse to run without it, payment sandboxes insist on it, and service workers will not register over plain HTTP. Turning it on locally should not require editing Apache by hand.
On and off from one button
The app runs the same command VXOST has always shipped, then restarts Apache. It tells you what it is about to do first, because restarting the server interrupts anything you have open.
- Port 443 appears among Apache's ports when it worked
- The certificate is self-signed, so browsers will warn once
- Off again just as easily, when a project no longer needs it
The security check, and a warning
VXOST ships a script that reviews the obvious weak points: whether MySQL is reachable over the network, and whether root has a password. The app opens it in Terminal rather than running it silently, because it asks questions and the answers matter.
⚠️ Read those questions before answering. One of them offers
to stop MySQL listening on TCP. Accepting it writes
skip-networking into my.cnf, and from the next
restart every project connecting to 127.0.0.1:3306 fails —
including all of them, since that is how local projects connect. The failure
arrives later than the change, which makes it hard to connect the two.
Backups
The backup command archives configuration, logs and databases. It also asks questions, so it too opens in Terminal. The archive lands inside the VXOST folder: move it elsewhere if it matters, because it is sitting on the same disk as the thing it protects.
What the app never does
- It installs no privileged helper and never edits
sudoers - It asks for your password through the native macOS prompt, each time
- It talks only to vxost.com: a daily check for updates, which can be switched off, the list of PHP versions when you open that window, and after a check for updates if an extra PHP version is installed, and a download only when you click Install
- It sends no telemetry, no analytics and no identifier, ever