neko-rooms
neko-rooms copied to clipboard
[FYI] server running neko-rooms changed the public IP. List of issues caused by this action
Hi, The neko-rooms AWS instance changed it's public IP (DKW) so I'm listing here the issues I'm finding to get instance back on track:
- Update NEKO_ROOMS_NAT1TO1
- Update NEKO_ROOMS_INSTANCE_URL
- Containers label: "m1k1o.neko_rooms.url": "http://52.211.54.158:9080/cxA8kBwY/", (didn't update)
- Update running conatiners ENV NEKO_ROOMS_NAT1TO1 (https://stackoverflow.com/questions/27812548/how-to-set-an-environment-variable-in-a-running-docker-container) (1)
(1) To update running containers:
- Find container id
- Stop docker
- Edit containers setting file at
/var/lib/docker/containers/{{conatiner-id}}/config.v2.json
- Restart docker
- Restart container (if needed Live Restore)
After that I could access the room again