nice one cheers, i'm still getting the error on my browser and phone so it must be a DNS delay that has caused the conflict i mentioned in the other thread.

so i'm guessing once everyone's DNS has caught up the error should be gone.