cryptoGlance [v2.1] :: Open-source, self-hosted, multi-rig monitoring tool!

[thedreamer]

Cool. I'll have to check it out when it's done.

[opentoe]

I'm trying to setup this program on my VPS, but there is only one port open on these miners. If I forward that port to one of miners I'll only see just that one miner and not the rest. An example would be

http://my_ip:4028

I'll setup port forwarding in my router but how would I configure the other miners as well? Because the main page comes up real nice on my VPS.

Thanks,

Michael

[Biffa]

I'm trying to setup this program on my VPS, but there is only one port open on these miners. If I forward that port to one of miners I'll only see just that one miner and not the rest. An example would be

http://my_ip:4028

I'll setup port forwarding in my router but how would I configure the other miners as well? Because the main page comes up real nice on my VPS.

Thanks,

Michael

Port forwarding on the router means that you can choose any port on the outside interface of the router and forward it to an address and port on a machine on the internal interface of the router.

So say your external interface on the router is 196.345.67.1

You can have port 1001 on the external interface point to port 4028 on the miner ip 192.168.1.101
i.e. 196.345.67.1:1001 ---> 192.168.1.101:4028

But you can also forward ports 1002, 1003, 1004, 1005 etc to other machines even if they are using the same port
i.e. 196.345.67.1:1001 ---> 192.168.1.101:4028
196.345.67.1:1002 ---> 192.168.1.102:4028
196.345.67.1:1003 ---> 192.168.1.103:4028
196.345.67.1:1004 ---> 192.168.1.104:4028
etc

Note how the external IP doesn't change, but the port does, and the internal IP does change but the port doesn't

Now having explained all this I don't actually think its a real good idea to open up these ports on your router directly to the miner unless you can protect them somehow, at the least by limiting access by IP address.

[Biffa]

You can make the window smaller in the browser if you zoom out using the browser feature. (tested using Chrome)

But maybe what is needed is just a more concise view with less info.

Problem with that is, that it resizes all the browser Windows after you set it up unless you set it back. Pretty inconvenient. Also requires you to run the program/app and the browser window if on the same pc.

If you guys need help with testing let me know. I can help.

On my chrome it only affects the tab that the instance of CryptGlance is running, not any other tabs in that instance of Chrome or even if I open a new window in Chrome.
I agree that a zoom util within the software would work better but it does work

[cryptoglance]

You can make the window smaller in the browser if you zoom out using the browser feature. (tested using Chrome)

But maybe what is needed is just a more concise view with less info.

Problem with that is, that it resizes all the browser Windows after you set it up unless you set it back. Pretty inconvenient. Also requires you to run the program/app and the browser window if on the same pc.

If you guys need help with testing let me know. I can help.

On my chrome it only affects the tab that the instance of CryptGlance is running, not any other tabs in that instance of Chrome or even if I open a new window in Chrome.
I agree that a zoom util within the software would work better but it does work

I have a solution in place, however FireFox doesn't scale properly... it works fine in any webkit browser (Chrome, Safari, latest Opera). For the windows application it works perfectly.

Just need a few minor fixes made and a new nightly build can be shipped out. I'm thinking Saturday ~4pm EST (March 28th).

@Biffa, There's a few fixes in the update procedure that should resolve the issue with your instance not updating automatically. Worse case scenario it will warn you about what is wrong.

[Biffa]

You can make the window smaller in the browser if you zoom out using the browser feature. (tested using Chrome)

But maybe what is needed is just a more concise view with less info.

Problem with that is, that it resizes all the browser Windows after you set it up unless you set it back. Pretty inconvenient. Also requires you to run the program/app and the browser window if on the same pc.

If you guys need help with testing let me know. I can help.

On my chrome it only affects the tab that the instance of CryptGlance is running, not any other tabs in that instance of Chrome or even if I open a new window in Chrome.
I agree that a zoom util within the software would work better but it does work

I have a solution in place, however FireFox doesn't scale properly... it works fine in any webkit browser (Chrome, Safari, latest Opera). For the windows application it works perfectly.

Just need a few minor fixes made and a new nightly build can be shipped out. I'm thinking Saturday ~4pm EST (March 28th).

@Biffa, There's a few fixes in the update procedure that should resolve the issue with your instance not updating automatically. Worse case scenario it will warn you about what is wrong.

Sounds great!

[cryptoglance]

Nightly has been released: v2.0.2.763

[Real-Duke]

Thanks for manual update check 

[cryptoglance]

Beta released!

