This issue is most likely caused by an incorrect websitePath. Try to set the path in the back end settings (refer to the user guide) or add the information manually to the local configuration file.