mwoods98

Members
  • Posts

    122
  • Joined

  • Last visited

Recent Profile Visitors

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

mwoods98's Achievements

Apprentice

Apprentice (3/14)

2

Reputation

  1. Thanks, I think I have seen a video on this. Thanks for you help, I'll shut down the VM's and get them moved tot he arrray then switch the locations. I see where it is for other stuff too. Thanks!!
  2. Just checked, that is a machine on the network that I did copy files from UR. I don't recall getting auth failures to llogin from that machine. But, its good to know. I'll reboot it in case its still trying to reach out to UR. Thanks
  3. I just noticed this FCP notification and just wanted to check on it. I don't have any SSH ports open to the server I also don't have this machine in the DMZ.. On Jul 18 there were 17 invalid login attempts. This could either be yourself attempting to login to your server (SSH / Telnet) with the wrong user or password, or you could be actively be the victim of hack attacks. A common cause of this would be placing your server within your routers DMZ, or improperly forwarding ports. This is a major issue and needs to be addressed IMMEDIATELY NOTE: Because this check is done against the logged entries in the syslog, the only way to clear it is to either increase the number of allowed invalid logins per day (if determined that it is not a hack attempt) or to reset your server. It is not recommended under any circumstance to ignore this error tower-diagnostics-20230730-1336.zip
  4. Yes, the idea would be to maybe run the VM's or move say plex meta manager to this new cache
  5. Hi there, I just added a new cache drive and wanted to know how I could have some of the app data or virtual machines use this new drive?
  6. UPDATE: After searching some more in the discord I came across a thread that said to delete the artemis folder. I did that and also added docker pull gotson/komga:1.x so that I'll stay at 1x and be more careful with my updates and its working.
  7. I too am looking for a way to get this back working. I started out in the Komga discord where the directions were to: I run Komga on unraid in a docker, so to update to 1.0 I just need to: 1) back up my config folder 2) change the port on the docker itself from 8080 to 25600 3) change my SWAG reverse proxy set up I have a back up of the config folder I changed the port numbers (I even edited the template in /boot/config/plugins/dockerMan/templates-user to make sure it is using port 25600) and I made sure I was updated to the latest version. Still no UI and here is the log file: As I mentioned, I still have the backup before I did anything so, I can replace any files. If anyone has any suggestions, please let me know. Thanks
  8. Hello, I am using Mullvad and I wanted to see if there was a way to find out what the name of the device that I'm using. I have added the configuration info my deluge profile and its working. Recently mullvad is doing this (https://mullvad.net/en/blog/2022/6/13/introducing-names-for-easier-device-management/) its naming connections like flying walrus etc I have ID'd all but two and one of them is this deluge docker. Is there any way to find the "device name" ?
  9. I'm also having an issue after updating this docker: I can't connect to the WebGUI and I had noticed a few times before that the web gui was getting disconnected. I removed the docker and, reinstalled it. Here is what's in the logs. Thanks in advance. deluge.txt
  10. Update: I did what was suggested, turned off docker, deleted the image restarted docker and reinstalled the images using the community apps way. (mostly followed Space Invaders guide he has on you tube) However it got down to containers that stated with 'Y' and seemed to get stuck. I'm going to let it run overnight but it doesn't appear to be moving. If it hasn't moved by the AM, any suggestions?
  11. Thanks, this looks easy enough but I want to make sure I take my time and re do this with off the docker images I have installed so I won't lose anything. Thanks for this.
  12. I was doing some regular updating this morning and I stumbled upon this error this morning. Normally I check to see what needed to be updated and then take care of it. I was trying to get a docker updated when I got this message. Diags also included. Thanks in advance. tower-diagnostics-20230130-1043.zip