Mihle

Members
  • Posts

    152
  • Joined

  • Last visited

Converted

  • Gender
    Male
  • URL
    https://www.flickr.com/people/145257438@N02/
  • Location
    Norway

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Mihle's Achievements

Apprentice

Apprentice (3/14)

0

Reputation

  1. If I currently have a basic licence, will I be able to upgrade to a plus, after the change has happened, or would I be forced to stay on basic/upgrade all the way to pro?
  2. So I did this with Nextcloud (Linuxserver) /tmp (not SWAG) a while ago by remapping it to a folder inside Nextclouds own Appdata folder. It worked fine at the time. But after a container/Nextcloud(v28) update, I started having issues with the photos app/viewing photos in Nextcloud making Nextcloud stop responding with few logs until I restarted my NAS, and then the docker service had to be turned on again manually. After a lot of testing I figured out removing the path remapping, fixed the freezing/stop responding issue. But Now I am back to /tmp being in the docker image. Anyone have heard about this before and know how to fix it or work around it? What about remapping a folder could cause problems with Nextcloud?
  3. So a question, I am on unraid 6.12 and didnt update to the new one yet because I didnt get around to it, but I am having problems and want to roll back appdata. Will the old version still work, even if it is not supported anymore?
  4. I am no longer getting that warning, but nextcloud stops responding every time the photo app in nextcloud tries to generate previews of photos. Nothing helps exept restaring the whole NAS. I have tried to find logs about it everywhere, nextcloud.log, docker.log, other logs, unraid syslog but there is zero logs that tells me anything about what is going on. At this point I think my only option is to try to roll back to an earlier appdata version.
  5. The last while I have gotten this error now and then: Allowed memory size of 536870912 bytes exhausted (tried to allocate 608580088 bytes) at /app/www/public/lib/private/Files/Storage/Local.php#327 How do I fix that? How do I increase that limit to something higher? How do I find the file in the path the error mentions, I have tried looking for it it in Appdata but I havent found it yet. it is somewhere else?
  6. After another update, its indeed fixed itself.
  7. I just had an issue where Jellyfin on custom network would not start with error that port was already in use, after a lot of trying different things, I figured out that it was conflicting with itself. This started after some update. In the configuration, it had both a field named "Webui - HTTPS:" and one named "WebUI (HTTPS) [optional]:" that was both set to 8920. I changed the last one to something else and it then started up fine. Is this an issue with that its an older docker that has been updated as its basically the same name, or is it an issue with the docker itself? EDIT: I just noticed my Docker is not the linuxserver one, opsie.
  8. I just updated (27.0.1, latest docker image I think), and I am getting the same errors, should I delete them manually or do something else or just wait?
  9. Same, only required to do ot with nginx.conf tho, not ssl.conf. For reference for other people, is is how the warning looks like in Swag log: I shut swag down and replaced the .sample with .conf and its working again
  10. I only did the ngnx.conf and it worked, did not touch ssl.conf, and it worked. Thanks!
  11. I figured it out, its not an issue with MariaDB at all. The issue is with SWAG. 1. Stop SWAG docker (dont know if this is required, but seems like a good practice to do?) 2. Go in to appdata/swag/nginx 3. Rename the nginx.conf like for example add .old (so you still have it, just in case) 4. Rename the nginx.conf.sample to just nginx.conf 5. Start SWAG docker 6. Profit. EDIT: Found this thread after the fact right now:
  12. Maybe stupid question, but where is $LOGFILE, how do you view it? (Krusader?) EDIT: I see its mentioned it is in /tmp but the /tmp I am looking in, doesnt have it, maybe there is multiple ones and I looked in the wrong one?
  13. My mistake, the command is what you say there, it was an error by copying it over. But yes, it is encrypted. $DEVICE do work for unmount tho so weird it doesnt for spindown, while using sde works? When using sde, it does say dev/sde and not /dev/mapper/mountpoint? Even tho its supposed to be an encrypted disk? EDIT: $LUKS works for spin down, Why is it better to use disk alias?