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

Redirecting http/https requests to /fog causes client smartinstaller to fail

Scheduled Pinned Locked Moved Solved
FOG Problems
3
3
1.0k
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.
  • K
    kylebeth94
    last edited by kylebeth94 Apr 7, 2017, 3:11 PM Apr 7, 2017, 9:09 PM

    Server
    • FOG Version: 1.3.5
    • OS: Ubuntu 16.04 LTS
    Client
    • Service Version:
    • OS:
    Description

    Creating a http/https redirect to make the root directory of the web server /fog causes the installer to break when entering the correct hostname and changing the directory from /fog to /

    Is there a specific way to get this redirect to work correctly?

    W 1 Reply Last reply Apr 7, 2017, 9:41 PM Reply Quote 0
    • W
      Wayne Workman @kylebeth94
      last edited by Wayne Workman Apr 7, 2017, 3:44 PM Apr 7, 2017, 9:41 PM

      @kylebeth94 Yes, use the webroot argument to point to the correct spot.
      https://wiki.fogproject.org/wiki/index.php?title=FOG_Client#FOG_Client_0.10.0.2B_Installation_Options
      If this doesn’t work - this likely means some paths are hardcoded somewhere - and that’d be something that @Senior-Developers would need to find in either the fog server or fog client.

      Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!
      Daily Clean Installation Results:
      https://fogtesting.fogproject.us/
      FOG Reporting:
      https://fog-external-reporting-results.fogproject.us/

      1 Reply Last reply Reply Quote 0
      • J
        Joe Schmitt Senior Developer
        last edited by Joe Schmitt Apr 7, 2017, 3:47 PM Apr 7, 2017, 9:45 PM

        @kylebeth94 the client does not follow 301 / 302 http codes (redirects). I run one of my development servers on https, and with a webroot of /. You’ll need to configure your webserver to serve out / without using redirects. You can redirect http to https traffic if you desire, but just make sure the client is set to use https then.

        Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.

        1 Reply Last reply Reply Quote 1
        • 1 / 1
        1 / 1
        • First post
          2/3
          Last post

        181

        Online

        12.2k

        Users

        17.3k

        Topics

        155.5k

        Posts
        Copyright © 2012-2024 FOG Project