Can not loggin in self host about hemmelig.app

[bjarneo]

@obito26m did you migrate from redis to sqlite? Meaning, did you transfer the data. There is no process doing this automatically for you, which means you either have to create a migrator from redis to the sqlite instance, or you have to start from scratch.

[obito26m]

I was first on redis but when I wanted to encrypt a file today I had to log in which did not work so I thought you do it all over again so I deleted the container the folders and so on and then recreated the container with the command from above but still the same can gladly give logs from portainer with

edit log datei hemmelig_logs.txt

[bjarneo]

@obito26m

Can you try this command instead? Seems to be missing the docker tag.

docker run -p 3510:3000 -d --name=hemmelig \
   -v /volume1/docker/hemmelig/uploads:/var/tmp/hemmelig/upload/files \
   -v /volume1/docker/hemmelig/db:/home/node/hemmelig/database/ \
   hemmeligapp/hemmelig:v5.3.0

EDIT: I do remember now that if no tag is added, it will use the latest, and the latest is the latest tag

[obito26m]

@bjarneo

ok i am testing it it is downloading now

edit also not still this 6 green bars and further does not happen

[obito26m]

can it be because I put everything behind synology proxy to access it with a domain that goes through port 443 to give only 443 and 80 free in the router ?

[bjarneo]

Have you tried it on localhost on your computer?

[obito26m]

unfortunately I can not test because I have a mac with apple cpu and there is the last 4.4.0

[obito26m]

with arm 4.4.0 nothing happens when creating an account or login

[bjarneo]

You are correct. It will not work on the apple cpu. I forgot we are not building the ARM images anymore due to a prisma bug we have to solve, but it should still be working on linux servers. Have tested it by running this command:

For the Hemmelig.app instance, this is how the docker container is started using ansible, which is not really huge difference if we look at what you are doing, except of the env vars, of course:

      - name: Start the Hemmelig.app container
        docker_container:
            name: hemmelig
            image: '{{hemmelig_docker_image}}'
            env:
                SECRET_MASTER_KEY: '{{SECRET_MASTER_KEY}}'
                SECRET_JWT_SECRET: '{{SECRET_JWT_SECRET}}'
                SECRET_ROOT_USER: 'groot'
                SECRET_ROOT_PASSWORD: '{{SECRET_ROOT_PASSWORD}}'
                SECRET_ROOT_EMAIL: '[email protected]'
                SECRET_MAX_TEXT_SIZE: '20048'
                SECRET_HOST: 'hemmelig.app'
            ports:
                - '3000:3000'
            volumes:
                - '/home/hemmelig/userdata/:/var/tmp/hemmelig/upload/files'
                - '/home/hemmelig/database/:/home/node/hemmelig/database/'
            restart_policy: always
        tags: hemmelig

with arm 4.4.0 nothing happens when creating an account or login

Yeah, version < 5 uses redis, so that is why, and from version 5 we do not have an ARM version of the docker image.

[obito26m]

ok because it may be I had already talked before ? and when the 5 version came is vllt my redit bent or so I test times the new code on synology

[obito26m]

ok still will not because I'll probably wait for new version have now adapted the code me one time withr direct connection so redit one time without so saw my code

docker run -d --name hemmelig
-p 3510:3000
-e SECRET_MASTER_KEY=key
-e SECRET_HOST=hemmelig.app
-e SECRET_ROOT_USER=admin
-e SECRET_ROOT_PASSWORD=password
-e SECRET_ROOT_EMAIL=mai
-e SECRET_MAX_TEXT_SIZE=20048
-e SECRET_FORCED_LANGUAGE=de
-v /volume1/docker/hem/up:/var/tmp/hemmelig/upload/files
-v /volume1/docker/hem/db:/home/node/hemmelig/database
hemmeligapp/hemmelig

[bjarneo]

@obito26m can you show me the logs when you try to start v5.4.3?

[obito26m]

[email protected] start
prisma migrate deploy && node server.js

Environment variables loaded from .env
Prisma schema loaded from prisma/schema.prisma
Datasource "db": SQLite database "hemmelig.db" at "file:../database/hemmelig.db"

SQLite database hemmelig.db created at file:../database/hemmelig.db

9 migrations found in prisma/migrations

Applying migration 20230403094651_init
Applying migration 20230403105353_init
Applying migration 20230405075854_usergenerated
Applying migration 20230405082548_userrole
Applying migration 20230406072002_settings
Applying migration 20230406095057_readonly
Applying migration 20230409114406_disablefileupload
Applying migration 20230409162446_cascadedelete
Applying migration 20230411070916_disable_account_creation

The following migrations have been applied:

migrations/
└─ 20230403094651_init/
└─ migration.sql
└─ 20230403105353_init/
└─ migration.sql
└─ 20230405075854_usergenerated/
└─ migration.sql
└─ 20230405082548_userrole/
└─ migration.sql
└─ 20230406072002_settings/
└─ migration.sql
└─ 20230406095057_readonly/
└─ migration.sql
└─ 20230409114406_disablefileupload/
└─ migration.sql
└─ 20230409162446_cascadedelete/
└─ migration.sql
└─ 20230411070916_disable_account_creation/
└─ migration.sql

All migrations have been successfully applied.
55249/01/09 04:28PM 30 undefined | pid=19 hostname=testhemm msg=Server listening at http://0.0.0.0:3511
(node:19) NOTE: We are formalizing our plans to enter AWS SDK for JavaScript (v2) into maintenance mode in 2023.

