Unable to select or enter realm, but can authenticate

[chippey]

Describe the bug Per topic subject, clients (separate machines on network than server) are able to authenticate, but can't select the realm or enter it. Realm shows up on the selection list, but trying to select it just keeps popping up the selection dialog

To Reproduce Modify .yml for location of client data. Start a new docker-compose (simple docker-compose up -d)

Expected behavior Be able to enter the realm

Environment (please complete the following information): Server/Docker hosts: CentOS 7.6, docker version 18.09.6 Clients tried: MacBook runing 10.12, Windows running 10

Log of bringing up a fresh docker stack, using existing world extraction data: https://gist.github.com/chippey/91f36e386429332be457124b8f4b2688

[LuxDincht]

To fix it, you should change in database the "address" in the table "realmlist".

[chippey]

That works! Thanks! Daniel, should I leave this open, or close it?

[danielsreichenbach]

Tasks to resolve this:

• [ ] change the Docker entrypoint to use the IP address assigned to the world server to update the realm list.

[ghost]

I tried to update the address field in the realmlist table, however I can authenticate, but the realm says Offline.

[aetmezgu]

Same issue as ghost, is there any fix possible to not see the realm "offline" ? I tried to change the address field in my "realmlist" table but nothing changed ...

[lindeMAX]

Hi, i just want do summarize the exact steps i did to solve this issue. Hopefully it might come in handy for some one else.

1. Start up the containers
2. Log in to mysql on the mariadb container
3. Select the 'wowstack' database
4. Update the IP-Address of 'Bronzebeard' in 'realmlist'

docker-compose up -d
docker exec -it <container_id> mysql -u wowstack -pp4ssw0rd
USE wowstack
UPDATE realmlist SET address = '<ip of the machine running the containers>' WHERE id = 1

Greets