Starting or stopping a second site causes an 'ERR_CONNECTION_REFUSED' on first site

Support
1

I’ve noticed this a few times but have only just been able to re-create it.

Essentially, if you have one site started in Local, and it’s running a script or performing a large update, starting or stopping a second site in Local will cause a ‘hiccup’ and make the first site stop working and give a ERR_CONNECTION_REFUSED error. I’ve been able to replicate this fairly consistently.
Not sure if this is due to a memory limit or something to do with accessing a hosts file whilst the second site is starting up.

Has anyone else encountered this?

Jack

1 Like
2

Hey, Jackmcconnell

I was doing everything i could but thanks to you i read what you wrote it really made a difference.

Thank you!!!

1 Like
3

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.