The problem was the client version. (old version: 0.9.12)
I had to install the new one on each computer (0.11.9), then reboot each computer.
Then “reset encrypted data” on the group
Now it works fine.
I thought that once there was a new version on the server the client updated “alone”.

@wayne-workman i used " your packages line" and it seems to work.
Then now i have to test pxe boot, capture and deploy !!

THanks for your help

Hello,
in first thank a lot for your answer.
For my test i’m going to work with a virtual machine with only one interface, then forget the “3 networks”
I begin by installing fog like that :
(i use my own dhcp server)

Type d’installation : N
IP du serveur FOG : 192.168.39.243
Would you like to setup a router address for the DHCP server? : n
Would you like to setup a DNS address for the DHCP server and client boot image? : n
Would you like to change the default network interface from eth0? : n
Would you like to use the FOG server for DHCP service? n
This version of FOG has internationalization support, would you like to install the additional language packs? n

My own dhcp server is configured like that (it has 192.168.39.247 for ip address):
subnet 192.168.39.0 netmask 255.255.255.0 {
range 192.168.39.40 192.168.39.230;
option subnet-mask 255.255.255.0;
option broadcast-address 192.168.39.255;
option routers 192.168.39.254;
next-server 192.168.39.247;
filename “pxelinux.0”;
}
then next server is the dhcp server itself

