Unable to create nest

[CC88 1]

Hi Covecube,

 

First time user of Bit Flock but I'm unable to create a Nest.

 

I've disable firewall etc, just in case, but still no joy.

 

The error says "The underlying connection was closed: An unexpected error occurred on a send." - screenshot attached.

[Christopher (Drashna) 501]

Works fine on my end (and ... I'm using an UTM device)

 

Try re-running it and see if it works fine.

 

If not, then are you using a firewall on the system?  Antivirus? 

[CC88 1]

Glad to hear it is still working, in general, but still no joy on my end.

 

I am using ESET Smart Security firewall/antivirus. But even if I completely disable both firewall and antivirus modules - no restrictions -, I still get the same error. Very strange...

[Christopher (Drashna) 501]

well, this guide is designed for StableBit CloudDrive, but ... should help out here.

 

Run this:

http://wiki.covecube.com/StableBit_CloudDrive_Web_Logs

 

Then try re-running BitFlock and try to create a nest. Once it fails, stop the logging and upload the logs.

[CC88 1]

Thanks for the effort... I tried from another PC and it worked fine. Made a claimed Nest, etc, no problem.

 

Still doesn't work from the original PC but, since it's due for a rebuild, not worth wasting too much time on it... it is just strange that it shouldn't work for no apparent reason.

My only guess would be, it may be due to some of the "unnecessary" Windows services I've disabled - has never stopped anything else from functioning.

 

Anyway, thanks again. I'll save the troubleshooting for the rebuilt PC, if needed... hopefully not!

[Christopher (Drashna) 501]

Well, if you disabled WMI, that could cause it.  Or if you've disabled HTTP/web related stuff, that could also do it.

 

That said, if you really, really want to (sounds like it isn't worth the effort though), download and run "fiddlerCap", and this will help see what is going on. 

 

http://wiki.covecube.com/StableBit_CloudDrive_Web_Logs

[CC88 1]

Sorry to take so long to reply... instead of trying to troubleshoot what wasn't working (most likely disabled HTTP/web service), I just set up new PC.

 

Scan and connection now works fine, under Win 10, but have a new issue...!

 

I have two PCs, both run and update my BitFlock nest fine. But each time I run BitFlock on one PC, it no only updates my nest but removes the other PC details. So the nest only ever shows one PC at a time.

 

Is this normal? I thought - maybe mistakenly - each PC I run BitFlock on would update and add, not replace, to my nest's computer list and be able to see multiple computers' HDDs at once.

[CC88 1]

Just wondering if any advice if multiple computers can be added to the same nest?

 

Thanks.

[Christopher (Drashna) 501]

Make sure the Nest ID is the same on both.  And that they're not using the same name. 

 

Because, yes, it supports multiple systems.

[CC88 1]

Nest ID is definitely the same - have only created one nest. And computer names are different.

 

Is very easy to replicate. Each time I update one computer, it updates the nest but removes the other computer.

 

Any other suggestions? Thanks.

[Christopher (Drashna) 501]

See, I can't reproduce the issue, it updates things properly for me.  And I can see the old, out of date systems listed as well.

[CC88 1]

Hmmm. It's a strange on then.

Both computers a newly installed Win 10. Both from scratch - no images.

 

I'll try on a 3rd computer and see what happens...

[Christopher (Drashna) 501]

Any firewall or web filter, by chance?  

 

And you have claimed an Nest ID, correct?

[CC88 1]

Finally got back to this and still the same issue unfortunately.

Each computer updates the same nest fine but each time I update from one computer it removes the other computer from the nest.

Claimed nest ID is definitely the same... screenshots attached.

Only thing I can guess at, is there some glitch due to the nest ID containing a "." ?

[Christopher (Drashna) 501]

Well, honestly, we plan on deprecating BitFlock in the not too distant future (for better stuff)... 

But I've flagged the issue, just in case.

https://stablebit.com/Admin/IssueAnalysis/27829

[CC88 1]

Yes, I'd noticed in another thread that BitFlock is due for retirement.

Hopefully I can have more luck for the replacement as it's a great idea.

Any guess of an ETA of BitFlock's replacement?

[Christopher (Drashna) 501]

Sorry, no ETA yet. 

 

[CC88 1]

No problem.

While not holding my breath, if any chance of a fix/solution for BitFlock, in the the meantime, would be great.

Thanks.

[Christopher (Drashna) 501]

Well, I've already flagged it, so when Alex is able to get to it, he'll take a look. 

[CC88 1]

Sounds good. Thank you!

[Christopher (Drashna) 501]

You've very welcome!