Code:

    [ v2.0.3-beta ]

    FEATURES
    ========
    - Added app specific way to zoom in/out
        - Zoom Out:     CTRL + <
        - Zoom In:      CTRL + >
        - Reset Zoom:   CTRL + /
    - Added manual update check in Settings page
    - Added New Zealand Dollar as a Fiat option in wallets
    - Added current FIAT price of a coin

    POOLS
    =====
    - [+POOL] NiceHash/WestHash
    - [+POOL] BitcoinCZ aka Slush
    - [+POOL] AntPool
    - [+POOL] BitMinter
    - [+POOL] P2Pool
    
    ALGORITHMS
    ==========
    - [+Algorithm] Blake-256
    - [+Algorithm] Groestl
    - [+Algorithm] Jackpot
    - [+Algorithm] Lyra2RE
    - [+Algorithm] Neos-Blake
    - [+Algorithm] NeoScrypt
    - [+Algorithm] WHIRL
    - [+Algorithm] X17
    
    COINS
    =====
    - [+COIN] Burstcoin
    - [+COIN] DogeCoin Dark
    
    HOTFIXES
    ========
    - Changed from BitcoinIndex.es to FirstRally.com
    - Fixed issue with Bitcoin Affiliate Network saving an empty name/label
    - Fixed incorrect reporting of rejected share warning
    - Added permission checking to the update process
    - Fixed permissionfix script, should correctly set permissions on parent folder
    - Fixed issue with pools not loading sometimes
    - Added round duration to CKPool
    - Fixed incorrect BTC Guild pool hashrate
    - Fixed incorrect BTC Guild worker count
    - Removed useless BTC column when looking at a BTC wallet
    - MPOS network hash x1000h too high
    - Update page will now display correctly for those with slow connections
    - Attempt to fix issue where the update.zip does not delete in some cases

    KNOWN ISSUES
    ========
    - Miner Failover may report incorrect active pool
    - Wallets can take a long time to load
    - Pools do not show an offline mode

[NameTaken]

I've been using cryptoGlance since I started mining again a few months ago so I made Linux Docker container that will run cryptoGlance with a single command.

https://github.com/UserTaken/docker-cryptoglance

[cryptoglance]

I've been using cryptoGlance since I started mining again a few months ago so I made Linux Docker container that will run cryptoGlance with a single command.

https://github.com/UserTaken/docker-cryptoglance

Thanks NameTaken, this is great!

I do have one concern though. The user_data is protected by a .htaccess file, but that's supported by apache and not nginx. Perhaps add the user_data folder restriction to the nginx.conf?

Maybe refer to this? http://serverfault.com/questions/137907/how-to-restrict-access-to-directory-and-subdirs

[NameTaken]

I've been using cryptoGlance since I started mining again a few months ago so I made Linux Docker container that will run cryptoGlance with a single command.

https://github.com/UserTaken/docker-cryptoglance

Thanks NameTaken, this is great!

I do have one concern though. The user_data is protected by a .htaccess file, but that's supported by apache and not nginx. Perhaps add the user_data folder restriction to the nginx.conf?

Maybe refer to this? http://serverfault.com/questions/137907/how-to-restrict-access-to-directory-and-subdirs

I've updated the image.

[opentoe]

I'm trying to setup this program on my VPS, but there is only one port open on these miners. If I forward that port to one of miners I'll only see just that one miner and not the rest. An example would be

http://my_ip:4028

I'll setup port forwarding in my router but how would I configure the other miners as well? Because the main page comes up real nice on my VPS.

Thanks,

Michael

Port forwarding on the router means that you can choose any port on the outside interface of the router and forward it to an address and port on a machine on the internal interface of the router.

So say your external interface on the router is 196.345.67.1

You can have port 1001 on the external interface point to port 4028 on the miner ip 192.168.1.101
i.e. 196.345.67.1:1001 ---> 192.168.1.101:4028

But you can also forward ports 1002, 1003, 1004, 1005 etc to other machines even if they are using the same port
i.e. 196.345.67.1:1001 ---> 192.168.1.101:4028
196.345.67.1:1002 ---> 192.168.1.102:4028
196.345.67.1:1003 ---> 192.168.1.103:4028
196.345.67.1:1004 ---> 192.168.1.104:4028
etc

Note how the external IP doesn't change, but the port does, and the internal IP does change but the port doesn't

Now having explained all this I don't actually think its a real good idea to open up these ports on your router directly to the miner unless you can protect them somehow, at the least by limiting access by IP address.

Thanks, that makes perfect sense. I completely forgot about the internal/external port. I'll lock up my router's access list so I'm the only one that is able to get in anyway, if I set it up that way. I did find a useful iPhone app that coincides with a program that I use on my computer which is all I need. Open up the program and it basically lists all my miners, hash rate and temps. Just the info I really need. It is nice to see though updates on the apps coming out.

[Mikestang]

Can this software monitor USB devices?  I watched your setup video and it shows you entering IP addresses for the miners, but my USB miners do not have an IP address.  Thank you.

Yes it can, your USB devices are controlled by a computer running cgminer or bfgminer, you just have to turn API access on and then use the ip address of the computer running the mining software.

You'll have to allow API access on the client config and adjust any firewall settings on the computer to allow external connections to the API ports.

Awesome, finally got around to installing and configuring your software.  It's really cool, just what I was looking for.  Now I can watch my S1, S3+, U3, and 4x nanofuries on one screen.  Thank you!  I will send a small donation (if I had more BTC I would send more).

