I'm posting this here because I couldn't find anything with 100% clarity of how to get AdventureLog onto Unraid.

This is the closest official guide I could find but the PostGIS bits were missing crucial details that could leave people scratching their head.

In my scenario I am exposing Adventure Log to the internet and therefore a lot of the variables around URL's are domain addresses.

The guide below exposes AdventureLog to the internet but keeps the admin console on your home network. I think I like it this way. I will try and expose it to the internet so I can add to this post, but since i use WireGurd to remote back home when out of the house, this feels way more secure.

For this guide I am assuming my UNRAID server is 10.0.0.18 on my network.

Assumptions

You've clicked AdventureLog --Backend and it's told you you need PostGIS. So you've installed PostGIS, then tried AdventureLog again and variables don't align. You were never asked to provide:

• Database - Name

• Database - User

If you were to click the official guide, it tells you explicitly to use repo: postgis/postgis:15-3.3

So now you've gone back into the PostGIS container, changed the repo to the above, and now PostGIS won't start. If you look at the logs, you'll see you've installed a new version, then tried to blast with an old version, and it just doesn't like it. Now you're stuck.

It's because of the above assumptions I'm writing this guide. I am not affiliated with PostGIS or AdventureLog. I just wanted the damn thing working as it looked cool.

Word of caution. I'm gonna do a purge of dangling docker images and volumes. I'm not responsible for you knackering your Unraid/Docker server. It's perfectly safe to run the commands I'm using, but heed with caution. It's also perfectly safe to skip this step IF you rename your PostGIS install from the default setting.

Clean your Docker Containers

• Remove PostGIS, and tick the box to remove the image.

• Click Add Container in the bottom left, find PostGIS in the list of existing templates and press the X to remove it.

• Navigate to Appdata and if PostGIS folder exists, delete it

• Open a Terminal window and type the following commands

  • docker image prune -af

  • docker volume prune -f

You're now back to square one and can install PostGIS as per the official guide without issue.

Docker Network

If you've not created a custom Docker Network, use this command from the terminal (changing IP's accordingly)

docker network create \

--driver=bridge \

--subnet=192.168.100.0/24 \

--gateway=192.168.100.1 \

adventurelog

PostGIS Install

The official guide says to use repo: postgis/postgis:15-3.3

That looks pretty old but I'm not here to question our dark overlords so lets do thy bidding. Hit up the APPS tab, find PostGIS and click install.

• Change the Repository to postgis/postgis:15-3.3

• You'll notice you're still missing the extra variables, we'll get them in a mo.

• Install PostGIS as per the official guide. Make sure to pick a custom network.

• Once the install is done, fire up Terminal.

• Type docker exec -it PostGIS psql -u postgres (where PostGIS is your docker container name)

• Type \l

• You'll see a database called template_postgis.

• To spawn a new database from this template, type : CREATE DATABASE adventurelog TEMPLATE template_postgis;

• Now you have a list of databases and your missing variables.

  • Database - User = postgres

  • Database - Name = adventurelog

AdventureLog---Backend Install

With PostGIS installed successfully, you have the ammo you need to install AdventureLog---Backend now, but the chances are you're still gonna be slightly confused with a few variables.

Here's a little helper for the requirements.

• Network Type

  • Ensure you've set this to the same as PostGIS

• Database - Host

  • This is the name of the container PostGIS. The default is likely going to be PostGIS

• Database - Name

  • Assuming you've followed the instructions above, this is going to be adventurelog

• Database - User

  • The default user based on the PostGIS install is postgres

• Database - Password

  • This is what you used during the install of PostGIS

• Secret Key

  • This can be anything you want

• Admin Username

  • This can be anything you want that you're not likely to use as a standard user

• Admin Email

  • Only one email per user so don't use an address you plan to set up for your standard account

• Admin Password

  • Self explanatory

• Public URL

  • So this one tripped me up. It's taken me countless hours, arguments with ChatGPT and many, many clicks in different Discord threads to get this working.

  • This is the IP address of my UNRAID server plus the port number of this docker container.

  • Example: http://10.0.0.18:8015

• Frontend URL

  • This is the IP address of your AdventureLog---Frontend install. If you have assigned an address within the docker container, this works. Or you can use your UNRAID public IP with port 8015

  • Example 1: http://192.168.100.25:8015 (where 192.168.100.25 is my docker container IP for frontend

  • Example 2 http://10.0.0.18:8015 (my IP address for UNRAID)

• CSRF Trusted Origins:

  • Throw every URL you've added so far in here. Plus your exposed https address. Separate each by a comer.

  • Example: https://adventurelog.mynetgear.com,http://192.168.100.25:8015,http://10.0.0.18:8015,http://10.0.0.18:8016

  • Above breakdown: Exposed address, docker container + port for frontend, UNRAID IP + port for frontend, UNRAID IP + port for backend

AdventureLog---Frontend Install

This one is a little easier but the variables still aren't as obvious/explained as they could be.

• Public Server URL

  • This is the name of your backend Docker + :8000

  • Example: http://AdventureLog---Backend:8000

• Origin

  • This should be your exposed address.

  • Example: http://adventurelog.mynetgear.com

Caveats

I can't for the life of me log in with the local IP address. I get the login page, but I can't actually log in (no errors, but nothing happens). I'm ok with using my public facing https address so this is small fry.

Immich Integration

I'll update this when I get it working. No matter what options I set on my Immich API I get a "warning. Permissions shouldn't be empty"

Edited August 5, 2025Aug 5 by elmuziko
Typos

Hi thanks for your work. I had done all with this and this from AlienTech42 https://www.youtube.com/watch?v=hJnoePdAhXg&t=806s (Stop Using Cloud Trackers — Build Your Own Adventure Map on Unraid!) and all looks fine but i cant login to frontend i have Bad Request: /auth/browser/v1/auth/login error on backend. I checked the password and a lot of things and always ends with this error on login. Do you have any idea what i can do?