Ver7o

Members
  • Posts

    71
  • Joined

Report Comments posted by Ver7o

  1. I figured out whats wrong on my part... this is madness. O.o

     

    I usually have manual page zoom set to 120% (set with ctrl+mouse wheel not within firefox settings) and with anything over 100% the tab freezes and throws that FF error of slowing down. If I set page to 100% before clicking apps tab, apps tab works as it should.

     

    This is 100% reproducible on my part.

     

    Call me crazy now. :D

  2. Layout was forced before the page was fully loaded. If stylesheets are not yet loaded this may cause a flash of unstyled content. dynamix.js:4:83380
    [UPC_ENV]  local Apps:355:27
    Sign In to your Unraid.net account to perform license key actions. unraid.min.js:75:96200
    Learn more at https://wiki.unraid.net/My_Servers. unraid.min.js:75:96217
    Some cookies are misusing the recommended “SameSite“ attribute 5
    Cookie “one” will be soon rejected because it has the “SameSite” attribute set to “None” or an invalid value, without the “secure” attribute. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite dynamix.js:6:884
    Cookie “tab” will be soon rejected because it has the “SameSite” attribute set to “None” or an invalid value, without the “secure” attribute. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite dynamix.js:6:884
    Cookie “top” will be soon rejected because it has the “SameSite” attribute set to “None” or an invalid value, without the “secure” attribute. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite dynamix.js:6:884
    Cookie “ca_startupButton” will be soon rejected because it has the “SameSite” attribute set to “None” or an invalid value, without the “secure” attribute. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite dynamix.js:6:884
    Cookie “ca_selectedMenu” will be soon rejected because it has the “SameSite” attribute set to “None” or an invalid value, without the “secure” attribute. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite dynamix.js:6:884
    checkPlugin  community.applications.plg Apps:605:10
    Ports In Use:139,22,22000,3306,3702,444,445,5355,6237,7070,80,8200,8384 Apps:702:17
    Result checkPlugin community.applications.plg Apps:607:11
    {"updateAvailable":false,"version":"2022.03.17a","min":"6.9.0","changes":"###2022.03.17a\n- Fixed: Display aberration on dockerHub installs when running Unraid 6.9.x\n\n###2022.03.17\n- Added: Option to determine automatically any paths, ports, variables used by a dockerHub search install\n- Fixed: A dockerHub search install could overwrite an existing user template if the same name was used\n- Fixed: PHP error if no change to Settings - Display Settings had ever been made\n- Fixed: White on white text would appear on 6.10-rc3 during a container update\n\n###2022.03.13\n- Maintenance Release\n- Fixed: Cancelling a plugin installation from the card if there was a warning popup would disable the search box\n- Fixed: On occasion the warning popup could have corrupted text\n- Fixed: Installed Version was appearing on sidebar if plugin wasn't installed\n- Added: Show current plugin version of non-installed plugins\n- Fixed: Max per page was appearing on Credits and Stats pages\n- Fixed: Ver…
    Apps:608:11
    checkPlugin community.applications.plg: 100ms - timer ended Apps:609:11
    Script terminated by timeout at:
    camelCase@http://192.168.1.100/webGui/javascript/dynamix.js?v=1621953008:4:2695
    css@http://192.168.1.100/webGui/javascript/dynamix.js?v=1621953008:4:53030
    css/<@http://192.168.1.100/webGui/javascript/dynamix.js?v=1621953008:4:54431
    K@http://192.168.1.100/webGui/javascript/dynamix.js?v=1621953008:4:30488
    css@http://192.168.1.100/webGui/javascript/dynamix.js?v=1621953008:4:54272
    updateDisplay/<@http://192.168.1.100/Apps:2206:40
    each@http://192.168.1.100/webGui/javascript/dynamix.js?v=1621953008:4:2861
    each@http://192.168.1.100/webGui/javascript/dynamix.js?v=1621953008:4:845
    updateDisplay@http://192.168.1.100/Apps:2204:82
    getContent/<@http://192.168.1.100/Apps:1531:26
    post/<@http://192.168.1.100/Apps:2437:22
    i@http://192.168.1.100/webGui/javascript/dynamix.js?v=1621953008:4:27151
    fireWith@http://192.168.1.100/webGui/javascript/dynamix.js?v=1621953008:4:27914
    z@http://192.168.1.100/webGui/javascript/dynamix.js?v=1621953008:4:76134
    send/c/<@http://192.168.1.100/webGui/javascript/dynamix.js?v=1621953008:4:79694
    dynamix.js:4:2695

     

    this is my console output, if it makes any sense.

     

    Stangely it works on my Linux device with basically the same settings across the board as the device it fails to load on. Both systems run English language.

     

    I even tried uninstalling/reinstalling the CA plugin (without reboot) and its the same.

  3. Can confirm this. The page does not load on my desktop using FF. After a couple of seconds FF throws "This page is slowing down FIrefox. To speed up your browser, stop this page" and if I click stop, the apps drop in but obviously I can't interact with the tab anymore. Running FF 98.0.1..570150754_2022-03-2110_26_20-Tower_AppsMozillaFirefox.thumb.jpg.caa76a6ef75609b21abc1d8128e2cdb2.jpg

     

    It does however work with brave desktop and with FF mobile.

     

    I went from RC2 to RC4. No issues before.

  4. 21 hours ago, MammothJerk said:

    Did not fix it for me unfortunately.

     

    Has to be something different with my setup then.

    in rc4 both terminal and logs are garbled whilst on my other server 6.9.2 only the terminal is garbled.

    guess i'll post a separate topic for this specific issue.

     

    This is not a FF issue. Its your FF config issue (had the same). Enable "allow HTML5 canvas data extraction" or for your server url and it should work.

     

    2022-03-21-10-09-29-Tower-Update-Mozilla

     

    2022-03-21-10-08-43-Tower-Update-Mozilla

    • Like 1
    • Thanks 1
  5. Just out of curiosity, do you have CPU C states enabled and/or Plex docker running (idle or with active stream, doesnt matter)?

     

    Asking because, I have had similar issues since summer probably, couldn't get over 1 week stability. The logs were all over the place, never the same thing and even getting zero logs wasn't that strange. ATM its been 30 days of stability with the two things mentioned as the only change.

  6. Hello,

     

    I have a question regarding the UPC functonality that (to my knowledge) hasn't been answered anywhere.

    Say we have a failing flash drive, but this flash drive is less then a year old which means changing it for a new one and activating the license is not a one click afair within the GUI.

     

    Does UPC improve that in any way, or is it essentially the same (not the best experience) as before... dropping a line to support so they can manually enable it?

     

    Thanks

  7. I get what LT is trying to do here. I also understand UPC and My Servers are separate things.

     

    - UPC is a system for licence key purchases, upgrades and renewals, meaning u only have to use it when you need something regarding the licence. Thats great, I support the idea. This seems like the only "mandatory" thing to use, as eventually we all meet the thumb drive reaper and need a new licence provisioned. It also enables the second thing which is:

     

    - My Servers plugin is, by my understanding, completely optional and can never see the light of day on ur server, if you do not want it to. That means no "constant connection to the cloud and no telemetry. If you do not have a use case for its features, you dont use it = no connection = win.


    Everything is all fine and good, but I left out the critical part: to use any of these 2 things linking with forum account is neccessary. This is the part I can't fathom. Why link such a critical system with something like a forum page which has very little actual significance in our minds with regards to how we approach it. Why was this chosen over, idk, a "dedicated intranet" for this purpose. We would not need to retrain our minds that this community page suddenly has the literal keys to your kingdom (server) :D

     

    I would be curious to hear the reasoning for this decision.

     

    Thats just my 2 cents about my thought process here.

     

     

  8. Does anything regarding key renewal logic change with My Servers and UPC?

    For example: my flash drives always somehow manage to fail before 1 year is up. The current system allows for automatic key renewal every 1 year, in case of failure. That usually means I have to email support for manual renewal, because just my luck, which means downtime.

     

    Does the new system change such cases or does that 1 year thing remain?

  9. Just to add to the disks not spinning down issue. I had an unassigned thumb drive hooked to my server and the syslog was throwing "emhttpd: spinning down /dev/sde" notices every 15min. I unmounted the drive yesterday, however, to my surprise, syslog is still filing with "emhttpd: spinning down /dev/sde" every 15min.

     

    Anyone experiencing the same?

  10. TurboWrite doesn't seem to be the reason for this. Spin ups still happen without it.

     

    Jan 25 20:53:42 Tower emhttpd: spinning down /dev/sdb
    Jan 25 20:53:42 Tower emhttpd: spinning down /dev/sdc
    Jan 25 20:53:42 Tower emhttpd: spinning down /dev/sdd
    Jan 25 21:24:30 Tower emhttpd: read SMART /dev/sdc
    Jan 25 21:39:32 Tower emhttpd: spinning down /dev/sdc
    Jan 25 21:51:53 Tower emhttpd: read SMART /dev/sdd
    Jan 25 22:06:55 Tower emhttpd: spinning down /dev/sdd
    Jan 25 22:53:12 Tower emhttpd: read SMART /dev/sdc
    Jan 25 23:05:09 Tower emhttpd: read SMART /dev/sdd
    Jan 25 23:05:19 Tower emhttpd: read SMART /dev/sdb
    Jan 25 23:20:11 Tower emhttpd: spinning down /dev/sdd
    Jan 25 23:22:21 Tower emhttpd: spinning down /dev/sdb
    Jan 25 23:22:21 Tower emhttpd: spinning down /dev/sdc
    Jan 25 23:37:59 Tower emhttpd: read SMART /dev/sdc
    Jan 26 00:00:13 Tower emhttpd: read SMART /dev/sdb
    Jan 26 00:01:55 Tower emhttpd: read SMART /dev/sdd
    Jan 26 00:30:19 Tower emhttpd: spinning down /dev/sdb
    Jan 26 00:33:24 Tower emhttpd: spinning down /dev/sdc
    Jan 26 00:33:47 Tower emhttpd: spinning down /dev/sdd
    Jan 26 02:01:55 Tower emhttpd: read SMART /dev/sdd
    Jan 26 02:01:55 Tower emhttpd: read SMART /dev/sdc
    Jan 26 02:18:14 Tower emhttpd: spinning down /dev/sdd
    Jan 26 02:18:16 Tower emhttpd: spinning down /dev/sdc
    Jan 26 09:35:11 Tower emhttpd: read SMART /dev/sdd
    Jan 26 09:50:13 Tower emhttpd: spinning down /dev/sdd
    Jan 26 14:13:46 Tower emhttpd: read SMART /dev/sdc

  11. I have these random smart spinups on RC2 too. I went from stable to RC2 because stable verson did not have drivers for newer intel nics. I do not remember this being a thing on stable. I cannot confirm since the stable was running on different mobo (B450 before, H410 now). I do not run any HBA controllers, just plain mobo sata. The hardware is in its 3rd day so I wouldnt say its dying (faking hopefully right :D)

     

     

    2021-01-24 08_57_21-System Log - Brave.jpg