Endpoint changed, but not working

[Tronus1409]

[]: This bug persists when memory is increased beyond 8GB.

Describe the bug
i changed the Endpoint in the boot.cfg, but it did not change anything,it keeps downloading them from the original endpoint.

To Reproduce
Steps to reproduce the behavior:

1. install netbootxyz
2. open the web dashboard and change the live_endpoint under Menus->Boot.cfg
3. wait till your pc loads into the pxe menu and select any os
4. see the change wont did not change anything
   Expected behavior

Screenshots

Additional context
netbootxyz runs under a docker container.

[antonym]

Have you set the live_endpoint variable in local-vars.ipxe?

https://github.com/netbootxyz/netboot.xyz/blob/development/roles/netbootxyz/templates/local-vars.ipxe.j2

[Tronus1409]

I cant find that file in the menus tab, do i need to build it on my own? Im using a docker image for deploying, is that the problem?

[antonym]

You can create it with those contents, it's currently left out of the release because it's a user defined option, but I can see about adding a local-vars.ipxe.example to the release file so it doesn't impact existing users.

[antonym]

Keep in mind if it fails to boot from local tftp, it rolls to the public instance of netboot.xyz using the default endpoint.

[Tronus1409]

That means i need to build it myself, not using docker?

[antonym]

Just create new file, name it that and add settings on the menus UI.

[Tronus1409]

i did what you told me and created the file in the web ui, but that changed nothing.

[jan-tee]

I too have this problem and here's what I can observe by setting up the Docker container and DHCP options. I am using a custom DNS name for the netboot.xyz services (think "boot.my.lab"):

• PXE system gets DHCP options
• retrieves netboot.xyz.kpxe via TFTP from DHCP "next server" option
• never retrieves anything via HTTP/HTTPS from the local instance, goes straight to GitHub; never retrieves any of the .ipxe files

My conclusion is that if you want to change the DNS names, you will need to re-compile the assets. Editing the menu files does nothing because they are never retrieved.

The user expectation is "editing the config files will change the behavior", but it seems that this is not true unless you run Ansible to re-generate the netboot files. So the Docker container just does not seem to support the scenario, and the docs are unclear.

[deffcolony]

Hi, I’m experiencing the same issue as you described. I’ve set up the Docker container and configured the DHCP options, but I’m also seeing that:

• Editing the menu files locally doesn’t seem to affect behavior.

For me its when i try to set the set win_base_url to a custom url it just does not want to fetch the URL in boot since its shows as emty

It’s not very clear to me how to configure netboot.xyz to use local variables. Even after trying several adjustments, it’s still not working for me. the documentation doesn’t make this clear.

Could you or someone else clarify how to properly configure netboot.xyz to use local settings without needing to recompile? Any guidance would be much appreciated!

[Tronus1409]

Hi, I’m experiencing the same issue as you described. I’ve set up the Docker container and configured the DHCP options, but I’m also seeing that:

• Editing the menu files locally doesn’t seem to affect behavior.

For me its when i try to set the set win_base_url to a custom url it just does not want to fetch the URL in boot since its shows as emty

It’s not very clear to me how to configure netboot.xyz to use local variables. Even after trying several adjustments, it’s still not working for me. the documentation doesn’t make this clear.

Could you or someone else clarify how to properly configure netboot.xyz to use local settings without needing to recompile? Any guidance would be much appreciated!

Hey, i solved my own way. I copied the dockwe config from techno tim, where he has a version for the menu specified and i kept it at this version. In that version, you can change things again.