ipxe https
-
@filisdiez Do you manually build iPXE? Have you tried using the provided script in
fogproject/utils/FOGiPXE/buildipxe.sh(ref). -
@Sebastian-Roth said in ipxe https:
@filisdiez Do you manually build iPXE? Have you tried using the provided script in
fogproject/utils/FOGiPXE/buildipxe.sh(ref).No, tried to generate it on https://rom-o-matic.eu. Generated through your script and what to do next not flood plain.
-
@filisdiez After the compile (script) has finished you find the new binaries in
fogproject/packages/tftp. Now you can either re-run the installer to populate those or just manually copy all the files fromfogproject/packages/tftpto/tftpboot. -
@Sebastian-Roth said in ipxe https:
@filisdiez After the compile (script) has finished you find the new binaries in
fogproject/packages/tftp. Now you can either re-run the installer to populate those or just manually copy all the files fromfogproject/packages/tftpto/tftpboot.It is clear, and what my actions are farther? Whether it is necessary to add additional options to iPXE Menu Customization?
-
@filisdiez Do you still get an error when PXE booting the client?? Please take a picture of that and post here!
-
@Sebastian-Roth said in ipxe https:
@filisdiez Do you still get an error when PXE booting the client?? Please take a picture of that and post here!
-
@filisdiez What exactly is share.cgi?? Can you open the URL https://hiddenurl.ddns.net:7443/share.cgi in your browser? If yes, what do you see?
Not exactly sure but the “Booting failed, dropping to shell” does not seem to be part of our official embedded iPXE script. While we still try to help you it would be helpful if you provide more information on what exactly you used to compile this iPXE binary. It seems highly customized and we need more information to be able to help!
-
@Sebastian-Roth said in ipxe https:
@filisdiez What exactly is share.cgi?? Can you open the URL https://hiddenurl.ddns.net:7443/share.cgi in your browser? If yes, what do you see?
Not exactly sure but the “Booting failed, dropping to shell” does not seem to be part of our official embedded iPXE script. While we still try to help you it would be helpful if you provide more information on what exactly you used to compile this iPXE binary. It seems highly customized and we need more information to be able to help!
Changed for the simplified way. But the error all the same arises. For compilation I used your script.
-
@filisdiez First I have to say this isn’t a FOG Project related issue. I just have to say that so that we are looking through the proper lens here. If others find this thread in the future it will confuse the heck out of them thinking that they might have found a solution related to FOG imaging.
While I haven’t worked with fog and https yet, it would say that your certificate embedded into the iPXE image doesn’t match the one configured into your web server (apache or nginx). Have you confirmed that you can access the page via a web browser? Right now its not clear if the issue is with the iPXE client or the web server.
-
@filisdiez Since you are building iPXE from the rom-o-matic site you might want to review the FOG configs from the github site. I’ve used the rom-o-matic before I and referenced the config settings in console.h, general.h, settings.h to know what rom-o-matic settings that need to be set. You can review the FOG Project related settings here: https://github.com/FOGProject/fogproject/tree/master/src/ipxe
You might also want to refer to the script that Sebastian mentioned in the first post you can review it here: https://github.com/FOGProject/fogproject/tree/master/utils/FOGiPXE
-
You’re trying to pull something from the images folder over https, but https isn’t configured to serve that location.
Think more along the lines of
/var/www/fog