Please migrate your code to use AWS SDK for JavaScript (v3).
For more information, check the migration guide at https://a.co/7PzMCcy
(Use node --trace-warnings ... to show where the warning was created)
55249/01/09 09:12PM 30 undefined | pid=19 hostname=testhemm reqId=req-1 req=[object Object] msg=incoming request
(node:19) [FSTDEP012] FastifyDeprecation: Request#context property access is deprecated. Please use "Request#routeConfig" or "Request#routeSchema" instead for accessing Route settings. The "Request#context" will be removed in fastify@5.
55249/01/09 09:13PM 30 undefined | pid=19 hostname=testhemm reqId=req-1 res=[object Object] responseTime=76.94451904296875 msg=request completed
55249/01/10 05:46AM 30 undefined | pid=19 hostname=testhemm reqId=req-2 req=[object Object] msg=incoming request
55249/01/10 05:47AM 30 undefined | pid=19 hostname=testhemm reqId=req-2 res=[object Object] responseTime=3.931118965148926 msg=request completed
55249/01/10 02:15PM 30 undefined | pid=19 hostname=testhemm reqId=req-3 req=[object Object] msg=incoming request

that comes with me at 5.4.3 therefore I have my horn container first time on 4.0.0 there I can log in and use everything

[bjarneo]

Hm, should be no issues here. Did you try to sign in with the SECRET_ROOT_USER?

[obito26m]

yes sure have both tried to create a new so and with admin acc login so I do not understand that that's why I just use the 4 version there is still everything no idea where ran is whether on synology or firewall or rervers proxy

[bjarneo]

To be honest, I really do not know what happens at your end. Do you have the correct read and write permissions set for the database volume?

[ccarpo]

Good Morning. I have a similar issue.
I also selfhost but on debian. I use 5.8.2 with nginx-proxy-manager as an reverse proxy before. I had to disable "Cache Assets" in the nginx-proxy-manager already to be able to access the site (else he couldn't load the assets and broke with a 404)

This is the log from the application after I login:

hemmelig_1  | {"level":30,"time":1682403954295,"pid":19,"hostname":"hemmelig","reqId":"req-5x","req":{"method":"GET","url":"/api/account/","hostname":"hemmelig.mydomain.net","remoteAddress":"172.22.0.1","remotePort":40368},"msg":"incoming request"}
hemmelig_1  | {"level":30,"time":1682403954296,"pid":19,"hostname":"hemmelig","reqId":"req-5x","res":{"statusCode":401},"responseTime":0.6597371101379395,"msg":"request completed"}

and in my browser it also says 401 not authorized

This is my dockercompose:

services:
    hemmelig:
        image: hemmeligapp/hemmelig:v5.8.2 # Check the tags for what version to use
        hostname: hemmelig
        init: true
        volumes:
            - /media/xyz/hemmelig/files:/var/tmp/hemmelig/upload/files
            - /media/xyzhemmelig/database/:/home/node/hemmelig/database/
        environment:
            - SECRET_LOCAL_HOSTNAME=0.0.0.0 # The local hostname for the fastify instance
            - SECRET_PORT=3232 # The port number for the fastify instance
            - SECRET_HOST=<a password i chose> # Used for i.e. set cors/cookies to your domain name
            - SECRET_ROOT_USER=ccarpo # User as the root admin user
            - SECRET_ROOT_PASSWORD=<a password i chose>  # The admin user password (change this after signed in)
            - SECRET_ROOT_EMAIL=<[email protected]> # The email for the admin user
            - SECRET_FILE_SIZE=10 # Set the total allowed upload file size in mb
            - SECRET_FORCED_LANGUAGE=en # Set the default language for the application
            - SECRET_JWT_SECRET=<a password i chose> # Override this for the secret signin JWT tokens for log in
            - SECRET_MAX_TEXT_SIZE=256 # The max text size for the secret. Is set in kb. i.e. 256 for 256kb
        ports:
            - '3232:3232'
        restart: always
        stop_grace_period: 1m
        healthcheck:
            test: 'wget -O /dev/null localhost:3000 || exit 1'
            timeout: 5s
            retries: 1

Maybe this helps speculating.

[bjarneo]

Hello,

Here is an issue where many of things has been discussed: #183

Maybe this is your issue as well? As SECRET_HOST has to be your domain name. #183 (comment)

As for the "statusCode":401 it means you did not have the correct user/password.

[ccarpo]

Thank you. That solved it for me. I misinterpreted the variable description. 25.04.2023 09:28:21 bjarneo ***@***.***>:

…

Hello, Here is an issue where many of things has been discussed: #183[#183] Maybe this is your issue as well? As *SECRET_HOST* has to be your domain name. #183 (comment)[#183 (comment)] — Reply to this email directly, view it on GitHub[#178 (comment)], or unsubscribe[https://github.com/notifications/unsubscribe-auth/AACCWPEMOU7IGGLGAGLMSIDXC54JJANCNFSM6AAAAAAWZJLP4Q]. You are receiving this because you commented.[Verfolgungsbild][https://github.com/notifications/beacon/AACCWPDUDWXMNIK5XJD2EHDXC54JJA5CNFSM6AAAAAAWZJLP4SWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTS2VTZ7W.gif]

[bjarneo]

I see. Then I should write a better description. Glad it solved it :)