• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. filisdiez
    3. Topics
    F
    • Profile
    • Following 0
    • Followers 0
    • Topics 4
    • Posts 15
    • Best 0
    • Controversial 0
    • Groups 0

    Topics created by filisdiez

    • F

      Solved Operation not permitted?

      FOG Problems
      • • • filisdiez
      3
      0
      Votes
      3
      Posts
      330
      Views

      F

      @george1421 Yes, really because of the substitution of certificates! Reinstalled fog and everything worked. https I was offered to enable the fog installer.

    • F

      Problem with new FOG 1.5.9 installation

      FOG Problems
      • • • filisdiez
      4
      0
      Votes
      4
      Posts
      2.1k
      Views

      S

      @belac said in Problem with new FOG 1.5.9 installation:

      manually update
      on all your storage nodes

      This is not for your FOG master node. Hope you have a copy of the old fogsettings file or we might be able to get the last fogmaster DB credentials from a backup of the config.class.php file in /home/fog_web_1.5.9.BACKUP/…

    • F

      ipxe https

      General
      • • • filisdiez
      12
      0
      Votes
      12
      Posts
      672
      Views

      Q

      You’re trying to pull something from the images folder over https, but https isn’t configured to serve that location.

      Think more along the lines of /var/www/fog

    • F

      problem Quick and full registration

      FOG Problems
      • • • filisdiez
      12
      0
      Votes
      12
      Posts
      2.3k
      Views

      S

      @filisdiez This is for sure not a general FOG problem as we don’t have other users reporting this as far as I know. I can’t replicate this issue either. So I am fairly sure this is something within your environment. Try opening the URL I posted for all the FOG servers you have and see if you always get the proper version printed in the browser.

      Looks this could be some kind of HTTP redirect issue. Maybe try this: tail -f /var/log/apache2/*.log (or for CentOS/Redhat: tail -f /var/log/httpd/*_log). Then boot up a client for registration and keep an eye on the logs the moment you see the error on the client screen. Stop the tail log (Ctrl+c) right after you saw the error on the client screen and post a picture of the logs here.

    • 1 / 1