I followed the same advise given by the online documentation and still have the same issue whenever I close DevKinsta and re-open it. Everytime I start the app I have to use the terminal to kill all tasks using port 80 before it will run properly. Too bad I was not able to test it as I wanted to.
Hey @michael, any update on being able to use different ports for nginx?
This is a show stopper for me. I’m trying to create a workflow for migrating client sites from Joomla to WP, so the Joomla sites live in my host’s native web service. I figured using DevKinsta was a quick way to get the new WP sites installed, work on them locally, and pushed back to Kinsta.
I can’t move the main web service ports, as I have a lot of existing infrastructure and development toolchains that expect them to be on the native ports.
This is pretty fundamental stuff. The DevKinsta containers are literally guests. They shouldn’t assume they can just usurp the default service ports on the host.
I’ve tried changing them in the nginx config in the container, but the container just crashes when I try and restart nginx. I’d be happy with that as a solution for now, if you have any suggestions on how to move the ports by hand while we wait for it to be a built in feature.