Hi Folks,
we are migrating our FusionHub Instances from Proxmox to Oracle Cloud OCI. Is anyone here that made it? We are not able to activate the licensing and it seems that FusionHub speak with inControl but don’t get the answer back. Egress rule on OCI is ALL for ALL and Ingress rules have the specific Peplink ports open.
Thanks,
-Jarno
I just gave this a go. It also failed at the licensing stage for me. Turned out the issue was DNS.
Oracle’s DHCP server assigned a WAN IP via DHCP but not the DNS servers.
Manually setting Google DNS servers for the FusionHub WAN connection in its Web Admin then let the FusionHub reach the licensing server which fixed the problem.
Thank Martin! We discovered this as well changing the DNS in OCI. Did you made the change in FusionHub instead of inside OCI VCN DHCP settings?
I had a issue with FusionHub as after trying several time to update the license, FusionHub refuses to go to any other web tab.
In the Fusionhub. I just ran the setup wizard again from the menu bar.
Wondering if anyone who successfully configured Oracle Cloud OCI to run a FusionHub instance can comment on how it all worked out (in terms of reliability, performance, etc).
Considering using OCI for a FusionHub Solo since AWS doesn’t yet have a datacenter in the needed region.
So, I’m currently running my Fusion Hub Solo on OCI in the Chicago region. I have ben pleased with the performance so far. I also tested FH Solo on Digital Ocean (lower cost, but their IP/ASN reputation meant many Cloudflare blocked web sites), and Microsoft Azure (more expensive than OCI as they charge for egress traffic over 500MB). I’m bonding 2 Starlink and one 5G connections into a single tunnel to the FH Solo instance. The days of multiple 15-30 second Starlink outages are over!