I have used the freeware version of the software for at least a year but not frequently. I tried starting it tonight and see an electrical plug image with a red line through it saying Disconnected with a Reconnect button beside it. The software does not reconnect and the Disconnected message remains. I am using version 3.1.0.21 and tried running a software update which fails and gives the message: “There was an error deserializing the object of type CloudBerryLab.Base”. The error message may be longer than this but the right border of the Check for Updates window cannot be extended to see any more. I cannot find this issue mentioned in the forum and am hoping you can provide some help. Thank you.
[reply=“Pete Palmer;d2677”] There was a DNS issue on one of our servers that the hosting provider is correcting. From what I was told by engineering, the problem was already addressed by the hosting provider, but the DNS entries need to do the typical internet migration. That should be complete by tomorrow. We apologize for the issue with Connect.
Thank you. I will try again tomorrow.
[reply=“David Gugick;9859”]
I am having the exact same problem with MSP360 Connect PRO
Couldn’t connect yesterday, and the problem persists this morning.
[reply=“David Gugick;9859”] Still down. Thanks
[reply=“Yen;9864”] Yes it’s still down. I don’t have an update but I’m hoping by tomorrow the DNS entries will be properly migrated across the internet and things will be back to normal.
Hi, when will the system be okay? I used it for work and right now it is still down. Is there any chance it may expedite? Hoping for an update as soon as possible. Thank you.
[reply=“David Gugick;9866”] Hi David, thanks for the reply. the remote computer shows it’s connected, but I’m in Nevada and my computer is still disconnected. can’t connect
[reply=“David Gugick;9866”] Any Update on this? I am having the same issue.
[reply=“David Gugick;9866”] any updates regarding this?
Same problem for 2 days. With the Pro version. Please fix this !!!
We still have this problem with our machines with the Pro version. Can you post the url and ip address info so that we can implement a workaround with Route53 or host files in the meantime?
I’m now on day 4 of having this problem. The response from the help desk is that this issue has been lowered from priority 1 to priority 3. Is there any workaround ?
Same issue here now.
We have been having the same problem. Can MSP provide an update or temporary workaround?
[reply=“David Gugick;9866”] I think handling our DNS as a workaround would be applicable for the time being here. But, would need the destination information if you can provide. Is that a possibility?
For anyone reading this, I see the activation is trying to hit foris.cloudberrylab.com. It’s incredibly disheartening to see the response is a webpage saying the domain is for sale. It seems that they’re finally trying to sunset references to Cloudberry in preference to MSP360 and the forwarding at the DNS is incorrect. If we could get an answer as to what the actual destination is supposed to be, this could be solved right now with an entry into the local host file or and entry into Route53.
David, it’s becoming obvious right now every user of the Cloudberry Drive product is down. Can you please provide us with some information (particularly pertaining to entries we can put into our DNS for forwarding) to use so we can create workarounds so that we can use the product?
So, looks like it might be the low road and the domain was allowed to expire. If it’s helpful to others, I see the A record for cloudberrylab.com was changed around 9/24 to 91.195.240.13, which would correspond with the expiration of the domain registration in whois. Before that, the A record history has it pointing to 50.19.243.6 and was there for several years until the expiration. So, the A change was likely the registrar updating it to the current “For Sale” location. I’m starting to mess with host entries and Route53 to point all requests to that ip (hoping it’s not toast too). Hope this helps someone.
David
Is there any timeline on when this issue will be resolved?