[Bug]: Note could not be be created. Please try again.

[peaklabs-dev]

I am finishing your template for Coolify and I keep getting this error:

Note could not be created.
Please try again.

Could you please deploy your service using the docker compose empty deploy type and fix this error. I believe this error is not related to Coollify, if it is please let me know what the problem is (maybe volume mounts?) and I will fix it.

Compose file:

# documentation: https://github.com/cupcakearmy/cryptgeon
# slogan: Secure note / file sharing service inspired by PrivNote.
# tags: cryptgeon, secure, note, sharing, privnote, file, sharing
# logo: svgs/cryptgeon.png
# port: 8000

services:
  app:
    image: cupcakearmy/cryptgeon:latest
    environment:
      - SERVICE_FQDN_CRYPTGEON_8000
      - SIZE_LIMIT=${SIZE_LIMIT:-4 MiB}
      - MAX_VIEWS=${MAX_VIEWS:-100}
      - MAX_EXPIRATION=${MAX_EXPIRATION:-360}
      - ALLOW_ADVANCED=${ALLOW_ADVANCED:-true}
      - ALLOW_FILES=${ALLOW_FILES:-true}
    depends_on:
      redis:
        condition: service_healthy
    healthcheck:
      test:
        - CMD
        - curl
        - "--fail"
        - "http://127.0.0.1:8000/api/live/"
      interval: 1m
      timeout: 3s
      retries: 2
      start_period: 5s

  redis:
    image: redis:7-alpine
    command: "redis-server --maxmemory 200mb --maxmemory-policy allkeys-lru"
    healthcheck:
      test:
        - CMD
        - redis-cli
        - PING
      interval: 5s
      timeout: 10s
      retries: 2

[cupcakearmy]

Hey, thanks for taking care and being proactive!

I just tested it on an empty project, and for me if I just pase the compose file (projects -> myproject -> new -> Docker Based -> Docker Compose) and deploy without changing anything it works.

Are you testing locally? because https:// is required, so depending on your local setup it might not work for that reason. I tested on a live domain with valid certificates and works.

Any other way I can help?

[peaklabs-dev]

Thanks for the quick reply. Yes, I develop and test locally. If https is required then we know the cause as https on local dev is kind of a pain I use http. I will enable the template then. You can track the release via this PR.