-
Notifications
You must be signed in to change notification settings - Fork 50
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
Windows client stays in logging in status... #57
Comments
Try log out and login again |
Not even funny. I logged in 1000 times on DIFFERENT computers and the same number of times I rearranged the application itself and TAP devices at the same time. It does not help! |
I am sorry for your inconvenient. I tried on my windows 10, sometimes it takes twice to get the login. @harri8807 Can you help ? |
I don't your understood answer. What do I need to do? I even created a 2-account to verify. 1 - google login. 2 - by e-mail and pass. And I can't go into both of them. Can you explain normally what I should do? Thanks for the quick replies... |
It looks that your windows client didn't get the token from the websocket. There is nothing special to use windows version, I do exactly the same the video did. https://omniedge.io/download/windows. |
I'll ask you again. What course of action should I take? Link - https://omniedge.io/download/windows I saw it. This is the most common installation.... And I DON'T know how source code will help me. I'm not a programmer. I'm a regular user. And I ask for advice, how do I log in from the Windows client? For the author of the program, this should be a simple question... |
Here is the text of the log: |
2022-11-22 01:17:50 TapManager: "C:/Program Files (x86)/OmniEdge\tap-windows\add_tap_device.bat" exists. 504 Gateway Time-out."2022-11-22 01:20:32 "API: Error when connecting to websocketInvalid statusline in response: nginx/1.20.0." 2022-11-22 01:20:32 "API: Error when connecting to websocketInvalid statusline in response: ." 2022-11-22 01:20:32 "API: Error when connecting to websocketInvalid statusline in response: ." |
You computer has network problem to connect the api. |
Have you read what I write to you? I used 4 different computers. And virtual. with DIFFERENT OS. Is everything so bad at once? That's why I'm writing here to get HELP at last. I look forward to your real advice HOW I can fix this problem. To Tailscale, for example, (have you heard about this???) ALL of these computers connect WITHOUT ANY problems ... I'm waiting for SPECIFIC help. And NOT ascertaining that everything is bad ... |
The communication from your computer to the API is the only reason I can see so far. I don’t know how to fix your network problem. Tailscale is a good product, if it works for you and solve your problem, I am happy to hear |
I wrote not about the fact that Tailscale is good, but Omni is bad. But only about the fact that from the same PC I connect to TS without any problems. Well, you, at least offer to do something. BUT? Any thoughts on this? "I DON'T KNOW" sounds quite shameful. I have son. Long ago, when he was little - I taught him to never say "I don't know"... Sorry... |
issue to: #59 |
Tried this on Windows 7 and Windows 11 hosts and virtual machines.
![123](https://user-images.githubusercontent.com/65159864/203156006-e43e5c75-8f02-4ebc-861a-5d01c1eac4e3.png)
In addition, I launched the subject in a Docker container on 2 different VPS. These 2 clients have been added. But ping doesn't go between them...
The text was updated successfully, but these errors were encountered: