Marti Martz

@brazenvoid Appreciate that report. Cleaning up my test VM before I create a new VPS with the next distro version. Want to make sure I'm not wasting money or too...

Hmmm new distro via MongoDB only has MongoDB 4... that can present a problem/delay with *express-brute-mongo*.

OOOH.. not good... local pro delay with next version of distro in VM. Guess I'll need to add that *async* test back in a local branch. It is about peak...

Okay... pro was dragging AWS and MongoLabs down in local pro. Killed pro and local pro is at top speed *(my usual perusing the site)* atm. Still have the lurking...

@sizzlemctwizzle I'm still recommending the VPS upgrade to a new one esp. to *(hopefully)* resolve this issue. Adding the extra security will take a bit more time on the VPS...

Hmmm looks like I have DNS access change... we'll know for sure in ~24 to 48 hours.

So before the DNS propagated to me it was fine using the direct IP. Granted no one else had that IP. There's very few things left that I can think...

#### Misc test note Local pro test *(this means I'm not using our VPS providers hosting for those new here but actual pro(duction) is running atm)* with this diff and...

Finally!!! Found evidence and confirmation of network issue on production *(from VPS to MongoLabs)*: ``` console 2018-12-18 13:30:17.100 +00:00: Group rating NOT updated aErr := MongoNetworkError: connection 10 to *clipped*.mongolab.com:*portclipped*...

#### Misc test note I've temporarily audited url usage *(on pro)* this morning for about 4 minutes on a single thread and most of the requests are to .meta.js and...