Studio on Linux and Apache/Nginx web server conflict

### Quick summary

When using WordPress Studio on a Linux environement (specifically Ubuntu) with either the Apache web server or Nginx web server installed, sites using custom domains or custom domains with HTTPS enabled do not load in the browser.

### Steps to reproduce

1. Start the Studio app on a Linux distro (tested on Ubuntu 24.04.4 LTS)
2. Create two sites, one only using a custom domain, and one using a custom domain with HTTPS enabled
3. Confirm both sites work as expected
4. Install the Apache webserver (on Ubuntu run `sudo apt install apache2`) or the Nginx web server (`sudo apt install nginx`)
5. Once Apache is installed, restart both sites in Studio and attempt to access them

### What you expected to happen

I was hoping Studio would work alongside Apache/Nginx.

### What actually happened

Attempting to access the custom only domain site, you'll either get an error (wp-admin) or the default web sever page, attempting to access the site with HTTPS enabled, you'll get a connection refused error.

### Impact

Some (< 50%)

### Available workarounds?

No and the app is unusable

### Platform

_No response_

### Logs or notes

If it is not possible for Studio to work when another webserver is installed, it might also just be useful to add a note about this to the documentation.

Start by reproducing the issue on Ubuntu 24.04.4 with WordPress Studio and Apache or Nginx installed, testing both custom-domain sites described in the report. Trace how Studio handles custom-domain routing and HTTPS when another web server is present; done means the sites work alongside either server, or the limitation is clearly documented.

Written by the indexing model from the issue text.