mihu

Members
  • Posts

    14
  • Joined

  • Last visited

Everything posted by mihu

  1. The "Share Floor" plugin is broken for me. I think it has something to do with that I use different ports for my web ui. It is trying to acces the web ui on regular https port which is used by my reverse proxy. Scanning downloads ... Warning: file_get_contents(): Peer certificate CN=`*.mydomainname.com' did not match expected CN=`localhost' in /usr/local/emhttp/plugins/dynamix.share.floor/scripts/share_floor on line 40 Warning: file_get_contents(): Failed to enable crypto in /usr/local/emhttp/plugins/dynamix.share.floor/scripts/share_floor on line 40 Warning: file_get_contents(http://localhost/update.htm): failed to open stream: operation failed in /usr/local/emhttp/plugins/dynamix.share.floor/scripts/share_floor on line 40 updated - new floor setting: 10.3 GB Scanning media ... Warning: file_get_contents(): Peer certificate CN=`*.mydomainname.com' did not match expected CN=`localhost' in /usr/local/emhttp/plugins/dynamix.share.floor/scripts/share_floor on line 40
  2. Using jackett via privoxy is not a good idea since it does not pass dns requests through privoxy. It is "leaking" those request to your regular dns servers. Jackett even has a warning about using proxy.
  3. @Dyon Thanks everything works fine now.
  4. Not sure since when, but it keeps crashing for me right after start. I have completely removed it and the template. This happens on a fresh install. LOG: 2021-02-12 20:54:08.312940 [INFO] Changing the ownership of the database ownership of '/root/.local/share/magneticod' retained as 99:users ----------- magneticow ----------- 2021-02-12 20:54:08.347295 [INFO] Refreshing the credentials file Adding password for user magnetico 2021-02-12 20:54:08.689373 [INFO] Setting magneticow address to 0.0.0.0 2021-02-12 20:54:08.719119 [INFO] Enabling verbosity for magneticow ----------- magneticod ----------- 2021-02-12 20:54:08.749972 [INFO] Setting magneticod indexing address to 0.0.0.0 2021-02-12 20:54:08.780145 [INFO] Setting magneticod indexing port to 0 2021-02-12 20:54:08.811124 [INFO] Setting magneticod indexing interval to 1 2021-02-12 20:54:08.842619 [INFO] Setting magneticod maximum number of neighbors to 1000 2021-02-12 20:54:08.873005 [INFO] Setting magneticod maximum number of leeches to 50 2021-02-12 20:54:08.905086 [INFO] Enabling verbosity for magneticod ---------------------------------- 2021-02-12 20:54:08.947026 [INFO] Starting magneticow... 2021-02-12 20:54:08.997816 [INFO] Log file /opt/magnetico/Logs/magneticow.txt doesn't exist. Creating it... 2021-02-12 20:54:09.031738 [INFO] Logfile created. Logging to /opt/magnetico/Logs/magneticow.txt magnetico.txt contents: /opt/magnetico/magneticow: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /opt/magnetico/magneticow)
  5. You can use: mv /mnt/user/a/foo /mnt/user0/b/ to have it moved outside cache edit: will not work for mover though, but if You have something specific You could make a custom scheduled script or something
  6. No benefit? The drive will last longer due to wear levelling.
  7. Mine started crashing a lot after recent updates. Some weird behavior in logs. https://pastebin.com/gJB9Wa32 Edit: Seems to be fixed now Edit2: And gone crazy again. It's as if it stopped reading conf files properly. It shows center in weird place. Edit3: Well I need to look deeper into this. Mantainer of the github repo has done some breaking changes recently. I was thinking of moving to raspberry pi anyway as I don't like 3m usb cable going from my unraid server to window where my sdr is located Edit4: I decided to go with Shoginn's containers. I liked the idea of a single container but Shoginn's seem to work better anyway.
  8. You should probably report it here
  9. Also experiencing the same problem with random log outs, even when doing something on the server.
  10. This has something to do with some network setting. I tried same setup on my test server and it works fine with all the recent hassio_supervisor changes, so it's not it's fault as i have thought before. Using IP address like: 192.168.0.7:7800 doesnt work, it returns code 1006. Using unraid domain name works: somerandomgeneratedtext.unraid.net:7800 works and returns the web ui fine. It's all weird for me.
  11. I did not change anything recently in configs for those two, but they stopped working. Not sure when it happened as I don't use them everyday. Tried removing completely and redownloading but still the same. Well, I think I figured it out. Recent updates to hassio-supervisor broke something with docker networks. I have setup the containers with br0 network and custom ip and it works fine... Sorry for the trouble. my-intel-gpu-tools.xml my-HandBrake.xml
  12. Is it just me or something is broken in intel-gpu-tools and handbrake? I'm unable to access web ui of those containers. Including log from intel gpu tools intel-gpu-tools.log