Jump to content

m8ty

Members
  • Content Count

    34
  • Joined

  • Last visited

Community Reputation

6 Neutral

About m8ty

  • Rank
    Advanced Member

Recent Profile Visitors

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

  1. Ah yes I do use one, specifically 1Password. I just find it annoying to have to login, sometimes even while I am in the middle of interacting with the webui I find the interface asks me to log back in again. For example, it did it again before I checked this thread! I suppose it's a problem specific to me if no-one has complained about it. The interesting this is it happens on my laptop, my desktop, Safari browser, Firefox browser, my iPhone...
  2. Hi there, I seem to be automatically logged out of the webui often, and having to log back into the unraid interface often. This is annoying because I am the only one who accesses it. This is what I see often and I don't know why I am logged out How do I stay logged in? Preferably never having to log in again after doing it once.
  3. Hi, does nerdpack install packages before the go file is executed? Meaning: if I place “pip3 install docker-compose” in my go file, docker-compose should install?
  4. So afaik "Community Applications" apps can only run one container in a template, whereas docker-compose can run multiple containers in a compose file. According to the Seafile docs here https://download.seafile.com/published/seafile-manual/docker/pro-edition/6.3 upgrade to 7.0.md version 7 has been broken up into multiple containers and "is configured and run using docker-compose". It seems users will have to start using docker-compose with version 7 if deploying with Docker *** Some notes on my upgrade experience: - Upgrade instructions 6.3 to 7.0 https://download.seafile.com/published/seafile-manual/docker/6.3 upgrade to 7.0.md - For deploying Seafile-pro https://download.seafile.com/published/seafile-manual/docker/pro-edition/6.3 upgrade to 7.0.md - Make sure to edit the yml as needed. - File structure: I organized the application files in a dir at "/mnt/user/seafile7/opt", that way it is in harmony with the Seafile documentation. Hopefully this makes it easier to troubleshoot/maintain in the future. I hope this helps edit - seems I also had to expose ports for "seafhttp" "seafdav". Not sure if I had set this up myself in my previous installation or the docs forgot to mention it
  5. Thank you. Simply curious. I had a problem with unraid not booting after upgrading earlier this year I was not sure if the upgrade process was the issue.
  6. Hello, What are the instructions to do a manual upgrade from the last stable version—Version 6.7.2?
  7. I have a question about a setting: In the "Docker Auto Update Settings" settings tab, there is the setting "Time to wait for docker graceful stop before killing". What unit of time does this use? Seconds or minutes? What command is used for a graceful stop versus killing? Does it kill dockerd or only containers currently running? Thank you!
  8. I just had a hell of a time getting the network interface working again after adding a mount tag in the tower/VMs page. (Btw this seems like an Unraid bug, hopefully it gets fixed eventually) I'm running an Ubuntu 19.04 VM When you add a mount tag, my Ubuntu VM's network interface logical name gets changed to enp3s0 (I don't know what it was before, but the problem is it has changed and now my netplan config needs to be fixed) A temporary fix to get the VM back on the network like @snailbrain mentioned: sudo dhclient enp3s0 I had to edit /etc/cloud/cloud.cfg.d/50-curtin-networking.cfg to setup static addressing instead of DHCP network: version: 2 ethernets: enp3s0: addresses: [192.168.88.25/24] - https://netplan.io/examples - https://askubuntu.com/questions/1036266/what-is-the-most-authoritative-file-process-for-managing-ip-addresses-on-an-18-0 I ran some commands I found on various stackexchange threads sudo cloud-init clean --logs sudo cloud-init init --local sudo netplan apply - https://askubuntu.com/questions/1104285/how-do-i-reload-network-configuration-with-cloud-init - https://askubuntu.com/questions/1029531/how-to-setup-a-static-ip-on-ubuntu-server-18-04 - https://askubuntu.com/questions/1036266/what-is-the-most-authoritative-file-process-for-managing-ip-addresses-on-an-18-0 Now my networking interface config persists between reboots
  9. To disable the need to login as admin:rutorrent at http://<host ip>:9080/ aka HTTP Basic Authentication Per the nginx docs http://nginx.org/en/docs/http/ngx_http_auth_basic_module.html In file `/config/nginx/config/nginx.conf` eg `/mnt/user/appdata/binhex-rtorrentvpn/nginx/config/nginx.conf` You can set `auth_basic` to "off", like so: location / { index index.html index.htm index.php; #auth_basic "Restricted Content"; auth_basic off; auth_basic_user_file /config/nginx/security/auth; } HTTP Basic Authentication will be disabled after restarting the container 👍.
  10. Yes I just caught that! I have run xfs_repair on the cache drive through the Unraid webui, found the corruption with -n and fixed it by omitting all flags per the wiki.
  11. Hi, Lately my Unraid install has been crashing/unresponsive. That means no response from webui/ssh/ping, and the attached display connected to the actual server is frozen. I am attaching the diagnostics zip as well as the /var/log/syslog I was able to capture with a remote syslog server, hopefully that is helpful but I'm unable to find anything telling me what happened. The last recorded log was @ Jul 07 07:52:45 shoebox kernel: mdcmd (66): spindown 1 And then my girlfriend told me she couldn't access the Plex at 8:17am I assume it could be because of docker since Unraid crashes often when I experiment with containers outside of "community applications" shoebox-diagnostics-20190707-1752.zip syslog.txt
  12. I recently upgraded my installation to 16.0.1 and I am getting the same warning: The "Strict-Transport-Security" HTTP header is not set to at least "15552000" seconds. For enhanced security, it is recommended to enable HSTS as described in the security tips ↗. Maybe it's a change in the nginx conf files between the last version (15) and the current (16) version by the LinuxServer.io author
  13. If you correctly mapped the new port, and you correctly set the WEBUI_PORT environment variable eg: to set the port to 8090 you need to set -p 8090:8090 and -e WEBUI_PORT=8090 Now the qBittorrent.conf should have been automatically set to WebUI\Port=8090 now I think You could try this troubleshooting tip taken from the linuxserver/docker-qbittorrent container readme.md https://github.com/linuxserver/docker-qbittorrent#webui_port-variable If you have no webui , check the file /config/qBittorrent/qBittorrent.conf edit or add the following lines ``` WebUI\Address=* WebUI\ServerDomains=* ``` Lastly, binhex-qbittorrentvpn doesn't like it when I launch the WebUI from http://tower/Docker page, I get a blank white screen. So I directly visit in my browser http://192.168.88.8:8090/