Dedicated to the Hydrogen framework, headless commerce, and building custom storefronts using the Storefront API.
hey - we’ve got a Hydrogen / Oxygen headless built where the checkout is going to checkout.mydomain.com and the rest of the site is at mydomain.com.
The issue is that all collections and static pages are redirecting to checkout.mydomain.com NOT mydomain.com. This happened after setting up the DNS per their guide here: https://shopify.dev/docs/custom-storefronts/oxygen/migrate/redirect-traffic#direct-checkout-traffic-...
Any feedback would be much appreciated.
Solved! Go to the solution
This is an accepted solution.
I posted this issue in the slack thread here: https://shopifypartners.slack.com/archives/C02F94JC3QC/p1687799668603189 - here I received confirmation that this was an issue on Shopify's end. They also were able to deploy up a fix for this shortly after. I am confirming that this issue is now resolved!
This is an accepted solution.
I posted this issue in the slack thread here: https://shopifypartners.slack.com/archives/C02F94JC3QC/p1687799668603189 - here I received confirmation that this was an issue on Shopify's end. They also were able to deploy up a fix for this shortly after. I am confirming that this issue is now resolved!
Hello Community,
I hope this message finds you well. I'm reaching out to seek assistance with a critical issue we're experiencing on our website, www.mydomain.com. Our site operates smoothly until the checkout process, where, instead of continuing within our domain, users are unexpectedly redirected to brandname.myshopify.com. This abrupt change not only disrupts the user experience but also raises concerns about the consistency and professionalism of our brand.
We have built our platform using the Hydrogen framework to create a headless commerce experience, aiming for a seamless and integrated shopping environment. Despite our efforts in troubleshooting, including reviewing our Hydrogen setup and Shopify settings, the issue persists, and we're at a loss for what might be causing this redirect.