PTRFRLL

Members
  • Posts

    78
  • Joined

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

PTRFRLL's Achievements

Rookie

Rookie (2/14)

23

Reputation

  1. The password should change, Pulseway hashes it for you so it's not stored in plaintext. As for the username, that shouldn't change. I suppose the simplest way to troubleshoot is: Disable the Pulseway service: /etc/rc.d/rc.pulseway stop Edit the config.xml located here: /etc/pulseway/config.xml Re-enable service: /etc/rc.d/rc.pulseway start Check if config.xml is still "intact" with your edits/Unraid machine is showing in Pulseway
  2. That all looks good to me. The contents of /boot/pulseway/config.xml are what you'd expect? With your info, etc?
  3. Are you sure your config.xml file is being copied to the correct location on boot? What's in your /boot/config/go file?
  4. How long has it been running? Most sites calculate your hashrate by averaging over a 24 hr period
  5. It should be listed under the Nvidia Driver section in Settings or you can run nvidia-smi -q in your console
  6. Add the NVIDIA_VISIBLE_DEVICES variable to the docker container and specify the GUID of the GPU you want to use (see the Specify GPU section in the first post)
  7. I haven't had much time to dedicate to this but it is still on my list. I hesitate to add it directly to this docker as the current method requires a specific version of nVidia drivers to be installed and I prefer to not force that decision on people (it also makes support a nightmare). My current plan is to create a separate docker that contains the over/under-clocking options which will persist those settings across all dockers. That way you could use that docker in conjunction with the T-rex one or any others.
  8. The WALLET variable on the docker is passed to the -u flag of T-Rex, so just enter everything in that field:
  9. Yes, you should be able to run two instances, just expose one GPU to each.
  10. Thanks for the link for NSFMiner, I hadn't seen that container before. I'll see if I can integrate the OC capabilities into this image as well.
  11. you could always route the Trex container through a VPN container:
  12. I see your server is set to raven.f2pool.com:3636 but does it have the stratum+tcp part at the beginning like so: stratum+tcp://raven.f2pool.com:3636
  13. You should be able to mine Raven using the kawpow algorithm. Did it throw a specific error message?
  14. I updated the Docker to include a PASS env variable, so you can now override the default
  15. I'll add a PASS variable that you can set for the container.