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. Now I’m getting validating 2009scape-master/docker-compose.yml: services.healthcheck additional properties 'timeout', 'interval', 'retries', 'test', 'start_period' not allowed when I run docker-compose up.
Ah man that was just tested. I’ll put that on my todo list.
In its simplest form, without containers, are you able to run the server and connect to localhost using the official launcher? (There’s a setting to swap from stable server to local server)
I was able to run the server properly after building it with ./build -g. I can connect if I select the local server and therefore have localhost for ip address and ip management in the config.
If possible, I’d like to find out where I can put my VPN’s internal IP address (assuming that’s what I need) so I could have the server listen on that interface and let people connect to my server from the outside.
Thanks again for all your help and your contributions to this project.
You shouldn’t need to put your VPN IP anywhere in the server, by default I’m pretty sure it listens on all interfaces. Just the client config I imagine is sufficient
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.
Update your repo and try the new docker files
Thanks. Now I’m getting
validating 2009scape-master/docker-compose.yml: services.healthcheck additional properties 'timeout', 'interval', 'retries', 'test', 'start_period' not allowedwhen I rundocker-compose up.I’m using the repository at https://gitlab.com/2009scape/2009scape
Ah man that was just tested. I’ll put that on my todo list.
In its simplest form, without containers, are you able to run the server and connect to localhost using the official launcher? (There’s a setting to swap from stable server to local server)
I was able to run the server properly after building it with
./build -g. I can connect if I select the local server and therefore have localhost for ip address and ip management in the config.If possible, I’d like to find out where I can put my VPN’s internal IP address (assuming that’s what I need) so I could have the server listen on that interface and let people connect to my server from the outside.
Thanks again for all your help and your contributions to this project.
You shouldn’t need to put your VPN IP anywhere in the server, by default I’m pretty sure it listens on all interfaces. Just the client config I imagine is sufficient