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

Selfhosted

50966 readers
599 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
[–] ryannathans@aussie.zone 5 points 2 days ago (5 children)

What issues are you running into?

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

I'm having a lot of issues, but I don't really know what I'm doing either.

Right now, when I try to run it on my machine, I get this error saying that I can't connect to google then asking if I'm offline. I haven't had this error before when I tried getting it to work, but it's where I am now.

Ultimately, I'd like to reach a point where I can host it on my own machine with a VPN and port forwarding so other people can connect from the outside.

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

That is a regular connection check we implemented to pause the server if the server goes offline. That's likely a warning and not an error, and you can disable it in the worldprops for the server

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

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.

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

If you're getting that message it's running, try logging in with the client

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

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.

load more comments (3 replies)