Here is a part of the PXE configuration (on my own dhcp server. (The dhcp server act as dhcp, tftp and pxe server)

DEFAULT vesamenu.c32
KBDMAP fr.kbd
MENU BACKGROUND splash.jpg
menu color title 1;37;40 #ffffffff #00000000 std
menu color timeout_msg 37;40 #80ffffff #00000000 std
menu color timeout 1;31;40 #ffff0000 #00000000 std
menu color border 30;44 #00000000 #00000000 none

TIMEOUT 300
ALLOWOPTIONS 0
PROMPT 0

MENU TITLE MENU
LABEL BootNormal
MENU LABEL Boot local
MENU DEFAULT
COM32 chain.c32
APPEND hd0

LABEL Drivers_Universels
MENU LABEL Drivers Universels
KERNEL memdisk
APPEND keeppxe floppy initrd=ghost/universels.img

LABEL hdt
MENU LABEL Hardware Detection Tool
COM32 hdt/hdt.c32
APPEND modules=hdt/modules.pcimap pciids=hdt/pci.ids

LABEL memtest
MENU LABEL Memtest86+
LINUX hdt/memtest86±4.20.bin

My question is how i could add entry for fog server using ipxe while i’m iusing pxe (pxelinux.0)
Thanks again for your help

Hello, i think i’ve got the same problem except i made modification on the web interface :
i didnt want the “images” directory be at the root (/images)
then i copy the images directory into /home/images.

Then i modify the image path on the web interface, i thought it would modify the export file also but it seems not.

then i had to modify manualy the export file. Now it works fine.
Could it be the problem ?

@need2 now i agree with you : if you accept that mysql root has no password
and if you know that if installer told you to go to http://192.168.39.243/fog it means you have to go to http://192.168.39.243/html/fog.
I know it’s a ridiculous bug of the default installer (without parameters) but it disturbed me

any way fog seems to be a great program, the forum is very reactif and it permit me to go on
Then thanks again for your help i appreciate
sorry for my poor english
@Tom Elliot : i will try with --docroot to tell you if it works.
But can you confirm me that the installer without parameters make a mistake between http://192.168.39.243/fog and http://192.168.39.243/html/fog to be sur we are agree ?

Thanks again for your help everybody !!

@Wayne-Workman said:

@plegrand said:

It’s not our dns servers

You don’t have to use them. You can make your own and direct all hosts to use yours.

I install dynamique DNS with bind and it works fine. Thanks again

@Wayne-Workman
I just made the test unicast (deploy and not multicast)
It’s a room with 12 stations.
2 stations failed
10 works fine (1.6 GB/min)
i’ll tell you more tomorrow

@Jbob Hello
In first sorry for this long delay
I just made the test today with the latest client. Everything seems to work fine !!

@Sebastian-Roth May be i could give you access to this machine if it’s usefull ?

Boot PXE OK
Capture OK
Deploy OK

@Sebastian-Roth
Thank you for your answer.
I didn’t touched anything in the deposits.
I use Fog as it is, without changing anything.
So I will do the update and I will come back here to tell you if everything went well.
Thanks again.

@Sebastian-Roth
Hello,
until now I was using the “dev-branch” branch of git:

git branch -vv
* dev-branch ddb9904a7 [origin/dev-branch] Fix https build failing due to inline tests
 master 171d63724 [origin/master] FOG 1.5.9 Officially Released

For the latest update of fog: 1.5.10, is it better to switch to the master branch?
This is a production server and I don’t want to “break” it.

Once the choice of the branch is made, the update procedure is always the same?

Change the reference branch to master or dev-branch (To be done the first time)
	git checkout master or git checkout dev-branch
Initialize git :
	git init
Update the git repository:
	git pull
Install FOG
cd bin/
./installfog.sh

Thanks for your help.
Pascal

@Tom-Elliott
So no problem to upgrade from 1.5.9.111 (dev-branch) to 1.5.9.235(dev-branch) ?
Thanks

Hello,
I am currently using FOG version 1.5.9.111 (dev-branch).
It seems that the last version of “dev-branch” is 1.5.9.235.

On github I don’t see the changelog concerning this version.
Can I upgrade from 1.5.9.111 to 1.5.9.235 without any problem?
They are minor corrections?
Thanks for your help.
Pascal

When I click this button, if I leave FOG and go back to the same host, the button is displayed again.
But it seemed to me that once I had clicked on this button, it was not supposed to be displayed again for the same host

Hello,
I have a little problem on the web interface.
I have to regularly click on the “reset encryption data” button of some hosts and it seems that this action is not remembered.
What could be the problem?
Thanks for your help
Pascal

@sebastian-roth
I think i 've got the solution :
in fogsettings,

storageLocation was ='/images',

then
/etc/exports was :

/images *(ro,sync,no_wdelay,no_subtree_check,insecure_locks,no_root_squash,insecure,fsid=0)
/images/dev *(rw,async,no_wdelay,no_subtree_check,no_root_squash,insecure,fsid=1)

After correcting fogsettings (storageLocation =‘/home/images’,
/etc/exports :

/home/images *(ro,sync,no_wdelay,no_subtree_check,insecure_locks,no_root_squash,insecure,fsid=0)
/home/images/dev *(rw,async,no_wdelay,no_subtree_check,no_root_squash,insecure,fsid=1)

and it seems to works

@sebastian-roth Hello
The migration is done and I think I followed the documentation.
During a test I encounter the following problem:

Could not mount images folder (/bin/fog.download)
Reason: mount: mounting 192.168.39.243:/home/images/ on /images failed: Permission denied

My images directory is in /home/images.
Do i miss something ?

Hello,
I’m planning to migrate our fog server to a new machine.
The new machine will be configured in the same way.

I had some questions about this migration:

• Is the documentation available at this address still up to date?
  [https://wiki.fogproject.org/wiki/index.php?title=Migrate_FOG](link url)
• The old machine is in version 1.5.9, the new machine, due to installation problems is in version 1.5.9.111.
  Is this a problem? Or do I have to upgrade the old machine to 1.5.9.111?

During tests, I noticed some bugs during the installation of the master branch on a stable debian (bullseye):
The installer tries to install the “php-gettext” package, but this package doesn’t exist anymore and you have to install the “php-php-gettext” package
The installer proposes the installation of certificate, if to the first question it is answered no, to the second question, it is not possible to say no to give a server name for the certificate.
So the installation fails with the stable version

When switching to the dev-branch version, the problems are the same but the installation finishes normally.

Thanks for your help.

@utpalgiriarc
You should install these packages:
php-gettext
php-php-gettext
This is what is installed on my server
Use aptitude or apt to install them.