2024-08-10, 05:35 PM
Hi Efficient_Good_5784
clearing my client cache on chrome fixed it, didn't have to edit any files thank you.
I am a bit curious as to if there was any way it would have worked this out on its own? i missed checking this as with the first instance that i had killed i had tried it on all my devices (that i cared to check) and it showed the same on them too
so seperately samsung interent (phone), Chrome (Laptop), firestick (android).
I am guessing this would have been avoided if i used a different exposed port the second time as it would have loaded as a new page?
either way its fixed so I appreciate your help.
Thank you
clearing my client cache on chrome fixed it, didn't have to edit any files thank you.
I am a bit curious as to if there was any way it would have worked this out on its own? i missed checking this as with the first instance that i had killed i had tried it on all my devices (that i cared to check) and it showed the same on them too
so seperately samsung interent (phone), Chrome (Laptop), firestick (android).
I am guessing this would have been avoided if i used a different exposed port the second time as it would have loaded as a new page?
either way its fixed so I appreciate your help.
Thank you