Jump to content

theGrok

Members
  • Content Count

    85
  • Joined

  • Last visited

Community Reputation

0 Neutral

About theGrok

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

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

  1. Yes, I put in the user/pass into the template and started the container once. I then copied over my .ovpn config into the openvpn folder. I was then was able to see that the credentials.conf was created. The logs say that privoxy has started. I'll recheck everything. I just wanted to confirm that setting up the host port that way was ok. Thank you. UPDATE: I tried to use the proxy in a radarr config, and it seems to connect fine. I just can't get it to work in a web browser for some reason.
  2. Hi. Thank you for making this container. I am already running your ruTorrentVPN container w/ privoxy enabled. I would like to install this one as well in order to have another endpoint available as an option. Since the ruTorrent one is already using 8118 for privoxy, would it be sufficient to change the host port of this container to say 8119 (leaving the container port 8118) in order to get this working? I've tried that, but privoxy does not seem to be working. Thank you.
  3. Well, I figured it out. I took a closer look at the ratio.dat file and it does in fact save my changes. I even restarted the container and it the changes were maintained. I reported that it did not save incorrectly above. I loaded ruTorrent ui with another browser and lo and behold, the ratio groups were there with my changes. When i went into my original browser (firefox) it did not have the changes. I reloaded the page without cage and it worked. So this appears perhaps to have been a browser cache issue more than anything. apologies for the confusion.
  4. nothing strange there that I can see
  5. I am not sure which log I should be looking at, nor where it is stored, to be honest
  6. it does not seem to change the files when I make changes to the ui.
  7. Thanks. Does this mean that I cannot use UI to set the groups and that I have to edit them in the console in order for them to persist? Thank you.
  8. Did you ever get this solved? I tried to use ratio groups for the first time today and even though I edit the group options, they always seem to go back to default. How can I make these settings permanent? Thank you.
  9. This would be great. clientbuffer is a must for those with multiple devices. Push is also very versatile as it works with many notification services. It is a lifesaver for those who are in multiple channels at the same time.
  10. Thank you for your reply. Indeed these are from after reboot. I thought perhaps old syslogs were saved. I have had more call traces, and I saw out of memory errors as well but have since rebooted. If I get more call traces I will post a new diagnostics. The first time, I did not have access to anything so could not.
  11. I am currently running 6.5. Everything has been going smoothly. Today I was in an RDP session on one of my VMs. All of the sudden I lost my session. My server became unreachable. I could not ping it or anything. I gently pushed the power button to initiate shutdown. Nothing. I then unplugged the UPS to try to initiate shutdown and the server would not shutdown. Finally, I had no choice but to hard reset the machine. The server came back up and everything seemed fine. A parity check initiated. After a couple of minutes, I lost access to the gui. I hooked up a monitor to the server and saw call trace messages and the server was frozen. I had to do another reboot. I have no idea what is causing this behavior. I have now disabled docker and VMs and will see if the server can stay online. I am just wondering if anyone can point me in the right directions as to what might be causing this? Is this bad hardware? Do I need to reinstall unRaid? I have attached diagnostics. medserver-diagnostics-20180408-2145.zip
  12. I upgraded to 6.5 with no problems at first. Yesterday, my windows VM started freezing. I tried to shut it down and could not. I did a force stop and restarted my server. When it came back, my cache drive showed Unmountable: No File System. I had backups of mostly everything, so I formatted the cache, restored my appdata, libvirt, and vdisks. Everything was back up and running smoothly. This morning while updating the windows VM (the vdisk backup was quite a bit older). It froze again. I checked the log and saw call traces and btrfs errors. Fix Common problems also reports: Mar 16 05:53:34 Medserver root: Fix Common Problems: Error: Unable to write to cache Mar 16 05:53:34 Medserver root: Fix Common Problems: Error: Unable to write to Docker Image I do not know whether it is just a coincidence that it happened after the upgrade or if my SSD is going bad. SMART seems ok. Now that it has happened a second time, I thought I would post here. The first time I had the problem I posted here. My original diagnostics are attached in this thread: I have also attached my new diagnostics here. It is from after I formatted the cache drive and restored. Thank you for any assistance that you provide. medserver-diagnostics-20180316-0533.zip
  13. thank you so much for all of your help. much appreciated.
  14. btrfs restore -v /dev/sdX1 /mnt/disk2/restore this seems to be working to restore some data. The first method returned could not read superblock. Any chance that something in the logs shows that it is the hardware that went bad? Should I be replacing this SSD?
  15. Thanks I'll try the recovery process. If that fails, I did find an older backup of my vidsk. Better than nothing I suppose. I would format, restore from CA Backup_restore, copy over the old vdisk and reboot?