-
Notifications
You must be signed in to change notification settings - Fork 23
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
Socket closed: The URL ... does not match any allowed pattern from undefined #8
Comments
Never mind, it appears to work when I use different devices, just doesn't show the cursors in different tabs in the same browser (although it does do that when I enabled localhost and run my local setup). I'm still getting the warning in all cases except in the localhost setup. |
I apologize, what I was seeing were multiple cursors from |
Weirdly, I'm not seeing any errors on https://cursor-party.whitep4nth3r.partykit.dev/ but I am seeing errors on https://cursor-party.kdheepak.partykit.dev/ And I can see that multiple cursors works on https://whitep4nth3r.com/ I tried in a different browser as well and I'm seeing the same result. @whitep4nth3r apologies for the ping but I'm curious if you made any changes to your cursor-party deployment for this to work? |
@kdheepak Everything I have modified from the fork is in this list of commits all pushed to my fork on 8th November: https://github.com/whitep4nth3r/cursor-party/commits/main/ |
Thanks for the reply! Weirdly, when I try your repository with no changes I still get the same error message on my account. |
I get this error message when I try to visit my domain where I have cursor party enabled:
The cursor party appears to be working when I add
http://localhost:4321/*
to one of the allow listed sites and when I test it with my development environment. So it appears that the code I'm using (i.e. adding the script tag to before thebody
end tag works). But it doesn't seem to work once I deploy my static site to cloudflare.Do you happen to know what I may be doing incorrectly?
The text was updated successfully, but these errors were encountered: