• Database Error when select a group

    Moved Unsolved
    8
    1 Votes
    8 Posts
    784 Views
    Tom ElliottT

    @mashina Ah, thank you for that and sorry for my denseness. Indeed this is a bug and I’ve replicated and figured out where this is occurring.

    I have pushed a few mroe adjustments in an attempt find and fix more bugs (thanks AI review and whatnot)

    Please pull and let me know if there’s any other issues.

  • FOG 1.5.10.1698 - UI bugs

    Unsolved
    2
    0 Votes
    2 Posts
    333 Views
    M

    Okay - So what killled this installation was the fact a 1.5.9 csv load was imported into my 1.5.10.1698 FOG - this killed a bunch of features and I eded up having to reinstall.

  • Version 1.5.10.1763 incorrect Image Size ON CLIENT

    Unsolved
    3
    0 Votes
    3 Posts
    235 Views
    H

    @rodluz yes, directly from 1.5.10.1754 to 1.5.10.1763 when I saw the prompt in the FOG gui that I’m not using the latest version - it was up to date before.

    in 1.5.10.1754 recapture didn’t added up, just updated the image size to the latest one.

  • Fog 1.6.0-beta.2141 remove folder with image

    Unsolved
    4
    0 Votes
    4 Posts
    717 Views
    S

    Every time after updating to a new build, the first image works, but the next one doesn’t.

  • Phantom Tasks after Host Deletion

    Unsolved
    6
    0 Votes
    6 Posts
    597 Views
    Tom ElliottT

    @Clebboii Following up if you’d be willing to let us know?

    Thank you!

  • FOG 1.5.10.1734 - Kernel panic on Dell Precision 3590 hosts while syncing

    Unsolved
    2
    0 Votes
    2 Posts
    452 Views
    DBailey635D

    Also occurring on Dell Latitude 5450 laptops.

  • Fog 1.6.0-beta.2268 Could not verify mount point

    Solved
    2
    0 Votes
    2 Posts
    414 Views
    S

    @sgennadi
    Fixed by
    touch /images/dev/.mntcheck

  • Fog 1.6.0-beta.2262 Create Task successful but no Active / Scheduled Task

    Solved
    7
    0 Votes
    7 Posts
    1k Views
    S

    Can you help me with bug topic ?
    Fog 1.6.0-beta.2141 remove folder with image

  • Group Client Settings - Enforce Hostname/AD Reboots - working-1.6

    Solved
    6
    0 Votes
    6 Posts
    773 Views
    A

    @Tom-Elliott Cheers, works as expected now!

  • Group AD Settings fails to save - working-1.6

    Solved
    2
    0 Votes
    2 Posts
    252 Views
    No one has replied
  • QuickReg Fails to Image - Invalid Login

    Solved
    7
    0 Votes
    7 Posts
    531 Views
    Tom ElliottT

    Thank you!

  • Change FOG Settings in working-1.6 not working

    Solved
    7
    0 Votes
    7 Posts
    965 Views
    A

    Ok, nevermind, did the git thing, got it working, cheers 🙂

  • refind.conf issue after upgrade to working-1.6

    Solved
    3
    0 Votes
    3 Posts
    382 Views
    A

    @Tom-Elliott cheers - looks like someone changed working branch in 2019 to add hdbios, and it’s not something that’s in the dev branch either!

  • [Problem] Storage Node connection issues after updating to FOG 1.6

    Unsolved
    5
    0 Votes
    5 Posts
    1k Views
    F

    @Tom-Elliott Thanks, going to switch back to 1.6 very soon.

  • rocky linux 9.6 quirks & php 8

    Unsolved
    4
    0 Votes
    4 Posts
    964 Views
    Tom ElliottT

    @mrowand The whole point of the checkAuthAndCSRF is to prevent unauthorized access. Based on the message I’m seeing, the 403 forbidden is happening because it’s crossing origin to get the data or the CSRF token isn’t passing correctly:

    Here’s the code that validates:

    // Optional defense-in-depth: Origin/Referer check for state-changing requests public static function checkOrigin(array $allowedOrigins): void { $method = strtoupper($_SERVER['REQUEST_METHOD'] ?? 'GET'); if (!in_array($method, ['POST','PUT','PATCH','DELETE'], true)) { return; } $origin = $_SERVER['HTTP_ORIGIN'] ?? null; $referer = $_SERVER['HTTP_REFERER'] ?? null; if ($origin) { foreach ($allowedOrigins as $allowed) { if (stripos($origin, $allowed) === 0) { return; } } http_response_code(403); echo _('Forbidden (disallowed Origin)'); exit; } elseif ($referer) { foreach ($allowedOrigins as $allowed) { if (stripos($referer, $allowed) === 0) { return; } } http_response_code(403); echo _('Forbidden (disallowed Referer)'); exit; } // If neither header is present, you can decide to be strict or lenient. // Often lenient to avoid breaking weird client setups. }

    I suspect your console has more information leading to the specific error that was hit.

    ultimately the code is working as expected and there’s something in your environment causing the issue. Now, to be fair, you said you installed Stable, and Dev-branch has a fix of which I admit I missed.

    If you’re willing/able to install the dev-branch I suspect you’ll see this is working much better.

  • Log Viewer not working after update

    Solved
    7
    0 Votes
    7 Posts
    3k Views
    C

    @Tom-Elliott Yes this did work. Thank you for your quick action.

  • FOG Dashboard not accurately showing Active and Available Storage Group Activity

    Unsolved
    2
    0 Votes
    2 Posts
    1k Views
    F

    I’m having the exact same behavior.
    Was working on the 27, 28 and 29.

    Stopped working start of this week (2 september)
    Added 3 storage nodes in between.
    1a07ba58-be68-4007-a60c-5532e6c42e41-image.png

  • 0 Votes
    17 Posts
    4k Views
    Tom ElliottT

    @Fog_Newb probaly just typoed it and i went with it too lol.

  • FOG 1.6.0-beta.2143 - Search no longer working with serial numbers

    Unsolved
    1
    0 Votes
    1 Posts
    429 Views
    No one has replied
  • FOG 1.6.0-beta.2134 - Host won't add automatically

    Solved
    8
    0 Votes
    8 Posts
    1k Views
    S

    @Tom-Elliott the device is showing in pending devices now, thank you!

130

Online

12.6k

Users

17.5k

Topics

156.5k

Posts