@Tom-Elliott helped out, it was a bug in replication. It should be fixed in the current.

@redbob said in Cannot enter FOG Web Interface: “Not Allowed Here”:

I cannot access Ondrej repository due to firewall issues!!!

You should request that the site be allowed. This is an open source repository for used for Linux package install and patching purposes - there’s no reason to block it.

We need to know what OS and version your FOG server is running on.

@unknownhost99 This video on Debian 8 will also work for Debian 9: https://wiki.fogproject.org/wiki/index.php?title=Debian_8
The video is very educational, I take the time to explain Linux partitioning and other things. It’s meant for newcomers to Linux like yourself.

@WelbyAdmin I agree, I think it’s the image. it worked fine in 0.32? If so, you could build a 0.32 server quickly and just copy over the image, make the definition for it appropriately, and then restore to a computer - then upload that to the new server.

That might work.

Another option is to rebuild the image.

Pay attention to this thread, others may chime in with better advice.

@cmcgonag sounds a lot like you are in need of a customized embedded linux os to do some sort of jobs. There are better ways to do this than using fog and Ubuntu. You should look into the Yocto project or a customized copy of Debian.

@Osayidan You’d accomplish it in Web interface -> FOG Configuration -> new iPXE This area is where you’d create the new entry.

The boot.php file mentioned in the article was intended to be viewed via a web browser, not locally on the server itself. Visiting the URL in a web browser allows you to see what the iPXE script looks like in total for an un-registered host after making changes to the menu via the web interface. To view what it looks like for a registered host, append ?mac=TheHostsMacWithColonsHere to the URL.

@eadhor Be sure to set the database username and password inside of /opt/fog/.fogsettings or you’re bound to break stuff later on when you upgrade (promise).

Change settings for fog inside of the fogsettings file, then re-run the installer for those settings to take effect. Here’s documentation about the file:
https://wiki.fogproject.org/wiki/index.php?title=.fogsettings

The settings you need to change are these:

snmysqluser=''
snmysqlpass=''

Put the correct values into them, save, then re-run the installer.

mysql
use fog
SELECT pxeID, pxeName, pxeDesc FROM pxeMenu WHERE pxeDesc = 'Boot CD 15.2';

That should return the row that you didn’t fill out completely, including the ID. If it does return the right row you can then delete that entry by ID.

Be sure to replace the ID number in this command!

DELETE FROM pxeMenu WHERE pxeID = '0';

@loosus456 said in Is supporting Secure Boot now possible?:

Would each and every version of iPXE have to be signed by Microsoft?

Yes, any version you want Secure Boot to accept must be signed. The idea we’ve kicked around before is only doing this every so often to minimize costs.

@lukebarone Those come with FOG Trunk. Try the other files I mentioned.

I think all the PXE binaries and FOS need compiled for ARM for this to work??

For future readers, the issue was an FTP problem, and everything you need to solve this is in the below article:
https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_FTP

@lubo Using the FTP credentials, simply log in via actual FTP, and do an ls to see where you are. Wherever you ‘plop’ into, that’s your FTP root. Taking that into consideration, you need to adjust FOG’s FTP Path to start at the ftp root -> to the images directory. If that makes sense. Also, could be a simple permissions issue too.

Can we get a copy of the .bat file? Remove IPs and replace with x.x.x.x and remove usernames and replace with UserNameGoesHere and passwords with PasswordGoesHere

@flipwalker As others have already said, it should work fine and be much faster. Setup a fog server and give it a go. We’ll help you with any bumps you hit - create a new thread for each bump.

@Scott-Adams the xcopy command is using the locally logged in user when you run it manually, and is using SYSTEM when snapins run it. You have to specify credentials, or set the share to read-only for “everyone”.

@foglalt I put together a script:
https://github.com/wayneworkman/fog-community-scripts/blob/master/troubleshootingTools/monitor-missing-primary-mac.sh
For future readers, this script will be here in the troubleshooting tools:
https://github.com/FOGProject/fog-community-scripts

It monitors the count of hosts that are missing a primary mac. If the count goes above 0, it gets those host IDs, the last 100 lines of the apache access log, the last 100 lines of the apache error log, and the last 50 entires from FOG’s history table and dumps them to the file /root/troubleshooting.log
Once that log file is written to, the script will not write anything else.

Get the script onto your fog server, and then you will need to setup this script to run as a cron task every minute on your FOG Server. There’s lots of tutorials if you google search cron or crontab but generally steps are as follows:

sudo -i
crontab -e     # this might ask you if you want to use vim basic or vim tiny, it doesn't matter which.

# Go into insert mode with:
i

# Paste in the below line:
* * * * * /root/monitor-missing-primary-mac.sh        # Or wherever you put the script.

# Leave insert mode with the escape key
esc

# Save and close in vim with
:wq

There are probably better tutorials out there on how to use Vim & create a cron job, but I put together this little Vim tutorial some years ago:
https://wiki.fogproject.org/wiki/index.php?title=Vi

If you need further instructions/clarification on how to setup the script, just ask. When the file /root/troubleshooting.log appears on your server, just look through it yourself first - remove any sensitive information. Maybe this file will help you figure out the bug yourself even. If not, you can share the file here with us and we can probably get a very good idea on how to reproduce this issue.

@maveriick You don’t need to install any of that stuff manually.

You simply need to install svn, and then pull the trunk repo. Then the FOG installer will do everything else for you when you run it.

There are step-by-step instructions in the upgrade to trunk article, here:
https://wiki.fogproject.org/wiki/index.php?title=Upgrade_to_trunk

@foglalt said in Disappearing hosts from host list:

Why post is solved?

Because we found a solution that fixed the problem earlier, and I marked that post as a solution. Now we are continuing in this same thread because it’s the same problem, trying to find the root cause to this issue. We can ask the @moderators to mark the thread as unsolved I suppose.