#286 Run web service on custom port

Peter Zingg

I would like to run (actually I am running) the Fog web management/status interface on a port other than port 80. Main things that seem to break are:

1. Global setting FOG_WEB_HOST could take optional [:port] if it doesn't break things
2. Global setting FOG_WOL_HOST could take optional [:port] if it doesn't break things
3. ngmHostName column in nfsGroupMembers table used to build URLs in at least three files:
a. /web/status/freespace.php
b. /web/management/includes/hwinfo.include.php
c. /web/management/ajax/dashboard.bandwidth.php

Perhaps adding FOG_WEB_PORT and FOG_WOL_PORT settings and using it where necessary could allow this.


  • Peter Zingg

    Peter Zingg - 2011-11-21

    On my local running installation, I added changes to these files:


    define( "FOG_WEB_PORT", ":88" );
    define( "FOG_WOL_PORT", ":88" );

    and included the (local) settings in the URLs that are set up in various functions.

  • Peter Zingg

    Peter Zingg - 2011-11-21

    I forgot about the other problem with a non-standard port. The /tftpboot/pxelinux.cfg/default menu file sets a "web" environment variable for the fog imaging process. This variable is then used to "checkin" with the fog managment server to update the status of the imaging task.

    The pxelinux.cfg/default file is built out of the OS-specific functions.sh files:
    /lib/ubuntu/functions.sh or

    So these files would have to be modified also to include a non-standard port. I will try this out locally in my pxelinux.cfg/default file.

  • Peter Zingg

    Peter Zingg - 2011-11-22

    Finally understood where pxelinux.cfg files get created in Fog web service, so I am attaching a patch file to the v0.32 tarball that contains all my changes.


Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

No, thanks