On 9/9/2023 at 9:37 AM, Findthelorax said:

Are you getting any errors in the container logs? I just installed it without issue after fixing permissions on the emqx appdata folder which may be my fault somewhere. I'll update the template with PUID/PGID variables. I ended up switching back to mosquitto after having some issues later on with emqx. I use Dozzle to view the logs and troubleshoot but if you post them and I'll do my best to help.

Yes, I am having issues with EMQX it says it cannot create the files and folders it needs due to permissions issue

where is the file to edit the data? i cant find it, like every app in appdata with ¨config¨ file

why i need that?

want to do this

because its using avx

in regards to EMQX, everytime i stop the container the accounts i create in user management. Any idea why this isn't being saved in appdata?

 

edit: i think setting the node name *should* fix this issue, I will update later and confirm.

 

EMQX_NODE__NAME: [email protected]

 

Edited July 16, 20241 yr by spyd4r

Yea, doesn't work. Fresh install. Logs just contain the following:

started 240711 as root (amd64-prod)
init: account with the user id 99 already exists
init: updating filesystem permissions
PHOTOPRISM_DISABLE_CHOWN="true" disables permission updates
Problems? Our Troubleshooting Checklists help you quickly diagnose and solve them:
https://docs.photoprism.app/getting-started/troubleshooting/
file umask....: "0002" (u=rwx,g=rwx,o=rx)
home directory: /photoprism
assets path...: /opt/photoprism/assets
storage path..: /photoprism/storage
config path...: default
cache path....: default
backup path...: /photoprism/storage/backups
import path...: /photoprism/import
originals path: /photoprism/originals
switching to uid 99:100
/opt/photoprism/bin/photoprism start
/opt/photoprism/bin/photoprism start
/opt/photoprism/bin/photoprism start

 

Here is what I see. It "refused" to connect, which tells me it is responding but won't serve any web traffic:

 

Edited August 5, 20241 yr by jaylo123

I got EMQX working. I did have to run the below code which I don't believe is secure so use at your own risk.

 

chmod -R 777 /mnt/user/appdata/emqx

 

As for PhotoPrism:

 

@Artiom97es I believe you can set those as environment variables when editing the container.

 

@jaylo123 What do your settings look like? What database are you using? It looks like it should be starting.

Affine

 

Hello I got the application running but when I try to log in with the email from the AFFINE_ADMIN_EMAIL variable and the password from AFFINE_ADMIN_PASSWORD I got only an error message:
 

Quote

Failed to send email. Please try again.

 

 

 

Howdy, I literally just heard about this app this weekend and got it running. I haven't figured out login in yet but I do remember seeing there are issues with connecting the self-hosted version to the desktop app and such. I will look into this but it may be a while until I can provide a definitive answer.

The Affine login doenst work. Tried everything, no deal. Anyway to fix it?

Edited August 11, 20241 yr by Delscipio

I've managed to get the program running with the mailer configured correctly and reached the login screen. When I enter the email address specified in AFFiNE_ADMIN_EMAIL, I receive an email with a link to create an account instead of logging in. Also, when I click the link, it opens a new browser tab with the URL http://localhost:3010/magic-link..., and I encounter the following error in the logs: 

 

[Nest] 1  - 08/13/2024, 4:29:17 PM   ERROR [HTTP] Internal server error
PrismaClientKnownRequestError: 
Invalid `prisma.user.create()` invocation:


