scissabob

Members
  • Posts

    8
  • Joined

  • Last visited

scissabob's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Hi, i can't get cryptpad running. After solving the permission rights and solving the problem, that the config was created as a folder, I still can't get on the webif. I can see this in the log > [email protected] start > node server.js nothing more is happening edit: i also added this to the config, didn't help (this is the ip of the container( httpUnsafeOrigin: 'http://192.168.178.8:3000', The container is running, but webif not accessible Is there someone, who got it working?
  2. Thanks, i will read into it tomorrow. But yes, when I edit it over the webif, i can only see the example config with all the # in front, so I guess, that the real config is somewhere else... if i look at the config without hitting the edit button, i can see the real config. edit: I got it... so you have to delete the #'s in the configfile for the lines which shows an error. Then you can add the shares in the config file and save it. After rebooting it takes some time, because of scanning your shares (you can see the status in the logs). When the scanning is done, everything works fine.
  3. Thanks, i will read into it tomorrow. But yes, when I edit it over the webif, i can only see the example config with all the # in front, so I guess, that the real config is somewhere else... if i look at the config without hitting the edit button, i can see the real config.
  4. Hi there, first, thanks for the slskd container! It is up and running. i was able to mount my NAS in it as download target. Unfortunately, I cannot get the share to work. The config is like this: directories: incomplete: /app/incomplete downloads: /app/downloads shares: directories: [] I cannot add my shares here... Even if I set the remote configuration to "true" it is not working to edit the config-file. Any Ideas?
  5. thank you so much, i love this forum... even if i don't find the specific things, i always find ways to my goal. in this case the "find -inum" command pointed me to this file: /tmp/pkg/538087d6d87660382fef5ac4ab400402587f3f1d97e2d97cd5cc502f37c11e01/@vmngr/libvirt/build/Release/obj.target/virt/src/hypervisor-node.o that's how i found out that my libvirt.img was corrupted. After deleting it and renew it my issue was gone. unfortunately my vm is now gone too, but that's ok. at least the issue with "BTRFS warning" is solved! thanks again!
  6. thanks, I will try tomorrow! have a nice evening and thanks again for your help, edit: it's working now 😊
  7. Hi, I'm Marco and I'm new here Maybe somebody can help me. I created a Stack with 4 Containers... everything is running fine. But when I try to backup everything, I got this message: [21.12.2023 10:32:42][❌][teslalogger-webserver-1] tar verification failed! Tar said: tar: Removing leading `/' from member names; mnt/user/appdata/TeslaLogger/TeslaLogger/bin/nohup.out: Mod time differs; mnt/user/appdata/TeslaLogger/TeslaLogger/bin/nohup.out: Size differs Does anybody know, what I can do to fix this? thx in advance