IT cloned our production server and now Umbraco loads a 404 error. I've changed the connection string and the machine name and any references to the old URL in the Web.config but it still complains of:
Umbraco.Web.Routing.PublishedContentRequestEngine - FindDomain: Matches no domain
Umbraco.Web.Routing.ContentFinderByRedirectUrl - No match for route: "/en/home".
Any ideas on what I need to do to get this to work?
I actually changed that value by doing an SQL update statement after the server was cloned so it does have the correct value at this point. I realize I'm not supposed to do that but it is set correctly at this time.
I actually changed that value by doing an SQL update statement after the server was cloned so it does have the correct value at this point. I realize I'm not supposed to do that but it is set correctly at this time.
UPDATE: Turns out you were right about the culture and hostnames being the issue because the entry I made did not take effect in the correct location. Once corrected and once app pool permissions added at the root it worked, so it was one of those issues or both.
Cloned production server has no match on domain or route "/en/home"
IT cloned our production server and now Umbraco loads a 404 error. I've changed the connection string and the machine name and any references to the old URL in the Web.config but it still complains of:
Umbraco.Web.Routing.PublishedContentRequestEngine - FindDomain: Matches no domain
Umbraco.Web.Routing.ContentFinderByRedirectUrl - No match for route: "/en/home".
Any ideas on what I need to do to get this to work?
Robb
Hi Robb,
It looks like you're probably missing the hostname - e.g. have you assigned one under "Culture and hostnames"?
(I don't believe they're transferred between environments)
/Chriztian
I actually changed that value by doing an SQL update statement after the server was cloned so it does have the correct value at this point. I realize I'm not supposed to do that but it is set correctly at this time.
I actually changed that value by doing an SQL update statement after the server was cloned so it does have the correct value at this point. I realize I'm not supposed to do that but it is set correctly at this time.
UPDATE: Turns out you were right about the culture and hostnames being the issue because the entry I made did not take effect in the correct location. Once corrected and once app pool permissions added at the root it worked, so it was one of those issues or both.
is working on a reply...