• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login

    v1.5.5 with https and fog client

    Scheduled Pinned Locked Moved Solved
    FOG Problems
    2
    3
    295
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • A
      Antonio
      last edited by

      Hello, thanks for Fog Project and all your big work on it.

      I’m testing FOG Project v1.5.5 with https and I have a problem with fog client.

      Well, i’m not sure if https causes the problem, but when I do an installation without it the client agent works correctly.

      I follow these steps in htpps installation:
      ./installfog.sh --force-https
      and when it finishes:
      utils/FOGiPXE/buildipxe.sh

      The MD5 sums match in:
      openssl rsa -modulus -noout -in /opt/fog/snapins/ssl/.srvprivate.key | openssl md5
      openssl x509 -modulus -noout -in /var/www/fog/management/other/ssl/srvpublic.crt | openssl md5

      The host is created on the server with “Perform Full Host Registration” on boot. I think all its fields in the DB are correct, MAC especially.

      On client fog.log appears “Invalid MAC address format” constantly on Authentication section:
      …
      Data::RSA FOG Server CA cert found
      Middleware::Authentication Cert OK
      Middleware::Communication POST URL: http://XXX.XX.XX.XX/fog/management/index.php?sub=requestClientInfo&authorize&newService
      Middleware::Response Invalid MAC address format
      Middleware::Response Success
      …
      After that, in all sections:
      Middleware::Response ERROR: Unable to get subsection
      Middleware::Response ERROR: Referencia a objeto no establecida como instancia de un objeto.

      I “Reset Encription Data” on host (when the button appears in it), creating a group with it and manually on DB too.

      MAC is correct in DB. I tried putting manually host in the server and get the same problem.

      Using debugger.exe command “middleware authentication handshake” I get:

      • Middleware : Authentication Error: Could not get security token
      • Middleware : Authentication Error: Clave no válida para utilizar en el estado actual

      There’s a file named token.dat in fog directory of client with current date.

      Now i’m not sure if all my steps in the installation were correct and I’m lost, I don’t know what try, change,… :S

      Thanks in advance 🙂

      1 Reply Last reply Reply Quote 0
      • S
        Sebastian Roth Moderator
        last edited by Sebastian Roth

        @Antonio said in v1.5.5 with https and fog client:

        Middleware::Communication POST URL: http://XXX.XX.XX.XX…

        See the URL is not HTTPS. You need to modify the client’s setting file C:\Program Files (x86)\FOG\settings.json and set HTTPS to 1.

        I know we should update the fog-client installer to reflect this option on the GUI installer as well but for now you can use installer parameters to set the option.

        As well the “Invalid MAC address format” is missleading. Sorry for that.

        Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

        Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

        1 Reply Last reply Reply Quote 0
        • A
          Antonio
          last edited by

          Now it works perfectly, thanks!

          1 Reply Last reply Reply Quote 0
          • 1 / 1
          • First post
            Last post

          155

          Online

          12.1k

          Users

          17.3k

          Topics

          155.3k

          Posts
          Copyright © 2012-2024 FOG Project