• [6.12.0] Dashboard misaligned - only 2 columns - main menu cut off


    ezek1el3000
    • Solved Annoyance

    I just updated from 6.11.5 to 6.12. Now the dashboard is all messed up. There are only  2 columns to put the "widgets" in. And the top menu is cut off. This is on Firefox 114.0.1. Windows 10

     

    2023-06-16_213836.jpg

    diagnostics-20230616-2133.zip




    User Feedback

    Recommended Comments



    Make sure your screen resolution is large enough to hold 3 columns.

     

    Put Windows scaling and browser scaling to 100% or smaller to make it fit.

     

    Link to comment

    The screen resolution is 1920x1080 and scaling set to 100%. Setting the scaling higher changes the scaling of other tabs with other ui coming from the same base url as well. The dashboard looks fine in Edge. I tested this on another monitor with a resolution of 2560x1080 and the dashboard won't show three columns either.

    Edited by ezek1el3000
    problem not solved
    Link to comment

    Can confirm I have the same issue, after updating to 6.12. Scaling is all setup correct (as it has always been). 

    Link to comment

    IIRC resetting the panes helped a user before, unlock, then click the wrench icon, then "reset"

     

    image.png

     

     

    • Thanks 1
    Link to comment
    45 minutes ago, bonienl said:

    This is the dashboard at a resolution of 1920 x 1080

     

    image.png

     

    which browser?

     

    48 minutes ago, JorgeB said:

    IIRC resetting the panes helped a user before, unlock, then click the wrench icon, then "reset"

     

    image.png

     

     

    Reset does nothing. Not resetting the layout, not setting anything else back. Tested on Firefox and Edge, different resolutions, always 100% scaling.

    I tried a new Firefox profile without any addons, same result.

    Edited by ezek1el3000
    Link to comment
    1 minute ago, ezek1el3000 said:

    which browser?

     

    Tested with Chrome, Firefox, Edge, Safari and Brave.

     

    2 minutes ago, ezek1el3000 said:

    always 100% scaling.

     

    Check you windows display properties, and set it to 100%

     

    Link to comment

    Your are missing the information about parity, array and pools.

    The screen should look like this

     

    image.png

     

    Your previous diagnostics is littered with ACPI errors because the BIOS is erroneous, not related but you propably should disable acpi in syslinux.

     

    image.png

     

    Furthermore there are nginx errors caused by plugins. Check for updates.

     

    Jun 16 21:02:52 Fileserver nginx: 2023/06/16 21:02:52 [error] 25539#25539: *55364 open() "/usr/local/emhttp/server-status" failed (2: No such file or directory), client: 127.0.0.1, server: , request: "GET /server-status?auto HTTP/1.1", host: "localhost"
    Jun 16 21:02:52 Fileserver nginx: 2023/06/16 21:02:52 [error] 25539#25539: *55365 open() "/usr/local/emhttp/server-status" failed (2: No such file or directory), client: 127.0.0.1, server: , request: "GET /server-status?auto HTTP/1.1", host: "127.0.0.1"
    Jun 16 21:02:52 Fileserver nginx: 2023/06/16 21:02:52 [error] 25539#25539: *55366 open() "/usr/local/emhttp/basic_status" failed (2: No such file or directory), client: 127.0.0.1, server: , request: "GET /basic_status HTTP/1.1", host: "127.0.0.1"
    Jun 16 21:02:52 Fileserver nginx: 2023/06/16 21:02:52 [error] 25539#25539: *55367 open() "/usr/local/emhttp/stub_status" failed (2: No such file or directory), client: 127.0.0.1, server: , request: "GET /stub_status HTTP/1.1", host: "localhost"
    Jun 16 21:02:52 Fileserver nginx: 2023/06/16 21:02:52 [error] 25539#25539: *55368 open() "/usr/local/emhttp/stub_status" failed (2: No such file or directory), client: 127.0.0.1, server: , request: "GET /stub_status HTTP/1.1", host: "127.0.0.1"
    Jun 16 21:02:52 Fileserver nginx: 2023/06/16 21:02:52 [error] 25539#25539: *55369 open() "/usr/local/emhttp/nginx_status" failed (2: No such file or directory), client: 127.0.0.1, server: , request: "GET /nginx_status HTTP/1.1", host: "127.0.0.1"
    Jun 16 21:02:52 Fileserver nginx: 2023/06/16 21:02:52 [error] 25539#25539: *55370 open() "/usr/local/emhttp/status" failed (2: No such file or directory), client: 127.0.0.1, server: , request: "GET /status HTTP/1.1", host: "127.0.0.1"
    Jun 16 21:03:01 Fileserver nginx: 2023/06/16 21:03:01 [error] 25539#25539: *55482 open() "/usr/local/emhttp/us" failed (2: No such file or directory), client: 127.0.0.1, server: , request: "GET /us HTTP/1.1", host: "localhost"
    Jun 16 21:03:01 Fileserver nginx: 2023/06/16 21:03:01 [error] 25539#25539: *55483 open() "/usr/local/emhttp/us" failed (2: No such file or directory), client: 127.0.0.1, server: , request: "GET /us HTTP/1.1", host: "127.0.0.1"
    Jun 16 21:03:01 Fileserver nginx: 2023/06/16 21:03:01 [error] 25539#25539: *55484 open() "/usr/local/emhttp/status" failed (2: No such file or directory), client: 127.0.0.1, server: , request: "GET /status?full&json HTTP/1.1", host: "localhost"
    Jun 16 21:03:01 Fileserver nginx: 2023/06/16 21:03:01 [error] 25539#25539: *55485 open() "/usr/local/emhttp/status" failed (2: No such file or directory), client: 127.0.0.1, server: , request: "GET /status?full&json HTTP/1.1", host: "127.0.0.1"
    Jun 16 21:03:01 Fileserver nginx: 2023/06/16 21:03:01 [error] 25539#25539: *55486 open() "/usr/local/emhttp/status" failed (2: No such file or directory), client: ::1, server: , request: "GET /status?full&json HTTP/1.1", host: "[::1]"

     

    Please post new diagnostics with your array halted and in safe mode.

     

    Link to comment
    On 6/17/2023 at 2:32 PM, bonienl said:

    Your previous diagnostics is littered with ACPI errors because the BIOS is erroneous, not related but you propably should disable acpi in syslinux.

     

    image.png

     

    Furthermore there are nginx errors caused by plugins. Check for updates.

     

     

    I added it. After that my gpu was no longer available. So i reverted the setting and have to live with the ACPI errors which are nothing to worry about apperently. Bios is up to date

     

     

    On 6/17/2023 at 2:32 PM, bonienl said:

     

    Jun 16 21:02:52 Fileserver nginx: 2023/06/16 21:02:52 [error] 25539#25539: *55364 open() "/usr/local/emhttp/server-status" failed (2: No such file or directory), client: 127.0.0.1, server: , request: "GET /server-status?auto HTTP/1.1", host: "localhost"
    Jun 16 21:02:52 Fileserver nginx: 2023/06/16 21:02:52 [error] 25539#25539: *55365 open() "/usr/local/emhttp/server-status" failed (2: No such file or directory), client: 127.0.0.1, server: , request: "GET /server-status?auto HTTP/1.1", host: "127.0.0.1"
    Jun 16 21:02:52 Fileserver nginx: 2023/06/16 21:02:52 [error] 25539#25539: *55366 open() "/usr/local/emhttp/basic_status" failed (2: No such file or directory), client: 127.0.0.1, server: , request: "GET /basic_status HTTP/1.1", host: "127.0.0.1"
    Jun 16 21:02:52 Fileserver nginx: 2023/06/16 21:02:52 [error] 25539#25539: *55367 open() "/usr/local/emhttp/stub_status" failed (2: No such file or directory), client: 127.0.0.1, server: , request: "GET /stub_status HTTP/1.1", host: "localhost"
    Jun 16 21:02:52 Fileserver nginx: 2023/06/16 21:02:52 [error] 25539#25539: *55368 open() "/usr/local/emhttp/stub_status" failed (2: No such file or directory), client: 127.0.0.1, server: , request: "GET /stub_status HTTP/1.1", host: "127.0.0.1"
    Jun 16 21:02:52 Fileserver nginx: 2023/06/16 21:02:52 [error] 25539#25539: *55369 open() "/usr/local/emhttp/nginx_status" failed (2: No such file or directory), client: 127.0.0.1, server: , request: "GET /nginx_status HTTP/1.1", host: "127.0.0.1"
    Jun 16 21:02:52 Fileserver nginx: 2023/06/16 21:02:52 [error] 25539#25539: *55370 open() "/usr/local/emhttp/status" failed (2: No such file or directory), client: 127.0.0.1, server: , request: "GET /status HTTP/1.1", host: "127.0.0.1"
    Jun 16 21:03:01 Fileserver nginx: 2023/06/16 21:03:01 [error] 25539#25539: *55482 open() "/usr/local/emhttp/us" failed (2: No such file or directory), client: 127.0.0.1, server: , request: "GET /us HTTP/1.1", host: "localhost"
    Jun 16 21:03:01 Fileserver nginx: 2023/06/16 21:03:01 [error] 25539#25539: *55483 open() "/usr/local/emhttp/us" failed (2: No such file or directory), client: 127.0.0.1, server: , request: "GET /us HTTP/1.1", host: "127.0.0.1"
    Jun 16 21:03:01 Fileserver nginx: 2023/06/16 21:03:01 [error] 25539#25539: *55484 open() "/usr/local/emhttp/status" failed (2: No such file or directory), client: 127.0.0.1, server: , request: "GET /status?full&json HTTP/1.1", host: "localhost"
    Jun 16 21:03:01 Fileserver nginx: 2023/06/16 21:03:01 [error] 25539#25539: *55485 open() "/usr/local/emhttp/status" failed (2: No such file or directory), client: 127.0.0.1, server: , request: "GET /status?full&json HTTP/1.1", host: "127.0.0.1"
    Jun 16 21:03:01 Fileserver nginx: 2023/06/16 21:03:01 [error] 25539#25539: *55486 open() "/usr/local/emhttp/status" failed (2: No such file or directory), client: ::1, server: , request: "GET /status?full&json HTTP/1.1", host: "[::1]"

     

    Please post new diagnostics with your array halted and in safe mode.

     

     

    New diagnostics added. All plugins up to date

    fileserver-diagnostics-20230618-1914.zip

    Link to comment

    I have the same issue (I am using Firefox and all the scaling is 100%, at 1920 x 1080 resolution), the only temporary solution I found is to zoom out in the browser to 90% instead of a 100%.

    Link to comment
    On 6/19/2023 at 5:14 PM, Sulaiman said:

    I have the same issue (I am using Firefox and all the scaling is 100%, at 1920 x 1080 resolution), the only temporary solution I found is to zoom out in the browser to 90% instead of a 100%.

     

    Not really the solution, but, yeah, that's the only workaround for now. Unfortunately, this also changes the zoom of other tabs that have the same base url. And thereby partially makes the UI of the other tabs unusable. Alternatively, you could open a whole new browser window. But that's not a long-term solution either. I reverted to 6.11.5 until there is a fix for this.

    Edited by ezek1el3000
    Link to comment

    The scaling i.e width of each panel has definitely changed. Maybe someone added to much padding or something. 

     

    Here's a screenshot with a big display 3024 x 1964 so it should have 3 columns.

     

    But anyway as mentioned above if you use chrome and zoom out to 90% it displays 3 columns. 

     

     

    Screenshot 2023-06-20 at 19.51.08.png

    Edited by dopeytree
    Link to comment

    ...and if you increase the width of the browser and then reduce it again (simply slide the right edge of the browser to the left and right), the content is no longer displayed correctly.

    You have to reload the page.70024689_2023-06-2023_24_48-Holzgerlingen_Dashboard-Brave.thumb.png.1f0b57b487855c3bfb2346a8a0eb7017.png

    Link to comment
    On 6/21/2023 at 9:44 AM, Masterwishx said:

    its working After reset button + scale to 90% from 110% in my case 2560x1440 screen , in 6.11.5 i think was 3 column in 110%

    Sadly not working for me...

    Link to comment

    6.12.2 is released

     

    webgui: Dashboard updates:
        Reduce gap between columns

     

    does it fix our issues? Did anyone had the chance to test it?

    Link to comment
    10 hours ago, ezek1el3000 said:

    6.12.2 is released

     

    webgui: Dashboard updates:
        Reduce gap between columns

     

    does it fix our issues? Did anyone had the chance to test it?

    I'll test it out now, will update in 10-15 minutes. 

     

    Update: not fixed (for me atleast)

    Update 2: it seems that when I put my browser on full screen (I've had it on 75% of a 2560x1440 for years and never had problems) it does go 'back' to the old 3 columns layout... 

    Edited by TristanDK
    Link to comment



    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.
    Note: Your post will require moderator approval before it will be visible.

    Guest
    Add a comment...

    ×   Pasted as rich text.   Restore formatting

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.


  • Status Definitions

     

    Open = Under consideration.

     

    Solved = The issue has been resolved.

     

    Solved version = The issue has been resolved in the indicated release version.

     

    Closed = Feedback or opinion better posted on our forum for discussion. Also for reports we cannot reproduce or need more information. In this case just add a comment and we will review it again.

     

    Retest = Please retest in latest release.


    Priority Definitions

     

    Minor = Something not working correctly.

     

    Urgent = Server crash, data loss, or other showstopper.

     

    Annoyance = Doesn't affect functionality but should be fixed.

     

    Other = Announcement or other non-issue.