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

[FYI] server running neko-rooms changed the public IP. List of issues caused by this action #62

Open
gbrian opened this issue May 2, 2022 · 0 comments
Labels
enhancement New feature or request

Comments

@gbrian
Copy link
Contributor

gbrian commented May 2, 2022

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:

(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

@gbrian gbrian changed the title [FYI] neko-rooms server changed the public IP. List of issues caused by this action [FYI] server running neko-rooms changed the public IP. List of issues caused by this action May 2, 2022
@m1k1o m1k1o added the enhancement New feature or request label Dec 23, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants