Skip to content

Expired TLS certificate on ping.detectionlab.network, preventing retrieval of the preseed config for ESXi deployment #897

Open

Description

@Qazeer
  • Deploying via (VirtualBox/VMWare/AWS/Azure/ESXi): ESXi

Description of the issue:

The TLS certificate of ping.detectionlab.network is expired, preventing access to http://ping.detectionlab.network/preseed.cfg for the Packer ubuntu image. As a result, the provisioning process hangs at Waiting for SSH to become available....

Switching to http in the ESXi/Packer/ubuntu1804_esxi.json configuration file fixes the issue (but is more a hacky fix than a lasting solution):

preseed/url=http://ping.detectionlab.network/preseed.cfg<wait>

Activity

  1. 0xv1n commented on May 9, 2023

    @0xv1n
    Contributor

    @Qazeer

    AFAIK, callbacks to ping.detectionlab.network were removed in 70fb1ec. The project is no longer being maintained, and the hosted resource there is probably inactive. My guess is the ESXi scripts didn't get updated?

  2. Skr1ptKid-0x commented on Oct 25, 2023

    @Skr1ptKid-0x
    • Deploying via (VirtualBox/VMWare/AWS/Azure/ESXi): ESXi

    Description of the issue:

    The TLS certificate of ping.detectionlab.network is expired, preventing access to http://ping.detectionlab.network/preseed.cfg for the Packer ubuntu image. As a result, the provisioning process hangs at Waiting for SSH to become available....

    Switching to http in the ESXi/Packer/ubuntu1804_esxi.json configuration file fixes the issue (but is more a hacky fix than a lasting solution):

    preseed/url=http://ping.detectionlab.network/preseed.cfg<wait>
    

    Still helped me out, thanks. Maybe we make a group repo, keep it going even a little bit. Can't install splunk lab on esxi, also a PITA with WSL2. Although I may have learned another way through here...

  3. fsacer commented on Mar 8, 2024

    @fsacer
    Contributor

    Had this issue as well, maybe a good fix would be to just host it here inside the repo, so no other external resources are needed because the project is no longer maintained. Maybe also specific version numbers should be written down so everything is reproducible even if packages change.

  4. brootware commented on Sep 5, 2024

    @brootware

    Similar issue I faced. was deploying this on proxmox and this workaround fixed it.. Agreed with @fsacer on just hosting the preseed,cfg file inside the repo rather than on a separate site.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions