Search results

It seems to be all sorted out. DNS propagation can take up to a few days, even if they generally take a few minutes to a few hours.

It will only delete your hosting account, yes.

Link to the site?

Try clearing your cookies for the login.

What would this 'domain service' be? You should still be able to use X10 with different name servers after. At least that was the case for CloudFlare's DNS service.

The name server check is there for verification. You could either use the X10 nameservers and then remove then after adding or you could wait for someone with sufficient access to add it themselves (getting around the check).

You will need to either turn on error logging or display errors (if you go with 'display_errors', turn it off when in production). This short guide will lead you to the correct page: https://x10hosting.com/support/account/my-website-is-showing-a-blank-page

Looks like the certificates need sorting out. If you are wanting to visit the site anyway, you can either use HTTP instead or proceed using the link in the spoiler that Chrome provides.

Okay so it is not that sort of poor detection method.. Try checking the results on this site: http://whatismyipaddress.com/proxy-check You can, though probably not necessary, check if your IP (range) is on a blacklist: http://whatismyipaddress.com/blacklist-check (Do not be surprised if it...

Are you hosting any services on your network (web server, gaming server, ...) ?

Via FTP or file manager (in cPanel), go to the directory where you installed Joomla, edit 'configuration.php' and search for something like this: public $live_site='example.com'; If the domain within the single quotes is not your custom domain, change it to your custom domain. Like so: public...

Have you previously set up Joomla with the sub-domain? From the looks of it, there is some sort of redirect involved. What fascinates me is the fact that it uses *.x10hosting.com rather than *.x10host.com.

From the looks of it, it could be either mod_security2 or the firewall blocking the server-side requests Jetpack is attempting to put out.

Which software are you using for your site? You will need to configurate it to use your new domain via the free sub-domain provided.

By disputing, if it were to be an administration suspension. Is this by any chance a 'substantial link' one you had encountered?

You may delete the 'cgi-bin' folder. It will cause no harm. If your site appears on the desired domain then that should be all good.

They can use their own domains. Just not as a default one. If I recall correctly, it was said that the reason for this was because domains would end up expiring for some (not renewing their domains in time) and so their sites become inaccessible via that domain. This would cause trouble for the...

If it ends up with duplicate results (because of the sub-domain), you can always use Google Webmaster tools to request removal of results for that sub-domain or any other tool that does the same thing on other search engines. You can kind of break the sub-domain so that it no longer points to...

You will need to wait for someone with sufficient access rights to configurate it correctly. Normal users cannot resolve this as far as I am aware of.

It looks like the virtual hosts might have not gone well on your end. This means repairing for those who have access.