How to configure Memberstack 2.0 with Webflow subdomain after CNAME changes cause 404 errors?
Hello all,
I'm currently working with Memberstack 2.0 and have implemented the login page on a custom domain using the Memberstack JavaScript include. After a user logs in, they are redirected to a Webflow site hosted on a subdomain of that custom domain. The Webflow site also includes the Memberstack scripts.
However, the logged-in state is not persisting after the redirect—the user is not recognized as logged in on the Webflow subdomain.
To address DNS requirements, I updated the CNAME record with my DNS provider as outlined in Memberstack’s documentation. Since making that change, the Webflow site now returns a 404 (Not Found) error.
Has anyone encountered a similar issue or can offer guidance on what might be going wrong? Any help would be greatly appreciated.
Comments
2 comments
Hi Jason, have you enabled cross-domain login as explained in this article?
Yes! I believe we were able to get it resolved and the user is now getting logged in properly. Thank you!
Please sign in to leave a comment.