One question, when I unplug and replug in my U3 (usb), the dashboard recognizes it as a new device and leaves the old one in the display.  I cannot figure out how to remove this old device.  The U3 needs to be unplugged and replugged often, and I'm afraid my display will become cluttered with old, unused devices.  Is there a way to delete the old device?


(disregard the error rate, it settles down after a few unplugs)

[Mikestang]

I think I answered my own question.  Since it's displaying what cgminer is reporting through api, I have to restart cgminer to remove the old, unused devices.

Is there a way to get best share to be shown?  It's fun to keep an eye on that one.

[cryptoglance]

I think I answered my own question.  Since it's displaying what cgminer is reporting through api, I have to restart cgminer to remove the old, unused devices.

Is there a way to get best share to be shown?  It's fun to keep an eye on that one.

Unfortunately cgminer doesn't remove it, we've ran into this issue with my HexFury devices. If you restart the miner via CryptoGlance interface it should fix the issue.

As for the best share, we can add this in the next nightly release. We're just waiting on a 3rd party API to be available to the public before we make our next release. Eta ~2 days - 1 week

[Mikestang]

I think I answered my own question.  Since it's displaying what cgminer is reporting through api, I have to restart cgminer to remove the old, unused devices.

Is there a way to get best share to be shown?  It's fun to keep an eye on that one.

Unfortunately cgminer doesn't remove it, we've ran into this issue with my HexFury devices. If you restart the miner via CryptoGlance interface it should fix the issue.

As for the best share, we can add this in the next nightly release. We're just waiting on a 3rd party API to be available to the public before we make our next release. Eta ~2 days - 1 week

If I quit cgminer and restart it removed the dropped device(s).  Takes several restarts to get the U3 to run without errors.


Having best share shown would be great, thank you!  In fact, being able to pick and choose what is displayed in each box and what isn't would be pretty cool, too.  Assuming I need to change my update setting from Release to Nightly to see the change?

I purchased the android app as well, are there instructions somewhere how to set up the server so that I can link to my phone? I am a noob with setting up webservers.  That appears what needs to be done here, right?  I've only just learned how to get one going for the Bitnodes incentive program.  So it's something I can figure out if I'm pointed in the right direction.  Thanks again.

[cryptoglance]

I will send a small donation (if I had more BTC I would send more).

I just noticed this, forgot to say thank you! So... Thank you! Much Appreciated

[cryptoglance]

Having best share shown would be great, thank you!  In fact, being able to pick and choose what is displayed in each box and what isn't would be pretty cool, too.  Assuming I need to change my update setting from Release to Nightly to see the change?

This is correct. On the settings page you have the option as to what kind of updates you want.
Release - Very stable, very well tested, expect no issues.
Beta - Fairly stable, meant for testing, expect a few issues.
Nightly - Stable enough to use, code is hot-off-the-press, some functionality might break.

I purchased the android app as well, are there instructions somewhere how to set up the server so that I can link to my phone? I am a noob with setting up webservers.  That appears what needs to be done here, right?  I've only just learned how to get one going for the Bitnodes incentive program.  So it's something I can figure out if I'm pointed in the right direction.  Thanks again.

Thanks! There are a few ways to do this. If you are running a linux machine, you can use the Docker link posted above (Thanks NameTaken). If you're using the windows app, check out the readme on how to enable remote access via browser (Search: Q. I cannot get cryptoGlance to run. What can I check?).

Whatever way you run CryptoGlance, you will need to add a Port Forward rule on your router. There's a good explanation here:

I'm trying to setup this program on my VPS, but there is only one port open on these miners. If I forward that port to one of miners I'll only see just that one miner and not the rest. An example would be

http://my_ip:4028

I'll setup port forwarding in my router but how would I configure the other miners as well? Because the main page comes up real nice on my VPS.

Thanks,

Michael

Port forwarding on the router means that you can choose any port on the outside interface of the router and forward it to an address and port on a machine on the internal interface of the router.

So say your external interface on the router is 196.345.67.1

You can have port 1001 on the external interface point to port 4028 on the miner ip 192.168.1.101
i.e. 196.345.67.1:1001 ---> 192.168.1.101:4028

But you can also forward ports 1002, 1003, 1004, 1005 etc to other machines even if they are using the same port
i.e. 196.345.67.1:1001 ---> 192.168.1.101:4028
196.345.67.1:1002 ---> 192.168.1.102:4028
196.345.67.1:1003 ---> 192.168.1.103:4028
196.345.67.1:1004 ---> 192.168.1.104:4028
etc

Note how the external IP doesn't change, but the port does, and the internal IP does change but the port doesn't

Now having explained all this I don't actually think its a real good idea to open up these ports on your router directly to the miner unless you can protect them somehow, at the least by limiting access by IP address.

[Mikestang]

Whatever way you run CryptoGlance, you will need to add a Port Forward rule on your router.

Cool, thanks for the info, I'll mess around with it tonight and see if I can get it working.