Skip to content
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

just hangs after login with neko:neko #173

Closed
dragonballa opened this issue May 29, 2022 · 3 comments
Closed

just hangs after login with neko:neko #173

dragonballa opened this issue May 29, 2022 · 3 comments

Comments

@dragonballa
Copy link

dragonballa commented May 29, 2022

This is my docker-compose.yml

version: "3.4"
services:
  neko:
    image: "m1k1o/neko:firefox"
    restart: "unless-stopped"
    shm_size: "2gb"
    ports:
      - "8080:8080"
      - "52000-52100:52000-52100/udp"
    environment:
      NEKO_SCREEN: 1920x1080@30
      NEKO_PASSWORD: neko
      NEKO_PASSWORD_ADMIN: admin
      NEKO_EPR: 52000-52100
      NEKO_ICELITE: 1
      NEKO_IPFETCH: https://ifconfig.co/ip
      NEKO_DEBUG: 1

Everything goes smoothly. I navigate to the webpage, it shows me login, I input neko:neko

However the reconnecting blue modal shows up and it is stuck at this loading screen.

What could be the cause? Where can I view logs?

I see a bunch of WRN logs wonder if its relevant.

pingAllCandidates called with no candidate pairs. Connection is not possible yet. module=webrtc subsystem=ice

Failed to start manager: connecting canceled by caller module=webrtc subsystem=pc

Failed to start SCTP: DTLS not established module=webrtc subsystem=pc

undeclaredMediaProcessor failed to open SrtcpSession: the DTLS transport has not started yet module=webrtc subsystem=pc



@m1k1o
Copy link
Owner

m1k1o commented May 29, 2022

It uses your external IP and sends that to the clients. Meaning, ports that you expose 52000-52100/udp needs to be avaliable from outside. Have you chcecked if your port forwarding is correct?

If you want to use n.eko locally, you needs to specify NEKO_NAT1TO1: <ip> to your local IP, that is reachable from the client and has correctly exposed all ports.

@dragonballa
Copy link
Author

thanks, do you mean a port range of 52000 to 52100 ? so hundred ip ports?

@m1k1o
Copy link
Owner

m1k1o commented May 30, 2022

Yes. But generally it means - how many concurrent sessions do you expect, that many ports you should have. So 10 colud maybe be enough for you. See docs: https://neko.m1k1o.net/#/getting-started/?id=why-so-many-ports

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants