Handling ports already in use

Indigo

soniktrooth First hurdle I ran across was that I got the message that something was using port 80 and 443 but took me a while to work out it was actually Docker. Perhaps it would be nice to report what process was using the default ports to make it easier to diagnose. I imagine most people interested in this app would be coming from Docker so could be a common issue.

You can actually configure Indigo globally (in the prefs) to use something other than 80 and 443, but it's kinda clumsy to have to append that to every URL eg https://mysite.test:8443. So I agree totally, it would be much more helpful for Indigo to at least give you a clue as to which process is already using the port(s).

I'll put that on my todo list.

soniktrooth

I did initially try changing the ports but wasn't with it enough to realise what that meant in terms of visiting the site. Makes total sense now. Perhaps as a prompt you could append the ports to the site urls when they differ from default

Indigo

soniktrooth Perhaps as a prompt you could append the ports to the site urls when they differ from default

An excellent idea. I've put it on my todo 🙂