First of all, hey there, liking your project!
I have been trying to install it via docker/portainer on my Synology NAS.
However whenever i connect there is no Serverpic to click on to redeem my Admin privileges, and this shows up in my logs.
TypeError: Cannot read properties of undefined (reading 'token')
at Socket.<anonymous> ( removed link )
at Socket.emit (node:events:519:28)
at Socket.emitUntyped ( removed link )
at removed link
at process.processTicksAndRejections (node:internal/process/task_queues:77:11)
[Error: ENOENT: no such file or directory, open './config_backups/config_6/27/2024_4-41-56 PM.txt'] {
errno: -2,
code: 'ENOENT',
syscall: 'open',
path: './config_backups/config_6/27/2024_4-41-56 PM.txt'
}
[2024-6-27 16:41:56]
[2024-6-27 16:41:56]
[2024-6-27 16:41:56] UNEXPECTED ERROR
[2024-6-27 16:41:56]
[2024-6-27 16:41:56] Cannot read properties of undefined (reading 'token')
In my docker compose i even gave dcts its own directory, but there are no files in it. Unsure what i am doing wrong.
First of all, hey there, liking your project!
I have been trying to install it via docker/portainer on my Synology NAS.
However whenever i connect there is no Serverpic to click on to redeem my Admin privileges, and this shows up in my logs.
TypeError: Cannot read properties of undefined (reading 'token')
at Socket.<anonymous> ( removed link )
at Socket.emit (node:events:519:28)
at Socket.emitUntyped ( removed link )
at removed link
at process.processTicksAndRejections (node:internal/process/task_queues:77:11)
[Error: ENOENT: no such file or directory, open './config_backups/config_6/27/2024_4-41-56 PM.txt'] {errno: -2,
code: 'ENOENT',
syscall: 'open',
path: './config_backups/config_6/27/2024_4-41-56 PM.txt'
}
[2024-6-27 16:41:56]
[2024-6-27 16:41:56]
[2024-6-27 16:41:56] UNEXPECTED ERROR
[2024-6-27 16:41:56]
[2024-6-27 16:41:56] Cannot read properties of undefined (reading 'token')In my docker compose i even gave dcts its own directory, but there are no files in it. Unsure what i am doing wrong.
Hi!
There were some issues related to docker to my knowledge. The way it would work with docker was changed. The release v2.6.6 had some accidental bugs and i think most of them have been caught. I didnt make a new release yet but you could straight up clone the repo to get these fixes.
Currently im re-organising the entire code so that these kind of bugs wont go unnoticed anymore.
I just testing it with a "fresh install" (without docker) and it worked so maybe it was a docker issue. Today the way to install it with docker was changed (as improvement) so maybe you need to install it again.
Small notice: when redeeming the role there seems to be a bug that the popup message after successfully redeeming a role is not closing. refreshing the page will remove it. its a small bug.
Please share this forum with your friends!
Let people know the software exists!
i would be very thankful <3
@dcts_8ynyz3lm Thanks for your quick response! I actually used that method today to install it via portainer, didnt quite work, i kept getting those errors, so maybe there is something wrong on my end, currently i am unable to pull new bcs of this error popping up.
failed to deploy a stack: dcts Pulling dcts Error Error response from daemon: Head " removed link ": denied
@itz_f3lix Support is very important ;D
i tested it and there was a small build error or something, anyway we fixed it and with the new way to install it it should hopefully work now.
Please share this forum with your friends!
Let people know the software exists!
i would be very thankful <3
I just repulled the image and sadly the Issue still persists.
@itz_f3lix hi so i just tried to use the docker commands on a machine where i never installed it before and it all worked and i was able to redeem the token too . Maybe its still saved locally somewhere and not fetching the latest version 🤷♂️
Please share this forum with your friends!
Let people know the software exists!
i would be very thankful <3
I have just setup docker+portainer on my actual PC to try it out, and yeah, it works, so the problem is on my end somewhere within my NAS config, thanks for your help tho, much appreciate it!