this post was submitted on 27 Aug 2025
40 points (100.0% liked)

Selfhosted

51028 readers
1986 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] humanoidchaos@lemmy.cif.su 1 points 3 days ago* (last edited 3 days ago) (1 children)

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.

[–] ryannathans@aussie.zone 1 points 1 day ago (1 children)

Update your repo and try the new docker files

[–] humanoidchaos@lemmy.cif.su 1 points 1 day ago (1 children)

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.

I'm using the repository at https://gitlab.com/2009scape/2009scape

[–] ryannathans@aussie.zone 1 points 1 day ago (1 children)

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)

[–] humanoidchaos@lemmy.cif.su 1 points 22 hours ago* (last edited 22 hours ago) (1 children)

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.

[–] ryannathans@aussie.zone 1 points 15 hours ago

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