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

    Unable to reach Fog Management website

    Scheduled Pinned Locked Moved General Problems
    14 Posts 3 Posters 4.9k Views
    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.
    • george1421G
      george1421 Moderator @Jarl2.0
      last edited by

      @jarl2-0 Well that’s pretty unimpressive. It just tells me the http server was shutting down. If you start the http server up again and try to access the management console does it append anything to the error log? It should be throwing some errors if you try to access the management page but only get a white (blank) page.

      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!

      J 1 Reply Last reply Reply Quote 0
      • J
        Jarl2.0 @george1421
        last edited by

        @george1421 It doesn’t the page comes up connection timed out and I don’t see any connection attempts on the apache logs.

        george1421G 1 Reply Last reply Reply Quote 0
        • george1421G
          george1421 Moderator @Jarl2.0
          last edited by george1421

          @jarl2-0 Ah, OK then lets try this.

          ps aux|grep apache to confirm that the apache process is running
          You should see something like this

          www-data 21806  0.0  0.7 106732  7236 ?        S    06:25   0:00 /usr/sbin/apache2 -k start
          www-data 21807  0.0  0.7 106732  7236 ?        S    06:25   0:00 /usr/sbin/apache2 -k start
          www-data 21808  0.0  0.7 106732  7236 ?        S    06:25   0:00 /usr/sbin/apache2 -k start
          www-data 21809  0.0  0.7 106732  7236 ?        S    06:25   0:00 /usr/sbin/apache2 -k start
          www-data 21810  0.0  0.7 106732  7236 ?        S    06:25   0:00 /usr/sbin/apache2 -k start
          

          netstat -an | grep 80 to confirm that the apache server is listening
          You should see something like this:

          tcp       0      0 :::80                   :::*                    LISTEN   
          

          systemctl status firewalld to see if the firewall is on by chance.

          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!

          J 1 Reply Last reply Reply Quote 1
          • J
            Jarl2.0 @george1421
            last edited by Jarl2.0

            @george1421 Output from the grep command
            0_1503348086684_apache.PNG

            Output from netstat
            0_1503348102270_netstat.PNG

            No firewall service is running.

            george1421G 2 Replies Last reply Reply Quote 0
            • S
              Sebastian Roth Moderator
              last edited by Sebastian Roth

              @Jarl2-0 Please run sudo iptables -L -n -v and post a picture here. Just wanna make sure…

              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
              • george1421G
                george1421 Moderator @Jarl2.0
                last edited by

                @jarl2-0 This is really strange.

                Apache is running, its listening on port 80 and yet you are getting a connection timeout. Something is not adding up. For the management gui access are you using the ip address of the fog server or a conical name?

                I’m going to confirm a curl call to see if we can call the management page from the linux server console. One sec while I confirm it does what I think I want it to.

                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!

                1 Reply Last reply Reply Quote 0
                • george1421G
                  george1421 Moderator @Jarl2.0
                  last edited by

                  @jarl2-0 OK from the fog server linux console key in the following command.

                  curl "http://127.0.0.1/fog/management/index.php"
                  This is going to return a screen full of html code. This is a good thing. If we get a timeout then that will tell us something else.

                  Then repeat the same process with the fog server’s IP address.
                  curl "http://<fog_server_ip>/fog/management/index.php"

                  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!

                  J 1 Reply Last reply Reply Quote 0
                  • J
                    Jarl2.0 @george1421
                    last edited by

                    @george1421

                    I connect to it via IP normally.

                    Curling localhost and IP I got an HTML dump.

                    @Sebastian-Roth the output was really long so I dumped it into a text file and copied it to pastebin. https://pastebin.com/DAUPa0F8

                    george1421G 1 Reply Last reply Reply Quote 0
                    • george1421G
                      george1421 Moderator @Jarl2.0
                      last edited by

                      @jarl2-0 well your pastbin file shows that the firewall rules are loaded into iptables.

                      You should see this if the firewall has been disabled.

                      # iptables -L -n -v
                      
                      Chain INPUT (policy ACCEPT 2968 packets, 899K bytes)
                       pkts bytes target     prot opt in     out     source               destination         
                      
                      Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
                       pkts bytes target     prot opt in     out     source               destination         
                      
                      Chain OUTPUT (policy ACCEPT 3137 packets, 471K bytes)
                       pkts bytes target     prot opt in     out     source               destination         
                      

                      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!

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

                        @Jarl2-0 As George already said, the firewall rules are the issue in your case. There is no rule to allow incoming packets on port 80 (HTTP) and default policy is drop… For now, try sudo ufw disable and see if you get back the FOG web UI.

                        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

                        J 1 Reply Last reply Reply Quote 0
                        • J
                          Jarl2.0 @Sebastian Roth
                          last edited by

                          @sebastian-roth That worked I have no idea how those rules got loaded onto the firewall however…

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

                          104

                          Online

                          12.3k

                          Users

                          17.4k

                          Topics

                          155.7k

                          Posts
                          Copyright © 2012-2025 FOG Project