Thank you, Paul. That was very helpful. Too bad they could/would not fix it for us after we submitted a ticket.
1 Like
I reached out about this too and made sure to reference ticket DPW-79PBB. They got back to me within minutes and now fusionHub is up and running. Thank you @Paul_Mossip for getting back with that ticket number, I’m sure this helped a ton!
2 Likes
If you make a snapshot of the 8.0.1 image before you configure the license, then you will be able to restore a clean original image with the archived boot settings for future installs.
1 Like
Thanks. Just referenced the ticket number and they set both the instance and the 8.0.1 snapshot in my account to legacy. I had to reinstall the instance from the snapshot and then everything booted fine,.
How are you all assigning a FusionHub license using this method?
I can get the instance to boot using a mix of the steps above for Vultr, DO and Linode, but once I get to the setup wizard I cannot add a license key as I get the “VMware model mismatch. Please check VMware Model and Server Address.” error.
The previous workaround was this was downgrade to 7.0.1 or lower but this firmware no longer seems to be available from the peplink download site.
I went through the same thing with my new FusionHub image on Vultr. I made a support ticket and provided the reference to ticket DPW-79PBB. Vultr fixed it within a half hour and I was able to proceed with the initial configuration of the FusionHub.
Thanks to everyone who has contributed to this thread.
A tip is to deploy the image, get Vultr support to disable the EUFI, then take a snapshot of the server BEFORE you run the Peplink installation wizard. You can then use this snapshot to deploy new instances without having to get Vultr support involved each time.
David
4 Likes
I’m having an issue deploying fusionhub on Vultr as well. They’ve disabled UEFI but according to Vultr the instance is hitting Kernel Panic after the GRUB bootloader as the OS is being initialized.
1 Like
Interesting issue. If it were me, I would blow away this instance, spin up a new VPS, and try again. I know this isn’t what you wanted to hear, but I just spun up a new instance two weeks ago with no issue.
I’ve destroyed it and redeployed it a couple times but it’s still the same. I guess I could try uploading the raw file again. It’s just annoying I have to submit a ticket to disable the UEFI when they give you the option to enable it during the deployment and I leave the box checked. The support rep mentioned they turned off UEFI for the snapshot/raw file I originally uploaded so that’s what I’ve been using.
Did you reference the ticket number for them to do it? Or just tell them to disable UEFI?
OH, I think i see what’s going on. They don’t need to disable UEFI for the SNAPSHOT, you need to provision a VPS with that snapshot and then have them disable UEFI on the VPS. Once that’s done, verify you can get to the login page but don’t login, take another snapshot of that machine, and you’re good to go forever.
Both. Initially I requested it to be disabled. Then when it started hitting the kernel panic I asked if they could reference the ticket and they confirmed they did everything mentioned in that ticket.
Ah ok. Bummer. If there was a way to share a snapshot with you I would.
So I decided to try again this morning and oddly enough this time it worked… I’m thinking something wasn’t working on Vultr’s end.
Awesome! Glad to hear it.
FWIW, I have posted a how-to on doing this step by step for anyone that isn’t comfortable with figuring it out as they go:
2 Likes
Attempting to install FusionHub on Vultr following the steps outlined above (thank you @ChristopherSpitler) . I have 2 instances I have attempted to get up and running, but I dont think either is completing the boot sequence even though Vultr has a public IP assigned and both report as running. FWIW I did reference the ticket requesting the UEFI be turned off, but Vultr says they cannot reference that ticket as it belongs to someone else. However, they indicate it has been turned off.
Looking at the Console as the VSP boots up, both seem to get hung up and never finish the bootup/start sequence. Not sure what this is supposed to look like, but most of these I’ve dealt with end up with some sort of complete/started message or a basic program menu. I have attempted this with FusionHub v8.0.1 build 1644 and v8.0.2 build 1656.
Any ideas?
So it seems @vigilant had the same issue, but there’s not a fix that was obvious. They said they waited awhile and it eventually would work. Unfortunately with the console UI they provide there’s no way to scroll up (that I’m aware of) so we can’t actually see what happened, only the end of the trace.
Trying again with new instance. Before requesting Vultr to disable the UEFI, this is the screen shot of the console. Looking for an .iso?
