-
Notifications
You must be signed in to change notification settings - Fork 572
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
Upgrade to 1.0.49 Unable to connect web socket, click to reconnect. #4242
Comments
Try clearing cookies |
@ClickLeft yes you need to clear your cookies sorry! Because we changed from single domain cookies to subdomain cookies And sadly the old single domain cookie is still left behind and the server gets confused because the client sends two cookies instead of one!? |
Interestingly enough, the issue does not reproduce in FF and Safari, is it a chromium-only case? Chrome and Edge fail the same way. |
Very weird? Happened to me with firefox, but it's simple to fix thankfully!
…On Sat, 9 Jul 2022, 19:50 I2700I, ***@***.***> wrote:
Interestingly enough, the issue does not reproduce in FF and Safari, is it
a chromium-only case? Chrome and Edge fail the same way.
—
Reply to this email directly, view it on GitHub
<#4242 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAF23AV5K2TPRG7ZCGDVSOLVTHCYHANCNFSM53DU4M5A>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Hello . I confirm the bug. The problem appears on Chrome and Firefox when trying to access by IP address, not by hostname. |
@uzmanager2 Just simply clear your cookies and away it goes, it's not a bug! Its Because we changed from single domain cookies to subdomain cookies And sadly the old single domain cookie is still left behind and the server gets confused because the client sends two cookies instead of one!? |
I tried logging in with clear cookies but that didn't solve the problem. When accessing through the hostname - the problem does not appear. |
@uzmanager2 oh yeh crap, accessing via an ip address isn't going to work because of the subdomain cookie! So sorry about this! I never through about ip access!? I'll see if I can do a PR to fix this if it's ip based for the moment As i believe @Ylianst is working on rewriting the web relay for cookies! But for now it is required to access via a domain name! |
I removed the domain for the cookie as that is not going to work well for many people. I am almost done on the improved version with the fix. |
Just put in the fix, working on releasing now. |
MeshCentral v1.0.50 is published. Cookies and web relay should both work. |
Now it works! Thank you very much! |
It works! Thank you very much! |
Wow, that was quick! I Installed the update, but now the "MeshCentral" service doesn't start at all. |
@ClickLeft Can you provide any hints as to what is going on? Your OS, NodeJS version, any errors in "meshcentral-data/mesherrors.txt"? Can you start MeshCentral manually and see if anything shows up? - Thanks. |
OS: Windows 10 21H1 meshcentral-data/mesherrors.txt doesn't exist. Trying to figure out how to start it manually now... "C:\Program Files\Open Source\MeshCentral\winservice\daemon\meshcentral.err.log"
|
AH, If I run it manually via node meshcentral it works! It's like the service needs to be reinstalled. I tried reinstalling everything, but it didn't work. |
If you run
You can try:
|
@Ylianst Thank you, you're amazing! That worked and both issues are resolved. |
I just upgraded from 1.0.48 to 1.0.49. No other changes made. Now I'm getting this error after logging on: "Unable to connect web socket, click to reconnect."
To Reproduce
Steps to reproduce the behavior:
Expected behavior
You would normally see the list of systems after logging in.
Server Software (please complete the following information):
Remote Device (please complete the following information):
Config.json
The text was updated successfully, but these errors were encountered: