Jump to content

PilotReelMedia

Members
  • Content Count

    19
  • Joined

  • Last visited

Community Reputation

4 Neutral

About PilotReelMedia

  • Rank
    Member

Recent Profile Visitors

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

  1. Kinda interesting since this morning my large server with dual 2GHz processors has been at an idle while connected to the Rosettta@home client. I restarted the docker to make sure nothing broke and after it connected again it is still not being utilized. My faster machines are still hard at work leading me to believe that they now have so much surplus of available machines they now may be utilizing only the faster equipment in the pool. This is a good thing and more than enough in this effort is a blessing. If I don't see activity by tomorrow I may assign the slower server to another service so it too will be getting used in a productive way. Either way I'm tickled that our group has shown so much compassion and human spirit in this crisis.
  2. Thank you guys for helping us to help them in this dire time. Feels good to do something!
  3. I want to do this so bad but I'm having trouble with the basic settup. The RTP Boinc docker Space Invader One used in his example is not in plugins and I cant figure out how to configure the one that is and its very different and has no GUI . Can anyone help me get this up and running?
  4. Thank you for your response. My particular issue at the moment is that the aws server unraid employees for this provisioning service seems to believe that my server still is on internal port IP ending in 15 but now resides on internal IP ending in 30. It may need to be corrected in the aws server record but I don't have the ability to do it. When I originally built this server using a netgear router it was on internal ip ending 15.
  5. Even following the Space Invader One guide I am still unable to provision a SSL Certificate on my server. I have followed the guide: (pfSense: If you are using pfSense internal DNS resolver service, you can add these Custom Option lines: server: private-domain: "unraid.net") I am still recieving: (Sorry, an error (403) occurred provisioning your SSL certificate. The error is: Your router or DNS server has DNS rebinding protection enabled, preventing) + the encryption address... If anyone had a similar issues that they were able to resolve in PFSense please enlighten me. Thanks
  6. I am having a similar issue and didn't see a resolution here. I have followed the guide: (pfSense: If you are using pfSense internal DNS resolver service, you can add these Custom Option lines: server: private-domain: "unraid.net") I am still recieving: (Sorry, an error (403) occurred provisioning your SSL certificate. The error is: Your router or DNS server has DNS rebinding protection enabled, preventing) + the encryption address... If anyone had a similar issues that they were able to resolve in PFSense please enlighten me. Thanks
  7. Also useful information. Thank you for showing me how to isolate it in the kernel. Had it selected and thought that was all that need be done.
  8. Are you referring the assignment at the bottom of the VM edit page. If so I have the logitech device checked. "It stems from interaction between qemu/kvm, both of which we keep up with latest releases, both of which we have no control over. " <- Usefull information. Thanks
  9. Great. I will need to see what got mangled with my particular update. I appreciate the info.
  10. Wired keyboard works and I've ordered the wired version of the Logitech keyboard to replace. Would be more interested to find out if the new configuration can be modified to fix the problem. If that's of no interest to you guys then you've lost a little stock in my humble opinion. I love the community here and the shear utility of your product, but can't help feeling a bit let down by that comment coming from a Limetech rep..
  11. Please don't be confused. It appears that something in the update has boxed support for wireless logitech keyboards. Specifically the K800 and MK540 models. I use the K800 on all my machines and the only model I have been able to get passing through to the VM's is an old Asus wireless keyboard for a Eee pc. It has never been a problem before the update and since I have verified that the Logitech keyboards are working I don't think it's stretch that something in the update has caused a conflict with this hardware. I can interact with the machine but not through to VM's.
  12. Originally posted and was told to remove because my problem was probably not a bug. I have tested two Logitech wireless keyboards and Keyboard and mouse combos and only my older Asus wireless keyboard seems to work now. It's a bug! My Logitech keyboard worked fine tel 6.8.1 Can this be fixed?