I've updated the template with the changes mentioned by @FestiveKyle.

how do i run this ?

docker run -e DATABASE_URL=postgres://affine:affine@postgres:5432/affine ghcr.io/toeverything/affine-graphql:stable sh -c "yarn prisma migrate deploy && node --import ./scripts/register.js ./dist/data/index.js"

if i run it from conole from the docker -e is unknown and i can't run it from docker exec -it from unraid terminal.

affine installs correct I just cant access the webui

I get the webUI no problem but I can't get past the login screen. Says invalid credentials. How do I set the username and password?

Wonder if anyone is checking this.

 

I started using PhotoPrism and I have now one problem with it, I guess it is some config issue on my Unraid:

I place images to Import folder and if I initiate the import, it reads the Array, but I want only cache actions.

 

Import foler is located on cache drive.

Target where the photos are imported is on /mnt/user which is backed by cache and mover.

I don't understand why it makes a read each time imports one file.

 

After you have testet it, can you adjust the Affine yaml file and remove these two values?

Troubleshooting Part 3:

When I remove the following variables from the config. The container spins up and i get the WebUI with the new version:

Green container:

Troubleshooting Part 2:

When you change the Affine container to an older one:
ghcr.io/toeverything/affine-graphql:stable-e043ecf

Then the container spins up with the settings on my below config.

The register.js is recognized and executed here.

Issue Part 1:

Hello, sorry to disturb you. I am testing the Affine template currently.

I get following issue with the Affine docker container:

node:internal/modules/esm/resolve:275
    throw new ERR_MODULE_NOT_FOUND(
          ^
Error [ERR_MODULE_NOT_FOUND]: Cannot find module '/app/scripts/register.js' imported from /app/
    at finalizeResolution (node:internal/modules/esm/resolve:275:11)
    at moduleResolve (node:internal/modules/esm/resolve:860:10)
    at defaultResolve (node:internal/modules/esm/resolve:984:11)
    at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:780:12)
    at #cachedDefaultResolve (node:internal/modules/esm/loader:704:25)
    at ModuleLoader.resolve (node:internal/modules/esm/loader:687:38)
    at ModuleLoader.getModuleJobForImport (node:internal/modules/esm/loader:305:38)
    at onImport.tracePromise.__proto__ (node:internal/modules/esm/loader:643:36)
    at TracingChannel.tracePromise (node:diagnostics_channel:344:14)
    at ModuleLoader.import (node:internal/modules/esm/loader:642:21) {
  code: 'ERR_MODULE_NOT_FOUND',
  url: 'file:///app/scripts/register.js'
}
Node.js v22.16.0

Standard Settings in the Affine Config:

I doesn´t matter currently which IPs I put into postgresql or redis. The above error comes always, when the container launches.

postgres://affine:[email protected]:5432/affine

Thank you for help

Edited November 1, 2025Nov 1 by sirblizz

Please make the following changes to the template:

• NODE_OPTIONS - not needed anymore, it fails to start the container if left on

• Default Post Arguments should be sh -c 'node ./scripts/self-host-predeploy && node ./dist/main.js'

Container launches normally after these

Edited November 7, 2025Nov 7 by Fallen94

Hi,

i have problems to connect the PhotoPrism container to MariaDB.

My config is based like your comment in the template.

DBUSER:DBPASSWORD@tcp(DBIP:DBPORT)/photoprism?parseTime=true

My database is called photoprism.

My logs shows this Error:

time="2026-01-24T10:27:49+01:00" level=info msg="config: waiting for the database to become available

I doenst work in host and bridge mode.

Any Solutions?

On 1/24/2026 at 10:29 AM, Becksy said:

Hi,

i have problems to connect the PhotoPrism container to MariaDB.

My config is based like your comment in the template.

DBUSER:DBPASSWORD@tcp(DBIP:DBPORT)/photoprism?parseTime=true

My database is called photoprism.

My logs shows this Error:

time="2026-01-24T10:27:49+01:00" level=info msg="config: waiting for the database to become available

I doenst work in host and bridge mode.

Any Solutions?

I found the solution. I use the MariaDB-Official container.

But Photoprism wants that the container identifies itself as mariadb.

I think the mariadb-official container identifies itself as mariadb-official.

The linuxserver Mariadb container works without problems.

Maybe you can add a variable in the template to change the name manually.

And i found a new problem. The initial admin password from the template doesnt work. I had to set a new one manually with the console.

I just tested using a password set in the config and it worked without issue, perhaps you had an existing photoprism folder from a previous install?

For the database config I use the IP of my sever where it shows DBIP:DBPORT. If you're using the container name then it should always use the containers internal port number even if you changed it. For example I have multiple mariadb containers and need to change the ports from 3306 to have 3301, 3302, 3304, etc so when using the IP I need to specify which port to hit the correct container. UNRAIDIP:3304. But when using the container name it should always be 3306 since that's what mariadb uses internally. Mine would then be something like mariadb-official_photoprism:3306. Tested and working.

Currently Testing the Affine Template.

On 3/2/2026 at 2:45 PM, Findthelorax said:

I just tested using a password set in the config and it worked without issue, perhaps you had an existing photoprism folder from a previous install?

For the database config I use the IP of my sever where it shows DBIP:DBPORT. If you're using the container name then it should always use the containers internal port number even if you changed it. For example I have multiple mariadb containers and need to change the ports from 3306 to have 3301, 3302, 3304, etc so when using the IP I need to specify which port to hit the correct container. UNRAIDIP:3304. But when using the container name it should always be 3306 since that's what mariadb uses internally. Mine would then be something like mariadb-official_photoprism:3306. Tested and working.

Also in my case the conection to the maria db container only worked if the container is called "mariadb". The Photprism docu says that the default hostname of the mariadb docker has to be "mariadb". I doenst know how to change this setting in the dockertemplate. In my case i had to named the mariadb docker "mariadb" (like in the linuxserver template. With "mariadb-official" (like in the official template) it didnt work.

Today i made a clean reinstall of photoprism and i had to set up the password manually via terminal again. The password from i set up in the template doesnt worked. I dont tested the docker problem.