Can you give us a screenshot of the XMR tab not populating? Thats also not happening on any of my machines, and not reported anywhere.
Is it that you just have to paste the address in and click lookup?
Sure, no problem. Here is a screenshot. It happens on all web browsers but was working fine just a couple days ago.
https://1drv.ms/u/s!AjuxSfKebyTRgcFIBZKV6Y2xf8Q6UAI see that, ok. Well thats sort of a smoking gun right there as I havent seen that behavior.
Please try opening a google chrome incognito window and pulling it up, and see if you can switch to the XMR inquiry tab.
One know issue with nomp is if you leave a browser window open, the page subscribes to the single thread (which I dont like) and it takes 60 seconds to update if you hit f5.
But a new incognito window refreshes all the tabs usually pretty fast (but not very fast).
On a side note, I plan on having the second pool ready by Monday evening, so if all else fails you can test it.
It sure does seem like your computer starts a session, then hangs up before it can solve a bbp share.
Id still recommend running a cat5 cable directly from a machine and try to mine from it through the router (eliminate wifi).
That imho, is the best shot right now to circumvent other tests first.
I think the computer gods just hate me. So here's where we stand...
First, the incognito tab in Chrome worked fine for a while, then it too stopped loading. I was forced to go straight to
https://minexmr.com/#worker_stats to be able to view my XMR shares.
Second, I tried hooking up a PC to my router via Ethernet cable, but ran into the same issue. I also remotely took over my mom's computer (2 hours away) and tested there with a freshly downloaded copy of the miner but same results as everything else. XMR shares are being generated steadily but no BBP shares at all.
During testing however, I noticed something went terribly wrong with the pool's stats:
https://1drv.ms/u/s!AjuxSfKebyTRgcFOYRshFGkuWBNLvQIt's been about 20 minutes since I noticed it and it's still looking like that.
Now I know that with everything going on it seems like there is something on my end that's blocking it, but even on computers 120 miles away it does the same thing. At that point, the only thing in common is my BBP address...even though I've already tested with a freshly generated one.
Something I just thought of...would there be any configuration in my BBP wallet that could be affecting this? Would received addresses generated in old versions have issues? Since I have not tested a new received address since I upgraded to the most recent build of the wallet, would that be worth a shot? Could this be something that the pool is rejecting when trying to credit shares?