Thanks. It could be nothing, but I’m also thinking it might be an issue on my end from improperly changing configurations while trying to get self hosting to work.
I just don’t know enough so I’m going to keep fiddling with it. I’ll keep your advice in mind and not focus too much on the warning while figuring this out.
I’ve made sure the changes persist by either setting the file to read-only, or just avoiding changing the server setting at the game client launcher.
The only change I’ve made for the server was changing 2009scape-master/docker-compose.yml. I put the VPN port to the left side and left everything else the same.
Thanks. It could be nothing, but I’m also thinking it might be an issue on my end from improperly changing configurations while trying to get self hosting to work.
I just don’t know enough so I’m going to keep fiddling with it. I’ll keep your advice in mind and not focus too much on the warning while figuring this out.
If you’re getting that message it’s running, try logging in with the client
Thanks. I’m probably doing something wrong here.
When I try to connect while self-hosting, I get stuck at “Connecting to update server” when Runescape is loading in the client window.
In
~/.local/share/2009scape/config.json, I have:{ "ip_management": "[VPN INTERNAL IP]", "ip_address": "[VPN INTERNAL IP]", "world": 1, "server_port": [VPN FORWARDED PORT], "wl_port": 43595, "js5_port": 43595, "ui_scale": 1, "fps": 0 }I’ve made sure the changes persist by either setting the file to read-only, or just avoiding changing the server setting at the game client launcher.
The only change I’ve made for the server was changing
2009scape-master/docker-compose.yml. I put the VPN port to the left side and left everything else the same.version: '3.3' services: app: build: . container_name: "2009scape_app" depends_on: - database restart: unless-stopped volumes: - "2009scape_app:/app" ports: - "[VPN FORWARDED PORT]:43595"Sorry if I come across as a novice. I’m still learning and any help is always appreciated.