Arch Linux User Repository

is it possible to ship pre-built package?

Upstream recommends using docker, for which they have pre-built images (that might also work with podman).

PostgreSQL 18 is coming to the Arch repos. Before upgrading, backup the files for vectorchord and pgvector somewhere, and then follow https://wiki.archlinux.org/title/PostgreSQL#Upgrading_PostgreSQL instructions. (In the next release, I'll also update the postinstall message to recommend changing postgresql.conf instead of doing ALTER SYSTEM SET.)

Also, you may find yourself updating VectorChord in this process. When doing so, remember to follow the migration steps at https://docs.immich.app/administration/postgres-standalone/#updating-vectorchord .

immich-web (localhost/immich-server:2283) used to be broken for some users of this package.

As @yparitcher also noticed, this was most likely caused by the following additions to .gitignore from f4e0aad2c495, which have since be reverted:

src/
pkg/
*.pkg.tar.zst
LICENSES/

The reason—for both this change sometimes and unpredictably breaking the build, and builds under a clean chroot still working—is unknown. I meant to investigate this on 2025-08-19 while updating the package but called it a day due to the unpredictability and long time of building. Help with figuring out why this happened would be greatly appreciated.

You may notice pacman refuse to upgrade this package, saying warning: cannot resolve "vectorchord", a dependency of "immich-server".

This is due to required manual intervention within the immich server database.

Newer versions of immich server have deprecated pgvecto.rs in favor of vectorchord.

Before updating from 1.133.1 or older, please follow steps 1 and 2 of the manual migration steps (should be the second dropdown) at https://immich.app/docs/administration/postgres-standalone/#migrating-to-vectorchord and uninstall pgvecto.rs.

Remember to remove references to "vectors.so" (which is shipped by pgvecto.rs) in shared_preload_libraries before pgvecto.rs in uninstalled. (For vectorchord to work, you'll need to add "vchord.so" to shared_preload_libraries after the upgrade as well.)

After that, you may upgrade this package. Please remember to follow steps 4 and 5 of the manual migration steps after the upgrade is finished to prevent data loss.

@dhtseany yup, it seems to be failing to init the db as you said. Make sure you have a working psql instance running, create the db following the arch wiki for psql, and set the required config parameters on /etc/immich.conf.

Also, you might have to enable the vectorchord extension on psql while you're at it, you can follow the "source" installation guide from vectorchord https://docs.vectorchord.ai/vectorchord/getting-started/installation.html . Just skip the first step, since you've already built vectorchord from the AUR. Also, you might want to use vectorchord instead of vectorchord-immich-bin, since the latter seems to be a bit outdated.

$ journalctl -xeu immich-server.service
Dec 01 07:48:23 archnas immich-server[317825]:   severity_local: 'FATAL',
Dec 01 07:48:23 archnas immich-server[317825]:   severity: 'FATAL',
Dec 01 07:48:23 archnas immich-server[317825]:   code: '3D000',
Dec 01 07:48:23 archnas immich-server[317825]:   file: 'postinit.c',
Dec 01 07:48:23 archnas immich-server[317825]:   line: '1014',
Dec 01 07:48:23 archnas immich-server[317825]:   routine: 'InitPostgres'
Dec 01 07:48:23 archnas immich-server[317825]: }
Dec 01 07:48:23 archnas immich-server[317825]: Node.js v25.2.1
Dec 01 07:48:23 archnas systemd[1]: immich-server.service: Main process exited, code=exited, status=1/FAILURE

Hi @dhtseany, I've experienced the same behaviour before, immich seems to start correctly based on what systemctl status tells, but it doesn't really work. Try checking "journalctl -xeu immich-server.service" right after service startup, and browse up the log to see if it's throwing any exception.

@aliu thanks for your help!

I don't have a software firewall on this system, it's internal-only for development purposes.

Netstat doesn't show web servers occupying the port, either.

immich-healthcheck returns: curl: (7) Failed to connect to localhost port 2283 after 0 ms: Could not connect to server Fail: exit code is 7

...which suggests the web server actually isn't running, right?

I went ahead and triple-checked the immich-server service status and it look like it's frequently restarting even though it says it's running but I noted that "immich-server.service: Scheduled restart job, restart counter is at 16788." at the bottom.

Finally, I was wondering what, if any, setup prep was required of Postgresql? I'm new to this app (test driving it to try and replace Google Photos) but upon review of the provided documentation online I didn't see much discussion about the DB side of things. After reviewing the Arch Wiki page for Postgresql I found that it's service wasn't running nor had it been initialized so I did a sudo su postgresql -> initdb -D /var/lib/postgres/data -> then started postgresql service however that still didn't seem to help immich's web app start either.

Did I need to worry about any DB setup or was the immich-server install (or it's upstream scripts) somehow supposed to do that bit for me? Thanks!

Did you set your firewall to allow traffic through port 2283? What does immich-healthcheck on your server say?

Apologies if I'm missing something obvious but was I expected to start/enable any services after install?

I've tried running the immich-server.service, which appears to be running, but http://<ip-of-server>:2283 isn't responding to requests.

I picked vectorchord-immich-bin when asked which package to provide vectorchord.

(I fixed the checksums yesterday, too. Happy thanksgiving and a merry new- month!)

@CountMurphy in my case, the admincodes files failed also. After fixing the checksums it worked all right, so no big deal.

Happy thanksgiving (if you're state side). I come bearing bad news: cities500.zip is failing checksum

There's groundwork in 2.3.0 on a plugin-based architecture which modifies the installation instructions. I'll hopefully finish this tomorrow night.

Note that the update-checker bug does not affect the mobile app, so use that in the meantime ig.

Edit: Okay, I didn't see @cebtenzzre's edit, but still I don't have enough time today.