The timing! I just finished 5 hours of playing on my self hosted server with a friend of mine lol On ubuntu, I just needed java installed, download the git repo, then ran the run sh file. That was it. In the client you edit the config file to swap the public server address with your server's ip and when you launch next, it will connect to yours.
this post was submitted on 27 Aug 2025
40 points (100.0% liked)
Selfhosted
51046 readers
1862 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:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
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.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 2 years ago
MODERATORS
Pretty much this, make sure it's Java 11 though
Sure. I wrote the docker-compose file in the repository. Unless something major has changed, it should be pretty straightforward to just clone the repo and then run
$ docker compose up
IIRC there is a MR to improve it, I just haven't had the time to finish testing and reviewing it
If anybody uses this in prod from a git repo, might want to place your database creds in an .env file adjacent to your compose file then gitignore the .env.
Referenced like so:
.env contents
MYSQL_ROOT_PASSWORD=MyExamplePassword
MYSQL_ROOT_USER=MyExampleUser
docker-compose.yml contents:
MYSQL_ROOT_PASSWORD: ${MYSQL_ROOT_PASSWORD}
MYSQL_ROOT_USER: ${MYSQL_ROOT_USER}
Don't commit secrets to git!
Damn mobile formatting.
No but I definitely want to now that I know this exists
Would recommend playing on the live multiplayer server rather than self hosting
What issues are you running into?
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.
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
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.
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 allowed when I run docker-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