@d2freak82 said in Certificate Nightmare:
on install if I select HTTPS it will not install because of the certificate error.
Even when using the updated SmartInstaller mentioned below?
Where exactly do you see the certificate error? Can you post a screenshot? Possibly it’s something we can/need to fix in the fog-client setup.
@b_man said in GParted Live from FOG:
kernel tftp://${fog-ip}/iso/gparted/live/vmlinuz vmlinuz boot=live ...
Do you have the ISO file extracted to /tftpboot/iso/gparted/ on your FOG server?
@george1421 By the way, do you think the double ... vmlinuz vmlinuz ... in that line is correct? I don’t think it’s causing an issue but nevertheless stumbled upon this.
@keroseni said in NBP Downloaded Successfully:
option 66 has undionly.kpxe configured and option 67 has the FOG IP address
You mean vice versa, right? Option 67 is for the filename.
@Greg-Plamondon From what I read you can’t really install the kiosk client. Maybe I missed that part. But the FAQ states that you can customize the ISO file.
For PXE booting, have you tried memdisk iso booting yet? Thou this is legacy BIOS mode only:
initrd http://${fog-ip}/path/to/porteus.iso
chain memdisk iso raw
boot || goto MENU
Edit: Quickly extracted the ISO and found this in boot/pxelinux.cfg/default:
label pxe
kernel vmlinuz
append initrd=initrd.xz,pxelinux.cfg/initrdpxe.xz quiet http_server=
So you might be able to boot the extracted ISO. But on the other hand we don’t know too much about the kernel parameters for network booting this beside the litte information on their website: https://porteus-kiosk.org/pxe-server.html
Be aware that FOG is not using pxelinux anymore. We use iPXE now and while you can do many more things with iPXE it’s not always possible to translate things over from the old pxelinux.
@Keroseni This sounds like you are mixing legacy BIOS mode and UEFI mode. What is serving DHCP in your network? What is DHCP option 67 set to? For legacy BIOS you use undionly.kkpxe or undionly.kpxe or ipxe.pxe but for UEFI it’s ipxe.efi or snponly.efi.
Also see: https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence
@sborgne said in (503) Service unavailable:
Proxy parameters bad config is to be blamed…
Wow, something I would not have thought of right away! Good you found why it fails!
No there are no proxy configuration settings in fog-client. We use simple C# .NET WebClient calls. That seams to be using your system proxy settings. Can you set your systemwide proxy settings to not use the proxy server if connecting to your FOG server?
@d2freak82 Does it work in the end using the new fog-client version? I am not sure I understand the baseline of what you say.
@john3892 As you see your version of FOG is way newer than the one of the original post here, so please open a new topic and post all your details there.
@SCavender Ahh, I didn’t notice the gateway (in DHCP) is set to your FOG server IP 192.168.22.11 when looking at the dhcpd.conf. Are you sure this is what you want? From what you said so far I would think you want the router to be 192.168.22.1.
If your FOG server is meant to be a gateway it needs things like IP forwarding in the kernel enabled and iptables rules to pass packets through. Not something we provide with the FOG installer.
While looking at the dhcpd.conf once again I also notice that you might wand to change the line range dynamic-bootp 192.168.22.10 192.168.22.254; because the range starts at 10 but your FOG server is at 11. Make it start at 20 for example to prevent from duplicate IP issues.
Make sure you also change the values in /opt/fog/.fogsettings so the installer won’t reset things on the next upgrade!
After changing the config you need to restart the DHCP service or your FOG server altogether.
@mesaman0182 Thanks to @Tom-Elliott this is fixed in dev-branch. So if you want to install FOG on Ubuntu 21.04 you just need to use the latest dev-branch version from github.
@john3892 Best if you open a new topic. Just cross link this forum post here as reference and then send all your details like FOG version, Linux OS/version, steps you took (in detail)…
@tom-elliott said in Dev branch 1.5.9.79 Installing package: php-gettext.............................Failed! has to use -X switch to get it to work.:
in my testing language translation worked properly using the common provided version
Then it’s all fine. Good that we don’t need that extra package anymore! 
@SCavender When you boot up a client, please run ipconfig /all in Windows CMD, take a picture and post here.
Just want to see if it receives the DNS server information from the DHCP or not.
@d2freak82 From the little information we have so far I would expect you run into the issue where Ubuntu started disabling TLSv1.0 and TSLv1.1 in the Apache configuration. Find more details on this here: https://forums.fogproject.org/topic/15151/fog-client-installation-error-cannot-install-ca-certificate
An updated and fixed fog-client installer is available: https://github.com/FOGProject/fog-client/releases/download/0.12.0/SmartInstaller_fixed-tls.exe
@tom-elliott said in Dev branch 1.5.9.79 Installing package: php-gettext.............................Failed! has to use -X switch to get it to work.:
Issue is ubuntu 21.04 is using php{ver}-common for php-gettext where in the past it was its own package.
When I was looking at this I got the impression the new package is named php-php-gettext (see package repo).
When searching for php-gettext in general (link to search) I find this:
bionic (18.04LTS) (web): transitional dummy package for php-php-gettext [universe]
1.0.12-0.1: all
You are absolutely right, the PHP gettext module is now part of php7.4-common but the mentioned php-php-gettext provides some helper PHP/INC files - not sure if we need those.
@scavender said in No Subnet Declaration for virbr0 After Upgrade to 1.5.9:
192.168.22.1 is the Gateway IP/Subnet for the VLAN 22
Does this gateway provide DNS as well? Either as a DNS service or by relaying the DNS queries to an upstream DNS server?
@cf20corvuss I suppose your are using VirtualBox, right? This is a known issue. If you shutdown the VM and “cold start” it up the issue does not happen.
A quick fix is to change your DHCP config to send ipxe.pxe (instead of the default undionly.kkpxe).
@george1421 said in One central FOG server plus multiple Storage nodes in different locations possible?:
You can only capture images to the central server. The storage nodes are deploy only.
This is the most important point I think. From what @tesparza said so far it sounds as if image capture to storage nodes is wanted.
@scavender said in No Subnet Declaration for virbr0 After Upgrade to 1.5.9:
Yes, I am using eth0 and DHCP works great. The problem is the clients don’t have internet access. They can ping external sites but webpages don’t load/resolve.
Sounds like a DNS issue. In the DHCP service config you have option domain-name-servers 192.168.22.1; - is this the correct DNS server in this subnet?
@DiscoNaut While you surely can mess with the port in the Apache config I am fairly sure this will break some of FOG’s features like wake on LAN, snapins and maybe even PXE booting. Will definitely take some manual adjustments in files in the FOG server to get this somehow working.
What’s your intend in doing this?