Near

Members
  • Posts

    10
  • Joined

  • Last visited

Recent Profile Visitors

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

Near's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Thanks for the link. It really looks like it's due to the Sonoma update. I just connected via another device (iPhone) and everything worked fine. Hopefully Apple will take care of it, it's really annoying.
  2. I have noticed that I cannot display most of the images on my Unraid shares correctly. When accessing the share via network connection on my MacBook, the images are displayed correctly in the preview (screenshot 1). However, when I double-click on the image to view it large, the images are only partially displayed (screenshot 2) or corrupted (screenshot 3). However, the files are fine, because when I copy them from the server to the Mac, they are displayed correctly again. Does anyone have an idea why this is happening and what I can do about it? I'm currently on Version 6.12.4 but had the same issue on 6.9.2 which I used before.
  3. Update: I got help from support to replace the key. Everything is currently running again, I'll let you know if the problem occurs again. Thanks for the help so far.
  4. Thanks again for the quick reply. I have replaced the USB flash drive. I had to generate a new registration key for this. I did that, but unfortunately I did not receive an e-mail with the key even after more than a day, not even in the spam folder. Is there another way to get the key file URL?
  5. Oh sure, sorry! Here are the diagnostic files. aldnoah-diagnostics-20231117-1015.zip
  6. A few minutes after my reply, the error unfortunately occurs again. You can see what I mean in my previous post on the screenshot. The cache drive is no longer displayed, but the USB stick is. The error appears exactly as described in the first post. I will replace the USB stick anyway, just want to make sure that the problem is not actually with the cache.
  7. Thanks for the quick reply! I have plugged the USB stick into a different port and the problem is solved for now after rebooting. However, I am still surprised that my cache drive (NVME) was no longer visible in the dashboard – before rebooting. Isn't this also referred to as flash drive? Or does this have nothing to do with the problem?
  8. Hi everyone, This is the second time I have received the message "Fatal Flash Drive Error". The first time I did a reboot, which didn't work, so I disconnected the system from the power supply and started it manually. After that, everything worked fine again. Now I'm getting this message again. The server is currently still running and Plex, for example, is still working. However, I can no longer connect via my MacBook, presumably because the shares are using my NVME as a cache. The NVME is also no longer displayed in the dashboard since the error. Please find attached a screenshot of the error message and the diagnostic files. If you need anything else, please let me know. Any and all help would be greatly appreciated. Thank you! aldnoah-diagnostics-20231114-1320.zip
  9. I am trying to connect SWAG to a domain via cloudflare. I get the following error message in the logs of SWAG. As email I have entered the address with which I log in to cloudflare and as key the Global API Key from cloudflare. Am I doing something wrong? How can I find out where the error is? Thanks! Here is an extract from the logs: Mar 23 15:30:45 Aldnoah nginx: 2022/03/23 15:30:45 [error] 2323#2323: *868944 connect() to unix:/var/tmp/swag.sock failed (111: Connection refused) while connecting to upstream, client: 192.168.178.22, server: , request: "GET /dockerterminal/swag/token HTTP/1.1", upstream: "http://unix:/var/tmp/swag.sock:/token", host: "192.168.178.47", referrer: "http://192.168.178.47/dockerterminal/swag/" Mar 23 15:30:45 Aldnoah nginx: 2022/03/23 15:30:45 [error] 2323#2323: *869155 connect() to unix:/var/tmp/swag.sock failed (111: Connection refused) while connecting to upstream, client: 192.168.178.22, server: , request: "GET /dockerterminal/swag/ws HTTP/1.1", upstream: "http://unix:/var/tmp/swag.sock:/ws", host: "192.168.178.47" Mar 23 15:30:45 Aldnoah nginx: 2022/03/23 15:30:45 [error] 2323#2323: *868944 connect() to unix:/var/tmp/swag.sock failed (111: Connection refused) while connecting to upstream, client: 192.168.178.22, server: , request: "GET /dockerterminal/swag/token HTTP/1.1", upstream: "http://unix:/var/tmp/swag.sock:/token", host: "192.168.178.47", referrer: "http://192.168.178.47/dockerterminal/swag/" Mar 23 15:30:45 Aldnoah nginx: 2022/03/23 15:30:45 [error] 2323#2323: *869158 connect() to unix:/var/tmp/swag.sock failed (111: Connection refused) while connecting to upstream, client: 192.168.178.22, server: , request: "GET /dockerterminal/swag/ws HTTP/1.1", upstream: "http://unix:/var/tmp/swag.sock:/ws", host: "192.168.178.47" Mar 23 15:30:46 Aldnoah nginx: 2022/03/23 15:30:46 [error] 2323#2323: *868944 connect() to unix:/var/tmp/swag.sock failed (111: Connection refused) while connecting to upstream, client: 192.168.178.22, server: , request: "GET /dockerterminal/swag/token HTTP/1.1", upstream: "http://unix:/var/tmp/swag.sock:/token", host: "192.168.178.47", referrer: "http://192.168.178.47/dockerterminal/swag/" Mar 23 15:30:46 Aldnoah nginx: 2022/03/23 15:30:46 [error] 2323#2323: *869161 connect() to unix:/var/tmp/swag.sock failed (111: Connection refused) while connecting to upstream, client: 192.168.178.22, server: , request: "GET /dockerterminal/swag/ws HTTP/1.1", upstream: "http://unix:/var/tmp/swag.sock:/ws", host: "192.168.178.47" Mar 23 15:30:47 Aldnoah nginx: 2022/03/23 15:30:47 [error] 2323#2323: *868944 connect() to unix:/var/tmp/swag.sock failed (111: Connection refused) while connecting to upstream, client: 192.168.178.22, server: , request: "GET /dockerterminal/swag/token HTTP/1.1", upstream: "http://unix:/var/tmp/swag.sock:/token", host: "192.168.178.47", referrer: "http://192.168.178.47/dockerterminal/swag/" Mar 23 15:30:47 Aldnoah nginx: 2022/03/23 15:30:47 [error] 2323#2323: *869165 connect() to unix:/var/tmp/swag.sock failed (111: Connection refused) while connecting to upstream, client: 192.168.178.22, server: , request: "GET /dockerterminal/swag/ws HTTP/1.1", upstream: "http://unix:/var/tmp/swag.sock:/ws", host: "192.168.178.47"
  10. Hey! I am new to Unraid and accordingly to nextcloud. I have been trying to install nextcloud (linuxsserverio) on my Unraid server. Along with MariaDB and I followed exactly the steps in Space Invader One's video. Up to the point 9:14 (https://youtu.be/id4GcVZ5qBA?t=554). But as soon as I try to log in again the next day to continue with the setup I get the error "Wrong username or password". I have checked the data several times and also completely rebuilt nextcloud & MariaDB (including cache clean). However, I keep getting the same error. Also resetting the password via terminal as mentioned in your documentation does not work. Screenshots attached. What can I do to get nextcloud to work? Thank you!