Security Reminder
Local does a pretty good job of scrubbing private info from the logs and the errors it produces, however there’s always the possibility that something private can come through. Because these are public forums, always review the screenshots you are sharing to make sure there isn’t private info like passwords being displayed.
Working with multiple developer applications at the same time can be problematic as they fight for ports and connections. You could try changing your Router Mode to Localhost and see if you can proceed that way.
I already tried and it’s almost working. The application I mount , it’s wordpress and woocommerce site from my client only for testing purpose. We building them a middleware so we need webhooks ect to test our middleware locally.
It’s almost working, because now the routing working but all theirs css and stuff are wrongly loaded.
But you make me thinks maybe by checking the wp-config, I’will be able to fix all this stuff. I expect that port of localhost will never change.
Per curiosity, did you have any other idea of making work by domain routing instead of localhost ?
Localhost doesn’t support HTTPS, so that might be causing mixed content or secure connection issues. You could try running S/R to clean up links or see if any cache troubleshooting helps.
To help identify and address Port conflicts with Docker for example you could try steps like this:
Stop all sites that are running in Local
Force quit Local
(If using Mac) Run the command lsof -nP -iTCP -sTCP:LISTEN
(If using Windows) Run the command netstat -ano
What you’ll be looking for here is to see when sites are stopped and Local is properly shut down if there are still programs running on ports 80 and 443. These may be conflicting with Local or the system may be reporting Local is still running.
Once you run that command you should see a list of listening ports. If you see a particular program making use of those ports, you can then kill that process by running sudo kill -9 XXX where XXX is the PID number of that process. (On Windows you will use taskkill /F /pid XXX where XXX is the PID number of that process)