An operation failed because it depends on one or more records that were required but not found. No 'Feature' record(s) (needed to inline the relation on 'UserFeature' record(s)) was found for a nested connect on one-to-many relation 'FeatureToUserFeature'.
    at _n.handleRequestError (/app/node_modules/@prisma/client/runtime/library.js:121:7749)
    at _n.handleAndLogRequestError (/app/node_modules/@prisma/client/runtime/library.js:121:7057)
    at _n.request (/app/node_modules/@prisma/client/runtime/library.js:121:6741)
    at async l (/app/node_modules/@prisma/client/runtime/library.js:130:9355)
    at async AuthController.magicLinkSignIn (file:///app/dist/core/auth/controller.js:102:22)

 

For those interested in how I got the mailer working, here’s what I did:

Edited the Docker container and added the following four variables:

 

Name: AFFiNE_MAILER_HOST

Key: MAILER_HOST

Value: [Your Email SMTP Server]

 

Name: AFFiNE_MAILER_PORT

Key: MAILER_PORT

Value: [Your SMTP Port]

 

Name: AFFiNE_MAILER_USER

Key: MAILER_USER

Value: [Your Email Address]

 

Name: AFFiNE_MAILER_PASSWORD

Key: MAILER_PASSWORD

Value: [Your Email Password]

 

This setup allows the mailer to function correctly, sending emails as expected.

You may need to setup an App Password if you're using outlook or Gmail.

Yes, that's as far as I've gotten. I'll keep looking into it and I'll add the environment variables in the template.

Trying to get this to work with reverse proxy. Currently using NPM.

 

When I create a share link, the link is correct with my domain. But when I navigate to that link all I get in return is a blank page. After a little bit the browser returns "This site can't be reached". Navigating to the shared link with local IP address results in it working just fine.

 

Photoprism is complaining about websockets not working. I've input their config in the proper place in NPM but it causes the proxy host to go offline. Does anyone have a working config for NPM? I am also looking at Traefik which was mentioned in photoprism's documentation.

 

EDIT: I had websockets disabled in NPM. When I enabled it the proxy host went offline. I removed all the extra config from the advanced tab and re-enabled websockets and now that is correctly working. As for the blank page/page not loading issue, I had the docker form incorrectly configured. In the "PHOTOPRISM_SITE_URL" field the site url needs to exclude the port number. With those changes I am no longer experiencing any issues or warnings.

Edited August 26, 20241 yr by offroadguy56

On 8/13/2024 at 9:58 AM, JEZBRO said:

I've managed to get the program running with the mailer configured correctly and reached the login screen. When I enter the email address specified in AFFiNE_ADMIN_EMAIL, I receive an email with a link to create an account instead of logging in. Also, when I click the link, it opens a new browser tab with the URL http://localhost:3010/magic-link..., and I encounter the following error in the logs: 

 

[Nest] 1  - 08/13/2024, 4:29:17 PM   ERROR [HTTP] Internal server error
PrismaClientKnownRequestError: 
Invalid `prisma.user.create()` invocation:


An operation failed because it depends on one or more records that were required but not found. No 'Feature' record(s) (needed to inline the relation on 'UserFeature' record(s)) was found for a nested connect on one-to-many relation 'FeatureToUserFeature'.
    at _n.handleRequestError (/app/node_modules/@prisma/client/runtime/library.js:121:7749)
    at _n.handleAndLogRequestError (/app/node_modules/@prisma/client/runtime/library.js:121:7057)
    at _n.request (/app/node_modules/@prisma/client/runtime/library.js:121:6741)
    at async l (/app/node_modules/@prisma/client/runtime/library.js:130:9355)
    at async AuthController.magicLinkSignIn (file:///app/dist/core/auth/controller.js:102:22)

 

For those interested in how I got the mailer working, here’s what I did:

Edited the Docker container and added the following four variables:

 

Name: AFFiNE_MAILER_HOST

Key: MAILER_HOST

Value: [Your Email SMTP Server]

 

Name: AFFiNE_MAILER_PORT

Key: MAILER_PORT

Value: [Your SMTP Port]

 

Name: AFFiNE_MAILER_USER

Key: MAILER_USER

Value: [Your Email Address]

 

Name: AFFiNE_MAILER_PASSWORD

Key: MAILER_PASSWORD

Value: [Your Email Password]

 

This setup allows the mailer to function correctly, sending emails as expected.

You may need to setup an App Password if you're using outlook or Gmail.

 

 

For me is not working! 

 

 

Hi, I have two instances of Photoprism running (one for me, one for my mom) and it was running fine for a long time but now that I started uploading more pictures, the previews or sidecar images (not sure at this point) are showing up as missing. All the previews start appearing with a broken image file - although the original image is still untouched. I ran a complete rescan on one library and it seemed like it fixed it but once I ran it on the other one, the first library started having the broken previews again. So far I think I have everything separated from each other from what I can tell but I may be wrong. Should I have had a separate path for PHOTOPRISM_ORIGINALS_PATH for the two instances? 

I believe the variable PHOTOPRISM_ORIGINALS_PATH is set with the docker path: Storage Path /photoprism/originals.

 

I don't even have the sidecar variable set in my template, nor the backup path but that shouldn't make a difference. Are there any errors? Is your storage filling up or server hitting load limits? What database are you using for the containers?

 

As far as I can tell you have photoprism set correctly as separate docker instances in /mnt/cache/appdata and the photos etc should be separated. Unless i'm missing something i'd say it was bad timing that running a scan was fixing/breaking the other docker unless it was affecting the server. You can keep testing and try stopping one container to see how long the previews stay there and if it actually is the second container affecting it.

 

The PhotoPrism docs show this:
 

Regenerate Thumbnails

docker compose exec photoprism photoprism thumbs -f

On 7/10/2023 at 11:07 PM, Findthelorax said:

Support for findthelorax docker templates
Just learning but happy to help where I can.

Look at the documentation on Github!

Application Name: EMQX
Application Site: https://www.emqx.io/

Docker Hub: https://hub.docker.com/_/emqx
Github: https://github.com/emqx/emqx

 

Application Name: blisshq
Application Site: https://www.blisshq.com/

Docker Hub: https://hub.docker.com/r/romancin/bliss
Github: https://github.com/romancin/bliss-docker

 

Application Name: PhotoPrism
Application Site: https://www.photoprism.app/

Docker Hub: https://hub.docker.com/r/photoprism/photoprism
Github: https://github.com/photoprism

Hiiii, about Affine.
I couldn't run it on docker unraid, it won't start. Any suggestions?

I am also having issues getting the login to work.  any progress?

I gave up trying to get the AFFiNE community app working and used the compose .yaml on the Affine Git Hub. I'll explain what I did below.

1. Create a Directory for Affine on Unraid

• Open the Unraid terminal.
• Create a directory for Affine in Unraid’s appdata folder

mkdir -p /mnt/user/appdata/affine-selfhost

 

2. Create the docker-compose.yaml File

• In the /mnt/user/appdata/affine-selfhost directory, create a file named docker-compose.yaml
• Add the contents from the GitHub example into this file, with a few modifications for Unraid file paths.

services:
  affine:
    image: ghcr.io/toeverything/affine-graphql:stable
    container_name: affine_selfhosted
    command:
      ['sh', '-c', 'node ./scripts/self-host-predeploy && node ./dist/index.js']
    ports:
      - '3010:3010'
      - '5555:5555'
    depends_on:
      redis:
        condition: service_healthy
      postgres:
        condition: service_healthy
    volumes:
      # custom configurations
      - /mnt/user/appdata/affine-selfhost/config:/root/.affine/config
      # blob storage
      - /mnt/user/appdata/affine-selfhost/storage:/root/.affine/storage
    logging:
      driver: 'json-file'
      options:
        max-size: '1000m'
    restart: unless-stopped
    environment:
      - NODE_OPTIONS="--import=./scripts/register.js"
      - AFFINE_CONFIG_PATH=/root/.affine/config
      - REDIS_SERVER_HOST=redis
      - DATABASE_URL=postgres://affine:affine@postgres:5432/affine
      - NODE_ENV=production
      - AFFINE_ADMIN_EMAIL=${AFFINE_ADMIN_EMAIL}
      - AFFINE_ADMIN_PASSWORD=${AFFINE_ADMIN_PASSWORD}
      # Uncomment next line if you wish to quit telemetry.
      # - TELEMETRY_ENABLE=false
  
  redis:
    image: redis
    container_name: affine_redis
    restart: unless-stopped
    volumes:
      - /mnt/user/appdata/affine-selfhost/redis:/data
    healthcheck:
      test: ['CMD', 'redis-cli', '--raw', 'incr', 'ping']
      interval: 10s
      timeout: 5s
      retries: 5
  
  postgres:
    image: postgres
    container_name: affine_postgres
    restart: unless-stopped
    volumes:
      - /mnt/user/appdata/affine-selfhost/postgres:/var/lib/postgresql/data
    healthcheck:
      test: ['CMD-SHELL', 'pg_isready -U affine']
      interval: 10s
      timeout: 5s
      retries: 5
    environment:
      POSTGRES_USER: affine
      POSTGRES_PASSWORD: affine
      POSTGRES_DB: affine
      PGDATA: /var/lib/postgresql/data/pgdata

 

3. Set Up Environment Variables

• You can create a .env file in /mnt/user/appdata/affine-selfhost/config to store your environment variables, like AFFINE_ADMIN_EMAIL and AFFINE_ADMIN_PASSWORD.
• To do this navigate to the directory

cd /mnt/user/appdata/affine-selfhost/config

• Create the .env file

nano .env

• Add variables

AFFINE_ADMIN_EMAIL=
AFFINE_ADMIN_PASSWORD=

# Server configurations
AFFINE_SERVER_HOST=your_server_host          # Replace with your actual server host (e.g., 0.0.0.0)
AFFINE_SERVER_PORT=3010                      # Replace with your desired server port
AFFINE_SERVER_HTTPS=false                    # Set to true if using HTTPS, otherwise false
AFFINE_SERVER_EXTERNAL_URL=                  # Replace with the external URL, e.g., http://yourdomain.com

# Mailer configurations
MAILER_HOST=smtp.yourmailhost.com            # Replace with your mail host (e.g., smtp.gmail.com)
MAILER_PORT=                                 # Mail server port (e.g., 587 for SMTP with TLS)
MAILER_USER=your_mailer_user                 # Replace with your mailer username (e.g., your email)
MAILER_PASSWORD=your_mailer_password         # Replace with your mailer password
MAILER_SENDER="Affine Admin <your_email>"    # Replace with the email sender's name and email

• After entering the environment variables, press CTRL + X to exit
• Press Y to confirm saving the changes.
• Press Enter to save the file with the name .env

 

4. Deploy Affine Using Docker Compose

• Navigate to the directory where the docker-compose.yaml file is located

cd /mnt/user/appdata/affine-selfhost

• Run the following command to start Affine

docker-compose up -d

 

5. Access Affine

• Once everything is up and running, open your browser and go to http://your-unraid-ip:3010
• You should now be able to access Affine

Agreed, I updated and now I can't get to the WebUI. No errors, logs says it should be accessible but it just isn't. My docker compose works though. I may remove the template next week if I don't make any progress.

I am struggling with access to the photoprism webui. It was working previously, but I'm now unable to connect at all and getting nothing in the logs. I have removed and reinstalled the image as I may have messed things switching between bridge/host modes (as described above), but still not able to access. Any help or suggestions would be much appreciated.

 

 

Edited November 8, 20241 yr by fghjgchjrt

3 hours ago, fghjgchjrt said:

I am struggling with access to the photoprism webui. It was working previously, but I'm now unable to connect at all and getting nothing in the logs. I have removed and reinstalled the image as I may have messed things switching between bridge/host modes (as described above), but still not able to access. Any help or suggestions would be much appreciated.

 

 

As my opinion, some times it takes a while to load, just wait, your log missing

"Loaded"

If you're using HDD with a lot of items It can take +3h to load

6 hours ago, Artiom97es said:

As my opinion, some times it takes a while to load, just wait, your log missing

"Loaded"

If you're using HDD with a lot of items It can take +3h to load

Oh dear, sorry yes you're absolutely right it just took several hours. Thanks and apologies!

Any news regarding the Affine template? I see it is still available in the Apps tab, but was reading this thread and seeing there were issues later last year. I just discovered Affine and was wondering about self hosting it.

I would recommend running the affine docker compose stack. I really haven't had any time to dive into this. Last time I checked the stack was working.

Affine is working for me with a couple changes:

• NODE_OPTIONS: --import=./scripts/register.js 
• Post Arguments: sh -c 'node ./scripts/self-host-predeploy && node ./dist/index.js'

12 hours ago, FestiveKyle said:

Affine is working for me with a couple changes:

• NODE_OPTIONS: --import=./scripts/register.js 
• Post Arguments: sh -c 'node ./scripts/self-host-predeploy && node ./dist/index.js'

Great timing! I just set up this up using the community templates and was having issues registering my admin user. The above two changes worked.