Skip to content

Ambiguous URL provided, did you omit the domain in a multi-site setup? #91

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
davidpattaguan-gsquared opened this issue Feb 19, 2025 · 2 comments

Comments

@davidpattaguan-gsquared
Copy link

davidpattaguan-gsquared commented Feb 19, 2025

Trying to setup multisite using this repo, are there any existing implementation on how I can do it via this repo?

@myuzhyk
Copy link

myuzhyk commented Mar 27, 2025

The question is still relevant.
When adding the second application, I get this error:

**Internal error: Error: 🔴 [RouteResolver] Ambiguous URL provided, did you omit the domain in a multi-site setup?** 
at OptimizelyCms13Client.getRouteByPath (../../.yarn/__virtual__/@remkoj-optimizely-graph-client-virtual-d439c2ed6b/0/cache/@remkoj-optimizely-graph-client-npm-4.3. 1-b9d85a09e5-2358afecfc.zip/node_modules/@remkoj/optimizely-graph-client/dist/services/routing/queries/cms13/index.js:50:19) 
at process.processTicksAndRejections (node:internal/process/task_queues:105:5) 
at async getInfoByPath (../../.yarn/__virtual__/@remkoj-optimizely-cms-nextjs-virtual-fd6c26f235/0/cache/@remkoj-optimizely-cms-next js-npm-4.3.1-a76ebe82eb-cf2ab75885.zip/node_modules/@remkoj/optimizely-cms-nextjs/dist/cms-page/page.js:73:23) 
at async Module.generateMetadata (../../.yarn/__virtual__/@remkoj-optimizely-cms-nextjs-virtual-fd6c26f235/0/cache/@remkoj-optimizely-cms-nextj s-npm-4.3.1-a76ebe82eb-cf2ab75885.zip/node_modules/@remkoj/optimizely-cms-nextjs/dist/cms-page/page.js:104:31)

@remkoj
Copy link
Collaborator

remkoj commented Apr 18, 2025

Doing a multi-site isn't yet fully documented. The code assumes the following

  • You're deploying an frontend (Vercel Project) per website
  • You'll implement a ChannelDefinition (from the @remkoj/optimizely-graph-client) package and provide that to the main catch-all route, so it can filter the routes for the specific website.

The error is showing that the same route exists in more then one application, hence the error. The domain it refers to is normally inferred from the ChannelDefinition.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants