Can't connect to Ready Cloud

I have been having issues connecting my RN104 to the ready cloud. It was connected at one point but then stopped worked. I'm not sure when as it is not a feature I use often. I first merged my ReadCloud and Netgear accounts. When the connection still wasn't working I tred leaving the ReadyCloud which didn't seem to do anything on the device. I then tried removing the offline device from ReadyCloud which successfully removed it however the NAS still thought it was joined. I then upgraded the firmware, added 8.8.8.8 to DNS. I was then able to leave the ReadyCloud on the NAS however now the Join and On/Off buttons are gryed out and I can't rejoin to ReadyCloud.

Of the research I have done I have see some have configuration issues though Netgear seems to fix it for them and not details are given on what was done. I also saw something about leafp2p needed to be enabled on the device. I have verified that it is not running but when I try to enable it with systemctl I get the following:

Executing: /lib/systemd/systemd-sysv-install enable leafp2p
The unit files have no installation config (WantedBy, RequiredBy, Also, Alias
settings in the [Install] section, and DefaultInstance for template units).
This means they are not meant to be enabled using systemctl.
Possible reasons for having this kind of units are:
1) A unit may be statically enabled by being symlinked from another unit's
.wants/ or .requires/ directory.
2) A unit's purpose may be to act as a helper for some other unit which has
a requirement dependency on it.
3) A unit may be started when needed via activation (socket, path, timer,
D-Bus, udev, scripted systemctl call, ...).
4) In case of template units, the unit is meant to be enabled with some
instance name specified.

Any help would be appreciated