Elmojo

Members
  • Posts

    88
  • Joined

  • Last visited

Recent Profile Visitors

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

Elmojo's Achievements

Apprentice

Apprentice (3/14)

19

Reputation

  1. AWESOME!!!! Thanks so much for listening to the community! This is one of the many things that makes Unraid so vastly superior to other competing platforms in my opinion. I just love the involvement of the Devs.
  2. It's probably just me, most things are. I'm not aware of any browser settings/addons that would affect how pages render. Certainly not anything that is installed on all 3, since I rarely use chrome and NEVER use Edge. I didn't see anything in the display settings to "try". It just looked like they were set on recommended scaling and resolution. I'm reluctant to set my display scale to 150%, as that would screw up my desktop icons, and it would take a while to get them back right. I'll just assume that the problem is me until others chime in, or not.
  3. I'm sorry, perhaps I'm not being clear, but I just don't know any other way to say it. I'll paste what I said above, but only speak for myself this time. "My point is that if the dashboard worked for me like it seems to for you and a few others, then there would have been no need for me to start this thread in the first place". That indeed doesn't have anything directly to do with the number of columns, but rather the dashboard experience as a whole, and that not being able to move and arrange items freely is making it difficult to keep up with all the data. The fact that for some of us (such as yourself) the dashboard seems to be resizing itself and adding/removing columns dynamically goes a long way towards addressing the issue I was complaining about in the first post.
  4. Hahah yeah, I started the thread, I know. My point is that if the dashboard worked for me (and all the other +1s) like it seems to for you and a few others, then there would have been no need for me to start this thread in the first place. I would have just arranged my columns vertically as best as I could, then sized the browser to spill or stack the 2nd/3rd column until I got it as good as possible. It probably wouldn't have been perfect, but it certainly would be better than what I'm dealing with now. Granted, it wouldn't have fixed the frustration of having most of the important stuff stuck in the left column, but it would likely have been below the "I have to get some help with this" threshold.
  5. Well that's just nuts. So it appears that for some of us, it's working fairly well, and resizing columns to fit the available window space, pretty much as you'd expect. For the rest of us (all those who have added their +1's to this thread), the columns are fixed at 3, and don't resize at all. Changing the browser window size only adds scroll bars, as though the page layout was fixed, and not responsive at all. Really odd. I don't have a clue how to explain that. Hopefully one of the devs will eventually see this and can perhaps explain why it happens and more importantly, can proposed a solution for those of us whose dashboards are not operating "as designed". This has just gone from a feature request to a bug report, I think.
  6. Well I just don't know what to tell you then. Mine absolutely does not do that, on any browser. I'm on Windows 10 x64. If mine did as shown in your gif, I would never have created this thread, since I often run my dashboard in a non-maximized window and would have noticed that behavior right away. Really strange. I'll be interested to hear from others as to whether theirs acts as yours, or more like mine. I can't imagine what sort of environmental variable or system configuration could account for the difference.
  7. That's very interesting, as mine does not display that behavior. I would assume that it doesn't work that way for others either, or there wouldn't be so much support for this issue to be resolved. Are you both @JonathanM and @Hoopster accessing the dashboard through a standard url? I mean, there's not an app or anything, is there? I have to assume this is on a desktop PC, right? I can't imagine how you'd be able to resize the window otherwise. Are you using some sort of dashboard plugin perhaps that adds that functionality? I don't know how to create and post a gif like that, or I could demonstrate that mine doesn't work the way shown above.
  8. I have never observed this behavior. I've tried Chrome, Firefox and Edge. Can you provide an example of how to make it do this? If the dashboard would work this way, I doubt we all would be complaining so much, since that would provide at least a workaround for how to get things into a bit more balanced view. When I resize my browser, all that happens is it cuts off the right column and adds a horizontal scroll. Please tell me I'm missing something, this would be awesome!
  9. So I thought I had this worked out, but I guess not.... Mine was running fine until recently, where it's stopped backing up automatically. If I run the backup manually, it works fine. All VMs stop, backup, and restart as expected. However, if the job runs as scheduled, it fails and I get a notification on the dashboard that the backup failed to run, but it doesn't say why. l've tried looking at the logs, but they are set to clear after 1, and I had already run a manual backup, so I have to wait until it fails again, which I believe will be tomorrow. Any idea what would cause a failure when scheduled, but work fine when run manually?
  10. That's good to learn. I didn't know that was a thing. It's the first time this has happened to me in over a year. I'll be on the lookout for it in the future. Thanks for the help!
  11. Creating and uploading new ovpn certs seemed to fix it. No idea why. Anyway, thanks!!
  12. Ok, I changed to those you listed. Where should I have gotten the new list from, out of curiosity? Nope, updated the NS list, re-enabled VPN... broken. No access.
  13. I saw that line. I don't think I can without deleting the port forward and reconfiguring the whole thing. I'd hate to do that if it's just not gonna work anyway. I was hoping someone would know if something had changed with the way we have to config for Mullvad or whatever. I'm not too well versed in this stuff, so I hate to monkey around in there and break it more without some guidance.
  14. Here's just the part from the last time I restarted the container, and then when I disabled the VPN and restarted it again... Created by... ___. .__ .__ \_ |__ |__| ____ | |__ ____ ___ ___ | __ \| |/ \| | \_/ __ \\ \/ / | \_\ \ | | \ Y \ ___/ > < |___ /__|___| /___| /\___ >__/\_ \ \/ \/ \/ \/ \/ https://hub.docker.com/u/binhex/ 2022-11-02 21:02:04.377689 [info] Host is running unRAID 2022-11-02 21:02:04.415799 [info] System information Linux 1954464e178d 5.15.46-Unraid #1 SMP Fri Jun 10 11:08:41 PDT 2022 x86_64 GNU/Linux 2022-11-02 21:02:04.456379 [info] OS_ARCH defined as 'x86-64' 2022-11-02 21:02:04.495462 [info] PUID defined as '1001' 2022-11-02 21:02:04.539328 [info] PGID defined as '100' 2022-11-02 21:02:04.633757 [info] UMASK defined as '000' 2022-11-02 21:02:04.672597 [info] Permissions already set for '/config' 2022-11-02 21:02:04.720468 [info] Deleting files in /tmp (non recursive)... 2022-11-02 21:02:04.777290 [info] VPN_ENABLED defined as 'yes' 2022-11-02 21:02:04.819589 [info] VPN_CLIENT defined as 'openvpn' 2022-11-02 21:02:04.860236 [info] VPN_PROV defined as 'custom' 2022-11-02 21:02:04.912225 [info] OpenVPN config file (ovpn extension) is located at /config/openvpn/mullvad_us_atl.ovpn 2022-11-02 21:02:05.120742 [info] VPN remote server(s) defined as 'us-atl-105.mullvad.net,us-atl-104.mullvad.net,us-atl-101.mullvad.net,us-atl-103.mullvad.net,us-atl-102.mullvad.net,' 2022-11-02 21:02:05.154388 [info] VPN remote port(s) defined as '1301,1301,1301,1301,1301,' 2022-11-02 21:02:05.187845 [info] VPN remote protcol(s) defined as 'udp,udp,udp,udp,udp,' 2022-11-02 21:02:05.226177 [info] VPN_DEVICE_TYPE defined as 'tun0' 2022-11-02 21:02:05.261517 [info] VPN_OPTIONS not defined (via -e VPN_OPTIONS) 2022-11-02 21:02:05.301258 [info] LAN_NETWORK defined as '192.168.11.0/24' 2022-11-02 21:02:05.344647 [info] NAME_SERVERS defined as '209.222.18.222,84.200.69.80,37.235.1.174,1.1.1.1,209.222.18.218,37.235.1.177,84.200.70.40,1.0.0.1' 2022-11-02 21:02:05.386736 [info] VPN_USER defined as 'xxxxxx' 2022-11-02 21:02:05.431075 [info] VPN_PASS defined as 'xxxxxx' 2022-11-02 21:02:05.473985 [info] ENABLE_PRIVOXY defined as 'no' 2022-11-02 21:02:05.521751 [info] VPN_INPUT_PORTS defined as 'REDACTED' 2022-11-02 21:02:05.561524 [info] VPN_OUTPUT_PORTS not defined (via -e VPN_OUTPUT_PORTS), skipping allow for custom outgoing ports 2022-11-02 21:02:05.604734 [info] WEBUI_PORT defined as '8080' 2022-11-02 21:02:05.646152 [info] Starting Supervisor... 2022-11-02 21:02:05,896 INFO Included extra file "/etc/supervisor/conf.d/qbittorrent.conf" during parsing 2022-11-02 21:02:05,897 INFO Set uid to user 0 succeeded 2022-11-02 21:02:05,901 INFO supervisord started with pid 8 2022-11-02 21:02:06,905 INFO spawned: 'start-script' with pid 236 2022-11-02 21:02:06,907 INFO spawned: 'watchdog-script' with pid 237 2022-11-02 21:02:06,908 INFO reaped unknown pid 9 (exit status 0) 2022-11-02 21:02:06,914 DEBG 'start-script' stdout output: [info] VPN is enabled, beginning configuration of VPN 2022-11-02 21:02:06,914 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2022-11-02 21:02:06,914 INFO success: watchdog-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2022-11-02 21:02:06,920 DEBG 'watchdog-script' stdout output: [info] qBittorrent config file already exists, skipping copy [info] Removing session lock file (if it exists)... 2022-11-02 21:02:07,029 DEBG 'start-script' stdout output: [info] Adding 209.222.18.222 to /etc/resolv.conf 2022-11-02 21:02:07,035 DEBG 'start-script' stdout output: [info] Adding 84.200.69.80 to /etc/resolv.conf 2022-11-02 21:02:07,039 DEBG 'start-script' stdout output: [info] Adding 37.235.1.174 to /etc/resolv.conf 2022-11-02 21:02:07,044 DEBG 'start-script' stdout output: [info] Adding 1.1.1.1 to /etc/resolv.conf 2022-11-02 21:02:07,049 DEBG 'start-script' stdout output: [info] Adding 209.222.18.218 to /etc/resolv.conf 2022-11-02 21:02:07,055 DEBG 'start-script' stdout output: [info] Adding 37.235.1.177 to /etc/resolv.conf 2022-11-02 21:02:07,062 DEBG 'start-script' stdout output: [info] Adding 84.200.70.40 to /etc/resolv.conf 2022-11-02 21:02:07,068 DEBG 'start-script' stdout output: [info] Adding 1.0.0.1 to /etc/resolv.conf 2022-11-02 21:05:14,221 DEBG 'start-script' stdout output: [crit] 'us-atl-105.mullvad.net' cannot be resolved, possible DNS issues, exiting... 2022-11-02 21:05:14,221 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 23425766678704 for <Subprocess at 23425766673808 with name start-script in state RUNNING> (stdout)> 2022-11-02 21:05:14,221 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 23425766678656 for <Subprocess at 23425766673808 with name start-script in state RUNNING> (stderr)> 2022-11-02 21:05:14,222 INFO exited: start-script (exit status 1; not expected) 2022-11-02 21:05:14,222 DEBG received SIGCHLD indicating a child quit 2022-11-02 21:39:32,560 WARN received SIGTERM indicating exit request 2022-11-02 21:39:32,561 DEBG killing watchdog-script (pid 237) with signal SIGTERM 2022-11-02 21:39:32,561 INFO waiting for watchdog-script to die 2022-11-02 21:39:32,562 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 23425766679088 for <Subprocess at 23425766678416 with name watchdog-script in state STOPPING> (stdout)> 2022-11-02 21:39:32,562 DEBG fd 15 closed, stopped monitoring <POutputDispatcher at 23425766679136 for <Subprocess at 23425766678416 with name watchdog-script in state STOPPING> (stderr)> 2022-11-02 21:39:32,563 INFO stopped: watchdog-script (exit status 143) 2022-11-02 21:39:32,563 DEBG received SIGCHLD indicating a child quit Created by... ___. .__ .__ \_ |__ |__| ____ | |__ ____ ___ ___ | __ \| |/ \| | \_/ __ \\ \/ / | \_\ \ | | \ Y \ ___/ > < |___ /__|___| /___| /\___ >__/\_ \ \/ \/ \/ \/ \/ https://hub.docker.com/u/binhex/ 2022-11-02 21:46:53.279086 [info] Host is running unRAID 2022-11-02 21:46:53.312759 [info] System information Linux 5b098552d729 5.15.46-Unraid #1 SMP Fri Jun 10 11:08:41 PDT 2022 x86_64 GNU/Linux 2022-11-02 21:46:53.359554 [info] OS_ARCH defined as 'x86-64' 2022-11-02 21:46:53.399484 [info] PUID defined as '1001' 2022-11-02 21:46:53.507180 [info] PGID defined as '100' 2022-11-02 21:46:53.639214 [info] UMASK defined as '000' 2022-11-02 21:46:53.682330 [info] Permissions already set for '/config' 2022-11-02 21:46:53.728705 [info] Deleting files in /tmp (non recursive)... 2022-11-02 21:46:53.782141 [info] VPN_ENABLED defined as 'no' 2022-11-02 21:46:53.823187 [warn] !!IMPORTANT!! VPN IS SET TO DISABLED', YOU WILL NOT BE SECURE 2022-11-02 21:46:53.868503 [info] WEBUI_PORT defined as '8080' 2022-11-02 21:46:53.917979 [info] Starting Supervisor... 2022-11-02 21:46:54,310 INFO Included extra file "/etc/supervisor/conf.d/qbittorrent.conf" during parsing 2022-11-02 21:46:54,310 INFO Set uid to user 0 succeeded 2022-11-02 21:46:54,314 INFO supervisord started with pid 7 2022-11-02 21:46:55,319 INFO spawned: 'start-script' with pid 80 2022-11-02 21:46:55,322 INFO spawned: 'watchdog-script' with pid 81 2022-11-02 21:46:55,322 INFO reaped unknown pid 8 (exit status 0) 2022-11-02 21:46:55,338 DEBG 'start-script' stdout output: [info] VPN not enabled, skipping configuration of VPN 2022-11-02 21:46:55,339 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2022-11-02 21:46:55,339 INFO success: watchdog-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2022-11-02 21:46:55,339 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22496522788848 for <Subprocess at 22496522783952 with name start-script in state RUNNING> (stdout)> 2022-11-02 21:46:55,340 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22496522788080 for <Subprocess at 22496522783952 with name start-script in state RUNNING> (stderr)> 2022-11-02 21:46:55,340 INFO exited: start-script (exit status 0; expected) 2022-11-02 21:46:55,340 DEBG received SIGCHLD indicating a child quit 2022-11-02 21:46:55,341 DEBG 'watchdog-script' stdout output: [info] qBittorrent config file already exists, skipping copy [info] Removing session lock file (if it exists)... 2022-11-02 21:46:55,395 DEBG 'watchdog-script' stdout output: [info] qBittorrent not running 2022-11-02 21:46:55,396 DEBG 'watchdog-script' stdout output: [info] Removing session lock file (if it exists)... 2022-11-02 21:46:55,418 DEBG 'watchdog-script' stdout output: [info] Attempting to start qBittorrent... 2022-11-02 21:46:55,540 DEBG 'watchdog-script' stdout output: [info] qBittorrent process started [info] Waiting for qBittorrent process to start listening on port 8080... 2022-11-02 21:46:55,671 DEBG 'watchdog-script' stdout output: [info] qBittorrent process listening on port 8080