-
-
Notifications
You must be signed in to change notification settings - Fork 184
[BUG]disconnected peer disconnect #37
Comments
in container,cat this /home/neko/.local/share/xorg/Xorg.99.0.log
|
few questions |
1.running on public network.
|
are you using cloud flair on |
I try this one https://114.244.66.63:99/ ,same peer disconnect. |
I am able to replicate this bug. Same set up of course different domain and sub-domain. Same exact error messages. Tried in both Chromium, Firefox, Waterfox. No addons installed. Reverse proxied behind nginx, no errors from the proxy. I can't get it to work neither locally or over my domain. Edit: |
Also Affected here |
Installed on a brand new ubuntu 18.04 vm. Disabled ufw for good measure. connecting to it's internal ip to reach the landing page to login (I tried on chrome and firefox). Get the same error message as OP. |
Unable to replicate on a fresh install of neko, Note: UFW was disabled. docker-compose file:
Nginx config:
|
I will try this again later using your exact set up. Sent with GitHawk |
I am still able to replicate with the exact setup you are using. @GigaFyde stdout when trying from mobile. Tested from a few different devices. This time it was on mobile and windows PC desktop from work. I will try one from the local network when I reach home. |
I've pushed the latest commit to docker hub, try running the container with
or add
to the environment section in docker-compose file. |
Ok testing newest commit. Still running into the same issue. I am at home now so I have better access. Here is my set up for this test. docker-compose.yml
Chrome Console:
Firefox Console:
Neko Stdout:
UFW is off. |
I have no idea what is causing this, I do acknowledge that it is an issue, but I can't reproduce on my end. So I've added the help wanted tag |
I'm doing this on a OS X host with Docker installed and it's also reproducible. If you'd like I can attempt to spin up a mac mini or something with remote access that you can use to test this. |
The issue seems to be rather system specific, as I seem to now be able to repro on a different machine. |
System specific for sure I got it working on a different machine.
The real disappointment is that shm setting isn’t available in a docker
swarm cluster and it doesn’t seem to like routing through Traefik now but
that’s a different problem.
…On Wed, Mar 4, 2020 at 3:07 AM Laurant ***@***.***> wrote:
The issue seems to be rather system specific, as I seem to now be able to
repro on a different machine.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#37?email_source=notifications&email_token=AAIE2VU75UR4BUVU2CPP63DRFYD43A5CNFSM4KXURQTKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOENWYQYY#issuecomment-594380899>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAIE2VUTLPWZKNJ7NSKQ25DRFYD43ANCNFSM4KXURQTA>
.
|
It would seem that neko not working locally has to do with neko detecting the hosts public ip and trying to access it. By running it on localhost and disabling all network access to the machine neko 'suddenly' started working as intended. |
after having made the initial connection whilst offline, it keeps working after re-enabling network connectivity and even reconnects after refreshing the page. you can even logout and login again. |
I noticed this on my end as well, why its screwing with me. Its hard to find out what is failing exactly. I think it has to do with some configuration on both the browser's and server's RTC. It could be the lib I'm using server side. |
I'm having similar issues on my end -- Ubuntu server with docker. Chrome console:
Neko logs:
Let me know what I can do to help debug |
Having the same issue as well unfortunately. Will be keeping up here to see if the issue is fixed. |
Well this is embarrassing -- I wasn't forwarding the udp ports. Weird though since it worked fine up until a few updates ago. |
@oransterf that is due to a change I made, you can read more about what I changed here #25 (comment) |
@spiral6 I am facing this same problem only in my local environment. But deployed on VPS it works fine. Are you trying it on local environment? UPDATE: |
@m1k1o where did you add that NAT1to1? I am still getting this same issue when hosting from my servers at home. Haven't tried a VPS. But that is something I may try later this week. |
NAT1TO1 fixed the issue for me as well, works amazingly now. Thanks so much for this! |
@SweetLouHD @m1k1o Yea anyone externally connecting just keeps getting disconnected regardless of the browser/device.
seems to be what keeps popping up in the stdout. Gonna try some more tests. |
@Aersaud so only websocket is disconnecting? Do you use port forwarding / NAT? Or any reverse proxy? Something like |
@m1k1o I have port forwarding enabled on the router for the udp ports 59000-59100. Tried doing host networking to isolate that. I am using NAT and reverse proxy is nginx. Yep just the websocket so they start connecting and get peer failed. If I remove 1to1 no one can connect not even myself. |
|
@nurdism Yes I tried that, when it's removed no one can connect not even myself same error messages as before. With NAT1TO1 I am able to connect with multiple devices on my local network atleast. |
then it might be a port issue, make sure you can access the udp ports accessible via your public ip |
@nurdism @m1k1o I figured it out! Apparently I had some kind of block via my DNS. Everything is working as expected now! Very excited to start using this with my friends especially due to the isolation here in NY. I will see what I can contribute. My GO is not the greatest, however I am fluent in other programming languages. |
If I have nat1to1 set with my external IP, I have to use my PIA vpn to get it to work. It will not work if I try nat reflection. |
I am able to log in locally when I put in my 192.168.x.x address in the docker-compose. I cannot log in when using my domain however. If it helps I'm using
I have used both my IP and also my domain (neko.xxxx.com) as the Any ideas on how to do this for if using a reverse proxy? |
@nukke Please make your own issue as I believe your problem to be beyond the scope of this one. There are also problems with what you have said that need to be ironed out. |
As a note, this issue is still open for those who are still having this issue and are trying to debug it. This is a place to discuss the issue, not to rant. |
I replied before i realized the brain spasm had been cleaned up. Thank you @nurdism for your patience moderating on the Internet can be tedious.
Thank you for your commitment to Neko I’m looking forward to giving it another chance soon.
|
Hi, what is the status of this issue? |
It's not really an issue, its 100% been due to networking outside of neko, but the issue continually get brought up so the ticket is only open to help debug |
@nurdism perhaps linking directly to the solution in a final comment prior to closing the issue would be prudent. |
Describe the bug
can not link to server https://pc.zzz9958123.com:99
docker-compose.yml
Desktop (please complete the following information):
Client Log:
Server Log:
The text was updated successfully, but these errors were encountered: