URL link issues in Umbraco 17

angelrishi · November 25, 2025, 3:24pm

Upgraded umbraco 13 to umbraco 17. Installed Umbraco.Cms.DevelopmentMode.Backoffice so the site starts loading the content.

Only the homepage is loading. All other nodes link simply shows:
“This document is published but its URL cannot be routed”.

I checked culture and hostnames. They look fine. I have 2 domains in culture and hostname:

localhost:44370 English(united states)
webseamsters.com English (united states)

The homepage shows both and loads with localhost:44370.

All other nodes show:

“This document is published but its URL cannot be routed”.
and
webseamsters.com English (united states)

Why the localhost:44370 is not shown and “This document is published but its URL cannot be routed”. shows instead? and why the other domain name shows without any path? just the absolute domain name.

This is same for every node/nested node I open and no pages load except homepage.

Please guide.

shearer3000 · November 26, 2025, 8:57am

I think I’m seeing the same thing (or something similar) after updating an Umbraco 13 CMS to 17 RC3.

In the CMS links section I see the following on everything apart from the Home / first root node:

which has the following response for “/umbraco/management/api/v1/document/urls“:

 "urlInfos": [
            {
                "message": "This document is published but its URL would collide with content 4babb907-cc10-4456-bc45-d12cf9a754aa",
                "provider": "umbDocumentUrlProvider",
                "culture": "en-NZ",
                "url": null
            }
        ]

Anyone been able to resolve? thanks

shearer3000 · November 26, 2025, 9:13am

I also noticed right after I posted above that RC4 nuget packages were available, but updating to those didn’t make a difference to this issue.

angelrishi · November 26, 2025, 11:05am

I resolved this by republishing all the nodes. Approach I took was to use Codex / Github Copilot AI agent and telling it to migrate site from Umbraco13 to Umbraco17. Once this was done, the site got migrated, but the inks had issued. Asked codex to republish all the nodes after sharing the error code with it. That fixed the issue.

you can tell codex to fix this “This document is published but its URL would collide with content 4babb907-cc10-4456-bc45-d12cf9a754aa”
and hope it fixes. Make sure to use Umbraco MCP with Codex or Github Copilot agents. Agent alone will not be able to fix.

mcgrathb1989 · December 11, 2025, 8:50am

My solution was to do the following:

Went to the root node (in my case it was Home) and clicked the 3 dots next to it.
Then selected the Culture and Hostnames option.
Then I changed the language from inherit to my chosen language (English - United Kingdom).
Then I set the domain value to “/” and again chose English - United Kingdom as the option as seen in the below screenshot.

5. Then finally, I went through and republished each node with its descendents and that solved the issue for me.

Hope this helps someone!