"Uh-oh! Unable to start site" on macOS with Local 5.4.1

Support
9

Hi David,

Thanks for the follow-up! Copying the site to another site is the best workaround for now as long as you have the site files and an SQL dump

For posterity and other readers:

After reviewing David’s sites.json, the ports property for the individual site services on some sites became an empty object ({}), which will cause the site startup to fail due to not having any allocated ports.

With the missing ports, the sites.json looked something like the following:

"SITEID": {
    ...
    "services": {
        "mailhog": {
            "ports": {},
            "type": "lightning",
            "version": "1.0.0"
        },
        ...
    }
    ...
}

Rather than…

"SITEID": {
    ...
    "services": {
        "mailhog": {
            "ports": {
                "WEB": [
                    10000
                ],
                "SMTP": [
                    10001
                ]
            },
            "type": "lightning",
            "version": "1.0.0"
        },
        ...
    }
    ...
}

If copying the site to another site isn’t possible, you can always create a new site and copy the services property from the newly created site over to the new site and then delete the new site.

Since this is such a tedious task and a complete work-stopper, I have prioritized this bug and have devised a fix. It should be available in the next Local Beta (and subsequently Local) release.