@Sebastian-Roth Yeah, I just added an edit section to my previous post. This thread popped up with no responses after 19 hours. I didn’t understand how I missed this for 19 hours that’s why my response was a bit random, I was starting at the beginning. Very strange.

Thanks that worked!

@Reagan said:

Are these commands something I need to run every time I upgrade the FOG server?

Well that’s a good question. No, from my point of view, if you don’t recreate the certificates (extra installer parameters - shouldn’t use if you don’t know exactly what you do anyway) or move to use your own custom certificates (from an official or internal certificate authority), there is no need to rerun the build script.

By the way, I opened an issue to include the build process to the installer, so this manual run won’t be needed anymore. This will be part of the next official release.

Super that did work… thanks guys

Okay, everyone, I found the reason why it wasn’t working. @george1421 and @Sebastian-Roth it was NOT because I used /image1. It was a complete dumb reason!

I set up the server, that every HTTP traffic gets redirected to HTTPS. My dumb mistake: I forgot to setup SSL on the NODE! So it looks like that because I used https://fog.xyz/fog it trys to reach the nodes via SSL as well! After setting up SSL on the node, Boom:

743cb9f1-d24b-43be-9b87-02b945e58a28-image.png

So sorry for directing you on a complete wrong path 🙈

@Critchleyb Did you come to a conclusion with this or got a little further with the commands and ideas provided?

ok that was it… My server is back online after the updates. thank you so much.
.fogsettings changed the package to libcurl4 because the install was not a fresh install.

got it now thank you so much for the fast response.
Bill

@Sebastian-Roth Well I feel silly, I should’ve done that to start. Apologies for the stupid question, thanks and once backups are done updates are next on the list.

Yes.
Tasked Successfully
Task Wake-Up Successfully created!
Created Tasks For
“hostname”

@Sebastian-Roth Ok, it sounds good that things are looking normal, and I can wait on doing an update. I see your reasoning and agree with that philosophy, on step at a time. I’m also three days away from the semester start so have limited time to troubleshoot and communicate here. I have run a few test images and may have figured something out, I need to complete my testing and will let you know. Thanks again, this has all been so helpful!

@Tom-Elliott said in db_root: cannot open: /etc/target:

@kboutelle There’s the problem.

You have /images and /images2 mounting to the same File system ID. I believe nfs will use the 1st instance (in your case it’s mounting /images rather than your new share /images2.

Edit the /etc/exports file.

For your /images and /images/dev lines, prepend them with a # symbol. This will comment those lines.

That, or change the fsid of the /images2 and /images2/dev to have 2 and 3 respectively.

Then restart the nfs service, systemctl restart nfsd

I can’t believe I missed that. Edited, going to try again.

Deployment is proceeding as it should.

Thank you all for taking the time to help.

@Rhywden said in Error while installing FOG on Ubuntu 18.04:

I tried it on both Debian 8 and Ubuntu 18.04

We have automatic daily installer test running and there is no general issue with Debian or Ubuntu I can assure you.

Make sure that interface is up and has an IP! Run ip a s before running the installer and post output here.

Basically I want to set it up thus that it’s able to connect to an existing network over Wifi.

Ok then you need to configure both interfaces. First WLAN, get an IP and make sure you have internet access through that (ping -c ix.de). Then configure enp6s0 with a static IP and make sure the interface is UP!

ip a s
…
2: enp6s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
…

@Tom-Elliott @Sebastian-Roth Understood, thanks again guys!

@MoonDancer Check out this wiki pages: https://wiki.fogproject.org/wiki/index.php/.fogsettings, https://wiki.fogproject.org/wiki/index.php/Password_Central and https://wiki.fogproject.org/wiki/index.php/Troubleshoot_FTP

Well if I reread your post through a different lens…

When you pxe boot through the fog iPXE boot menu and let the default “Boot to hard drive” menu happen, when windows starts the iPXE dhcp name is still in place and windows is happy to just use that lease. If this is the case then iPXE might not be releasing the dhcp lease when it boots from the hard drive. In this case its not clear who is at fault (iPXE or Windows for just reusing what was there)?

Hi @quinniedid ,

In this post you can find info about how works and how create rules in this plugin.

https://forums.fogproject.org/topic/9624/control-access-plugin/14

With this plugin you can restrict the access to the menus and submenus but not to specific host and groups. To do this maybe you can use the Site plugin but, unfortunately, this plugin doesn’t work with the 1.5.5 version. I am working to fix the bugs.

@george1421 Oh, my apologies. Thank you very much for your help. You’re truly a wizard as your profile picture shows. 😉 Thank you again!

@Sebastian-Roth I’m not seeing image definition. If you mean under Image General after opening an image and changing one of the properties to any of the settings then that did not work either.

I was able to export the images and import them to the new server after I RSYNC’d the images.

I’m good now.