gagimilicevic · November 27, 2019 10:43
diff --git a/gistfile1.txt b/gistfile1.txt
 Thanks! That’s very helpful.

 Based on the output, Apache appears to be running. Heads-up, if you’re using it for another project, the commands below will temporarily stop Apache.

 Can you try the following?

 Try running sudo service apache2 stop. If it results in an error, you may need to find a different stop command for Apache from this blog post: http://www.learn4master.com/programming-language/shell/start-restart-and-stop-apache-on-linux

 Run netstat -ltnp | grep -w ':80' again after a few seconds and see if Apache stops listening on port 80.

 If 1 and 2 look good, try creating a new site in Local and see if you can access it.



 Is it not possible to run Local and Flywheel on the same time? I use to run the xampp and local on my Windows machine at same time.


 I experience this same issue whenever Local is not shut down correctly. Running the commands:
 sudo fuser -k 80/tcp
 sudo fuser -k 443/tcp
 And then starting a site will fix it. Perhaps Local can check to see if Apache is running on startup and issue a restart so that the router can bind correctly?
	Thanks! That’s very helpful.

	Based on the output, Apache appears to be running. Heads-up, if you’re using it for another project, the commands below will temporarily stop Apache.

	Can you try the following?

	Try running sudo service apache2 stop. If it results in an error, you may need to find a different stop command for Apache from this blog post: http://www.learn4master.com/programming-language/shell/start-restart-and-stop-apache-on-linux

	Run netstat -ltnp \| grep -w ':80' again after a few seconds and see if Apache stops listening on port 80.

	If 1 and 2 look good, try creating a new site in Local and see if you can access it.



	Is it not possible to run Local and Flywheel on the same time? I use to run the xampp and local on my Windows machine at same time.


	I experience this same issue whenever Local is not shut down correctly. Running the commands:
	sudo fuser -k 80/tcp
	sudo fuser -k 443/tcp
	And then starting a site will fix it. Perhaps Local can check to see if Apache is running on startup and issue a restart so that the router can bind correctly?