search

m1k1o / neko-rooms

Selfhosted collaborative browser - room management for n.eko
Apache License 2.0
437 stars 59 forks source link

After neko-rooms creates a room, must restart docker before you can enter the room #124

Open Believe1011 opened 5 months ago

Believe1011 commented 5 months ago

Hello, when I use the tutorial to install neko-rooms in the intranet environment, I have to restart docker to enter the room, this is my env file.

TZ=Asia/Shanghai NEKO_ROOMS_EPR=59000-59100 NEKO_ROOMS_NAT1TO1=192.168.211.87 NEKO_ROOMS_TRAEFIK_DOMAIN=test.com NEKO_ROOMS_TRAEFIK_ENTRYPOINT=websecure NEKO_ROOMS_TRAEFIK_NETWORK=neko-rooms-traefik NEKO_ROOMS_TRAEFIK_CERTRESOLVER=lets-encrypt NEKO_ROOMS_NEKO_IMAGES=m1k1o/neko:firefox m1k1o/neko:chromium m1k1o/neko:google-chrome

我在本地hosts文件中添加映射192.168.211.87 test.com

m1k1o commented 5 months ago

You mean restarting docker daemon? Seems like an issue with docker installation, that it is probably not setting up network properly. I never heard of such issue, with other containers it works without restarting?

Believe1011 commented 5 months ago

When I've added a room, I'm waiting to sign in until I'm prompted to time out, and when I restart with docker-compose, I can enter the room. My deployment environment is on a LAN

m1k1o commented 5 months ago

Could you compare room logs (docker ps, find room, docker logs <container-name>) before and after restart? Whats different there. Also check neko-rooms logs if there is anything relevant. Make sure to have set NEKO_DEBUG=1 env variable and NEKO_ROOMS_DEBUG=1 for neko rooms to get verbose logs.

Believe1011 commented 5 months ago

neko_debug.log This is the complete log of my actions after creating a room. Could you please help me take a look

jameskitt616 commented 3 months ago

I do have the same issue. When i create a new room with an, in my case, Intel iGPU and start it. It fails to start, i need to stop it and start it again, then it works and continues to work.