@Sebastian-Roth I did it and it’s work ! thanks a lot for your reply ans the time you spent for me 🙂

@Sebastian-Roth I added the new lines to my /etc/apache2/sites-enabled/001-fog file, entered my credentials and waited 10 minutes… No change, still getting an HTTP/503 response.

I downloaded the script to the FOG server, ran ./updateIP.sh, and got the following results:

Updating the IP Settings server-wide. A password was not set in /opt/fog/.fogsettings for mysql use. Updating the IP in /tftpboot/default.ipxe Backing up /var/www/html//fog/lib/fog/config.class.php Updating the IP inside /var/www/html//fog/lib/fog/config.class.php Updating the fields inside of /opt/fog/.fogsettings All done.

I tried to log in again, and it’s still spinning around (although, it’s only been 2 minutes since I ran the script and tried to log in).

EDIT: It’s working now! After running the script, I also restarted Apache, PHP and MySQL, then tried again:

systemctl restart php7.0-fpm.service apache2.service mysql.service

I believe I’ve found and fixed the task active tasks page to refresh properly and stop displaying completed tasks. I tested this very minimally as I don’t have my normal dev environment setup currently.

It appears to be working properly, and should be fixed for RC-11.

As I don’t have a means to properly test this issue, I am not going to solve it, but just wanted to give a heads up so people don’t think it’s just been forgotten.

Thanks @Tom-Elliott, I have successfully captured and deployed Debian 9 clients both in virtual space and to real hardware. So, it looks like your fix works. I did notice some slower booting as you mentioned but that seemed to be minimized after I went through a full capture-deploy-capture sequence. Perhaps there was residual file system ambiguities that was affecting the boot times. In any event, the boot times smoothed out over time. The only slightly odd thing I did notice is sometimes the client would boot twice before the capture would actually start. I cannot reproduce this all the time. Just thought I would mention it if it makes you think of anything.

Thanks again; will this fix make it into 1.4.5?