Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at

  • Carlos Casalicchio 109 posts 471 karma points
    Aug 19, 2019 @ 14:29
    Carlos Casalicchio

    Cultures and Hostnames issue with Request URL

    I am developing a multi-tenant project for a client. The tenant sites support multi-languages, and several child pages.

    When multiple tenants are created, I don't need to set Cultures and Hostnames because the subdomains are always different.

    For example:

    But, since all the children will have the same relative paths, the child pages return errors "This document is published but its url would collide with content /Umbraco Test 40/Sport (id=1484)"

    By setting the cultures and hostnames, the issue does not happen. But then it seems that Umbraco starts ignoring the Request Url, and always opens the first tenant's site.

    The client is using Cloudflare for DNS and caching, and has not setup any type of IIS bindings (one of their requirements it to NOT have IIS bindings).

    I'm having a hard time figuring this one out. Any suggestions, Or, am I doing something wrong?

    I have set a personal VPS (I'll leave on for now), and the languages work, and the child pages work (i've only set the sports page for now)

    But I have set the IIS bindings, and it all works. So, I'm not sure how to make it work without the IIS bindings.

    IIS Bindings

  • Alex Skrypnyk 5754 posts 21844 karma points MVP 4x admin c-trib
    Sep 02, 2019 @ 21:10
    Alex Skrypnyk

    Hi Carlos

    Did you solve this issue?


  • Carlos Casalicchio 109 posts 471 karma points
    Sep 03, 2019 @ 13:53
    Carlos Casalicchio

    Hi Alex,

    Yes, the client figured out that the issue was in their SSL configuration, it had nothing to do with umbraco or IIS. They wanted to avoid doing IIS bindings for each site, so they had a complex setup with CloudFlare for caching and DNS, which was making me suspicious the issue was the CDN.

    But it turned out it was all in their SSL configuration, once they figured it out, everything started working without even needing to set an IIS binding for each site.

    I was relieved :)

Please Sign in or register to post replies

Write your reply to: