@Sebastian-Roth said in Update fog using only https:

/opt/fogprojectgit/bin/error_logs/

logs are very large, how could I send it ?

I have commented on the last two
lines of the/opt/fog/. fogsettings file and the installation works

I have a problem running install

* Changing permissions on apache log files....................OK
* Backing up database.........................................Failed
* Updating Database...........................................OK
* Update fogstorage database password.........................Failed!

It seems to have conflits in the /opt/fog/.fogsettings file :

cat /opt//fog/.fogsettings
## Start of FOG Settings
## Created by the FOG Installer
## Find more information about this file in the FOG Project wiki:
##     https://wiki.fogproject.org/wiki/index.php?title=.fogsettings
## Version: 1.5.7.93
## Install time: ven. 06 déc. 2019 04:11:04 EST
ipaddress='148.60.4.2'
copybackold='0'
interface='ens3'
submask='255.255.248.0'
hostname='cosinus.istic.univ-rennes1.fr'
routeraddress='# No router address added'
plainrouter=''
dnsaddress='# No dns added'
username='fogproject'
password='1rstpasscoded'
osid='1'
osname='Redhat'
dodhcp='N'
bldhcp='0'
dhcpd='dhcpd'
blexports='1'
installtype='N'
snmysqluser='fogmaster'
snmysqlpass='my_original_pass_still_working_with_root'
snmysqlhost='localhost'
installlang='0'
storageLocation='/images'
fogupdateloaded=1
docroot='/var/www/html/'
webroot='/fog/'
caCreated='yes'
httpproto='https'
startrange=''
endrange=''
bootfilename='undionly.kpxe'
packages='bc curl dhcp-server gcc gcc-c++ genisoimage gzip httpd lftp m4 make mod_ssl mtools mysql mysql-server net-tools nfs-utils php php-bcmath php-cli php-common php-fpm php-gd php-json php-ldap php-mbstring php-mysqlnd php-process syslinux tar tftp-server unzip vsftpd wget xinetd xz-devel'
noTftpBuild=''
notpxedefaultfile=''
sslpath='/opt/fog/snapins/ssl/'
backupPath='/home/'
armsupport=''
php_ver=''
php_verAdds=''
sslprivkey='/opt/fog/snapins/ssl//.srvprivate.key'
## End of FOG Settings
mysqldbname='fog'
snmysqluser='fogstorage'
snmysqlpass='a crypted password '

Hello

My fog server is running under 1.5.7.60 version.
I have installed it by ./installfog.sh -W https://cosinus.istic.univ-rennes1.fr -S
I f I want tu uptade it, should I use:

cd /opt/fogprojectgit/
git checkout
git pull
cd /opt/fogprojectgit/bin/
./installfog.sh  -W https://fogus.istic.univ-rennes1.fr -S

to not break https communications with the clients ?

Arnaud

@Sebastian-Roth
I am on leave for 10 days
I’ll test the new installer when I get back.

Merry Christmas

@Sebastian-Roth
Hello
msi install works when passing https=0, so if I copy a settings.json file after installation, will the operation be sustainable ?

@Sebastian-Roth
I did not try with certificats and client 0.11.16.
Without certificat 0.11.16 was working

Hello
The client do not install with msi

I have add https install installing with this option: ./installfog.sh -W https://fogus.istic.univ-rennes1.fr -S

CustomActionSchedule(Action=InstallCert,ActionType=3073,Source=BinaryData,Target=InstallCert,CustomActionData=sHTTPS=1;sUSETRAY=1;sWEBADDRESS=fogus.istic.univ-rennes1.fr;sWEBROOT=/fog;sROOTLOG=1;sProductVersion=0.11.17;sINSTALLDIR=C:\Program Files (x86)\FOG\)
MSI (s) (58:C0) [16:30:10:887]: Invoking remote custom action. DLL: C:\windows\Installer\MSI2D78.tmp, Entrypoint: InstallCert
SFXCA: Extracting custom action to temporary directory: C:\windows\Installer\MSI2D78.tmp-\
SFXCA: Binding to CLR version v4.0.30319
Calling custom action SetupHelper!SetupHelper.CustomActions.InstallCert
MSI (s) (58!20) [16:30:11:809]: Note: 1: 2205 2:  3: Error 
MSI (s) (58!20) [16:30:11:809]: Note: 1: 2228 2:  3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1709 
MSI (s) (58!20) [16:30:11:809]: Product: FOG Service -- Unable to install CA certificate

Unable to install CA certificate
CustomAction InstallCert returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)

Here is the installfog generate by misexe:
installfog.log

installsation with SmartInstaller.exe works

Could you help me ?

@Sebastian-Roth
with your modification, the execution of the script goes to the end

Thank you

@Sebastian-Roth said in Auto-Installing FOG with HTTPS enabled issues:

https://github.com/ipxe/ipxe

wget https://github.com/ipxe/ipxe works on my centos 8.0 machine

I am on a Centos 8 server.
wget https://git.ipxe.org/ipxe.git/ gives :

--2019-12-09 15:51:41--  https://git.ipxe.org/ipxe.git/
Résolution de git.ipxe.org (git.ipxe.org)… 212.13.204.60
Connexion à git.ipxe.org (git.ipxe.org)|212.13.204.60|:443… connecté.
GnuTLS: A packet with illegal or unsupported version was received.
Incapable d’établir une connexion SSL.

On a centos 7, wget https://git.ipxe.org/ipxe.git/ works

No, we don’t have any proxy.

Works without -S option

@Sebastian-Roth said in Auto-Installing FOG with HTTPS enabled issues:

fogproject/bin/error_logs/fog_error

Hello Sebastian
Using ./installfog.sh -W http://cosinus/ -S
I get the same error:

* Compiling iPXE binaries that trust our SSL certificate......Failed!

Here is my error log file:
fog_error_1.5.7.56.log

Hello.

I have always the problem.
Can’t view Advanced menu command with Firefox 70.0.1 (64 bits).
No problem with chromium or opera.
Client os is ubuntu 18.04

@Quazz
Thank you for your answer, I did not know that deployed partitions were prorated to captured partitions.
It’s clear for me now

Hello,
Working on 1.5.7.55 version, I have a problem using single disk -resible image.
Working from a 250Go master with 34.1Go partition.
Deploying on a 55Go VM for test, I get a full partition on deploy.
I di not see any error during capturing and deploying

Here are the defintion files of the image :

cat win10light-1903/d1.fixed_size_partitions
1

cat win10light-1903/d1.minimum.partitions 
label: dos
label-id: 0x17fda016
device: /dev/sda
unit: sectors

/dev/sda1 : start=        2048, size=     1021952, type=7, bootable
/dev/sda2 : start=     1024000, size=    34329556, type=7
/dev/sda3 : start=    76800000, size=      112166, type=7

 cat win10light-1903/d1.original.fstypes 
/dev/sda2 ntfs
/dev/sda3 ntfs

cat win10light-1903/d1.partitions 
label: dos
label-id: 0x17fda016
device: /dev/sda
unit: sectors

/dev/sda1 : start=        2048, size=     1021952, type=7, bootable
/dev/sda2 : start=     1024000, size=    71680000, type=7
/dev/sda3 : start=    76800000, size=    38541312, type=7

Hello
I set up a new fog server to replace an old one.
We have 1 vlan for the servers, 1 VLAN (2) for the pc (~ 500) which are in the rooms of TP, 1 VLAN for the positions of the personnel of administration, and other VLANs for the wifi, projects …
My predecessor had configured the current fog server with an interface and an interface and an IP for the management interface on the server VLAN and its storage node on the VLAN (2). I think it was to avoid broadcasting multicast streams across the router.

On the test server, for the moment I only have an interface on the server VLAN.
During the deployment tests on lots of 10 machines I did not see a drop in performance.

Which architecture do you recommend?

@Tom-Elliott said in FOG 1.6, identified problems:

I have identified a few more issues and been able to correct them.

1. Clicking on pages within the menu as opposed to full refresh on the same page, some elements such as list -> select items to delete, click delete, the modal not appearing requesting password to ensure you want to do this. On full refresh to link it worked. On clicking from the menu it didn’t. Fixed by causing reinitialization.

2. Import elements didn’t return proper notification items. Similarly warnings and info notifications always assumed error. This has been fixed

3. Added rudimentary file upload progress system. Will be working to implement a progress indicator.

4. Creating images when entering the name, the path didn’t auto populate. This has been re-implemented.

5. Snapin file uploads were already set to be operational, but did not work due to typo on the POST field to send up the files. Renamed and introduced.

6. Host export didn’t properly indicate the primac field. It didn’t even pull in the Mac at all and the values were improper. The host name appeared in description, and name field was the spot Mac was trying to populate. Added the primac field and properly pulling the data now.

7. Along with the reinitialization for the modal requesting passwords, this same reinitialization was causing table populating to be reinitialization and throw an error as it already existed. Set to retrieve so not to throw the error.

What a job, thank you very much !

When I edit a group, I can’t set module association in client module settings

@Tom-Elliott said in FOG 1.6, identified problems:

@lebrun78

Cool, thank you for that. This feature has not been implemented yet. Here’s the code behind the scenes, so it is a known thing and needs to be worked. I’m only one person though…

Could you tell me which features are not implemented todoy, so I will be able to test all the others ?