andrejs80: Perhaps you don't understand the meaning of the word "should".
This is an odd error and seemingly unrelated to the previous problems, and isn't affecting the subdomains strangely enough. The generation of the site's entry in their Apache web server configuration file apparently got messed up somehow or other. I've contacted support about it.
EDIT:
as a temporary workaround until they fix whatever is messed up with the main domain, you can connect to:
http://core.mbrepository.com/
Instead of the normal site, this is a subdomain that mirrors it and is unaffected. If you have an account you would have to log back in, though.
EDIT 2:
Got this reply back from support, the main site should be working again soon:
This is an odd error and seemingly unrelated to the previous problems, and isn't affecting the subdomains strangely enough. The generation of the site's entry in their Apache web server configuration file apparently got messed up somehow or other. I've contacted support about it.
EDIT:
as a temporary workaround until they fix whatever is messed up with the main domain, you can connect to:
http://core.mbrepository.com/
Instead of the normal site, this is a subdomain that mirrors it and is unaffected. If you have an account you would have to log back in, though.
EDIT 2:
Got this reply back from support, the main site should be working again soon:
I am very sorry for the downtime you have experienced with this website. I checked the site and found that the IP address had updated, but not been put into effect. I ran an update script that has the new IP in place and now it just needs a little time to propagate.