BreakfastPurrito

Members
  • Posts

    59
  • Joined

  • Last visited

Everything posted by BreakfastPurrito

  1. I deleted the image and reinstalled everything, and it works. So something must've been corrupted. Thanks!
  2. By recreate, do you mean plopping in a docker.img from a backup or is there a specific procedure?
  3. I made a bit of a booboo by creating a network that conflicts with others, causing Docker to crash when I start it. I need to: 1) remove the conflicting network without docker running OR 2) start docker without the containers How do I do that?
  4. Recently I upgraded to 6.12.6 from 6.11.1. Ever since then, I got crashes which after a bit of investigation were due to the macvlan bug introduced in 6.12.6. The first thing I tried was to remove the macvlan and create it again. However I am thwarted with the error 'gateway already in use'. I tried searching online or what that meant or how to solve it and got nowhere. (Sidenote: why is that error message so vague and unhelpful? A gateway is supposed to be used by multiple devices. It's a gateway. It has literally no other function than to serve multiple devices on a network.) People did suggest trying IPvlan instead, but I got the same error. I thought it might be a problem with Portainer, but I get the same error in command line. So today I decided I had enough and downgraded to 6.11.1 again. However, the problem hasn't gone away and I now also get the same error in 6.11.1, whereas before it used to run just fine. This is all very frustrating. Does anyone have a solution? I just want everything to work the way it did before.
  5. This has to be one of the all time most unhelpful conversations I've ever had.
  6. The error is not coming from any container, because I'm not interacting with any container. I'm trying to set up a macvlan. I haven't even gotten to the point where I attach it to a container yet.
  7. I'm not following you either. I just want to get everything back the way it was before the latest unraid update ruined it.
  8. But the problem is not with any specific container, its with getting macvlan up and running at all.
  9. I tried those settings, it doesn't help. I tried every combination of those settings. No dice. As for the error, this is all I get:
  10. Recently I upgraded to 6.12.6 from 6.11.1. Ever since then, I got crashes which after a bit of investigation were due to the macvlan bug introduced in 6.12.6. The first thing I tried was to remove the macvlan and create it again. However I am thwarted with the error 'gateway already in use'. I tried searching online or what that meant or how to solve it and got nowhere. (Sidenote: why is that error message so vague and unhelpful? A gateway is supposed to be used by multiple devices. It's a gateway. It has literally no other function than to serve multiple devices on a network.) People did suggest trying IPvlan instead, but I got the same error. I thought it might be a problem with Portainer, but I get the same error in command line. So today I decided I had enough and downgraded to 6.11.1 again. However, the problem hasn't gone away and I now also get the same error in 6.11.1, whereas before it used to run just fine. This is all very frustrating. Does anyone have a solution? I just want everything to work the way it did before.
  11. My server also started crashing after updating to 6.12.6. I use a macvlan for Pihole. I tried removing the macvlan and creating a new one, but now I'm getting the error "gateway already in use". Which is just the most useless error message. No shit the gateway is already in use. It's a gateway. But it's stopping me dead in my tracks. I get the same error message when I try to make an IPVlan. So now I have neither. I've been scouring the internet for the last few days trying to find a solution, but to no avail. Changing the setting described above doesn't help. I just want it to work the way it did before I updated.
  12. Sorry, I should have been more specific. In Transmission itself, using "set download location".
  13. Every time I want to change the download location outside of /downloads/ I get a 'permission denied (13)' error. I have tried resetting the permissions in unraid for user 99/100, and I have tried making a new user specifically for Transmission with explicit access to the folders I want to use. I still keep getting the error. What can I do to fix this?
  14. I've got NVME drives as a cache pool and I would like to benchmark them. I get the error: However I can't find any info on what changes I need to make?
  15. I tried it, and every time I start transmission, it changes `rpc-authentication-required` false back to true and asks for a password.
  16. I'm having a peculiar problem. I want to run transmission without a username and pass. If I remove the USER and PASS variables from the docker container, all my torrents disappear. As in, I just get an empty interface if I go to the Transmission web address. If I then put the USER and PASS back, my torrents reappear. This happens regardless of what user and pass I use. It also happens when I leave them both blank, or leave either blank. What am I doing wrong?
  17. I don't know if I'm in the right place, but I have a question about luckybackup. Is there a way to make it delete files first in a backup task instead of at the end of it? I keep running into the problem that my backup drive runs out of space. Both the backup drive and array are the same size, but it keeps overflowing because it only deletes files at the end of the task.
  18. I have no idea how to do that. Is there a tutorial somewhere?
  19. The thing is, I only have this problem with Transmission. Every other service I can connect to through my VPN.
  20. Is there a way to label these fans anything other than Fan X? I want to label them something like Case Fan, CPU Fan, etc.
  21. I would like to label these fans to something like CPU Fan, Case Fan, etc. How do I do that? I tried searching this forum but couldn't find anything.
  22. WHITELIST: 192.168.1.207,192.168.1.205,192.168.1.211,10.8.0.3 The first 3 work, the last one does not.