I have an unusual problem with a site I am moving from one host to another.
The new host has given me a temporary URL for checking the site, but this is just showing a 404 error.
The host says this is something Ubraco has happen quite often, and only by making a change to the hosts file to redirect the correct URL will the site work.
By doing this I can get to the home page but none of the other pages, as these redirect to another website. Also I cannot get to the login page of Umbaco for the same reason.
I have moved a number of sites recently and this is the first one to show this error.
Any suggestions on how to get around this error?
I am trying to install the site on another server at the moment.
This seems really strange, sounds to me like the host doesn't know what they're doing to be honest.
Have you tried setting the hostname in Umbraco? Oh wait, that doesn't work, right? Hmmm.. All I can think of ist that the host isn't setting up things properly really. As soon as you can hit 1 page in the site, you should be able to get them all, Umbraco takes over the default.aspx and everything you try to find will resolve through that.
Is it the default IIS 404 error or the Umbraco specific 404?
Then I don't think we can be of much help, the hoster needs to solve this. If they can't make it work on a temp URL, then surely, the real URL is also not going to work. They have just misconfigured it somehow and are trying to put it on you. All they need to do is configure a binding in IIS though, how hard could it be?
404 error when using new hosts temporary URL
I have an unusual problem with a site I am moving from one host to another.
The new host has given me a temporary URL for checking the site, but this is just showing a 404 error.
The host says this is something Ubraco has happen quite often, and only by making a change to the hosts file to redirect the correct URL will the site work.
By doing this I can get to the home page but none of the other pages, as these redirect to another website. Also I cannot get to the login page of Umbaco for the same reason.
I have moved a number of sites recently and this is the first one to show this error.
Any suggestions on how to get around this error?
I am trying to install the site on another server at the moment.
Regards
TT
This seems really strange, sounds to me like the host doesn't know what they're doing to be honest.
Have you tried setting the hostname in Umbraco? Oh wait, that doesn't work, right? Hmmm.. All I can think of ist that the host isn't setting up things properly really. As soon as you can hit 1 page in the site, you should be able to get them all, Umbraco takes over the default.aspx and everything you try to find will resolve through that.
Is it the default IIS 404 error or the Umbraco specific 404?
Hi Sebastiaan
It was a host specific one, so I assume the IIS one had been customised.
Regards
TT
Then I don't think we can be of much help, the hoster needs to solve this. If they can't make it work on a temp URL, then surely, the real URL is also not going to work. They have just misconfigured it somehow and are trying to put it on you. All they need to do is configure a binding in IIS though, how hard could it be?
Hi Sebastiaan
Thanks for the help.
Have just got it up and running on my machine under both an IP address and a different URL.
Its back to the host about this one.
Many thanks.
TT
The host is still saying it is an Umbraco issue.
I am running the site on IIS7, where as they are using IIS6.
Are there any differences between the two that I need to be aware of?
Many thanks.
TT
Ugh.. I haven't seen IIS6 for two years now, so I am not sure. Can you find a host that is not living in 2001? ;-)
That said, you might need to have them set this up for friendly URL's: http://our.umbraco.org/wiki/install-and-setup/setting-up-umbraco-for-friendly-urls
Or you could just disable friendly URL's and use the ".aspx" ones, that might be easier.
I wish I could use one not living in 2001, but this is the designers choice.
Will have a look at this and see what happens.
Thanks
TT
Have found the solution, something was damaged within the database, and this was not responding correctly.
Thanks for all your help.
TT
is working on a reply...