Jump to content


  • Content count

  • Joined

  • Last visited

Community Reputation

4 Neutral

About DoItMyselfToo

  • Rank
    Advanced Member

Recent Profile Visitors

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

  1. DoItMyselfToo

    Deleted VM, Can't Access PCI NIC

    Getting back to your title of your post, I had a problem where I couldn't access the quad nic. What I discovered was this: in "System Settings" - "Network Settings" under "interface Rules", the mac addresses got out of order. I think this was a result of rebooting into GUI mode where the quad nic was not stubbed out, and me making changes and rebooting multiple times to 'fix' the problem. At some point, I looked at this and thought that it looked disorderly, and I figured that it really should be in order. It was more an intuition thing. So, I reordered them, clicked apply, and rebooted. I could then access the quad nic.
  2. DoItMyselfToo

    Deleted VM, Can't Access PCI NIC

    If you follow Spaceinvader One's guide, the "append" to the syslinux config is put in the spot for accessing unRAID via the default menu. If on the other hand you boot into unRAID via the GUI mode, then you must also append that. I found this out when configuring my pfsense vm and having to reboot multiple times, so I needed to login to the server directly via GUI mode, because the network would be down and not have access to unRAID to make changes, etc. Here's how: 1. From the "Main" tab, click on "Flash" as in Spaceinvader One's video. 2. Click on "Advanced view". 3. Notice the "Unraid OS" mode where you can see your previous append. 4. Notice the "Unraid OS GUI Mode" just below. 5. Append "Unraid OS GUI Mode" just like you did the standard mode. 6. Click "Apply" and reboot.
  3. DoItMyselfToo

    NextCLoud No webUI access

    well, it's working when you type in your proper reverse proxy address into a web browser. right? the config file changes make the docker gui redirect to that. that's where i would be looking. if it were me, i would take a short break and then come back with a fresh set of eyes. i would turn on the reverse proxy video and watch starting at 22:30. remember that the config file needs to be opened and saved using a proper text editor.
  4. DoItMyselfToo

    NextCLoud No webUI access

    remember when you made changes to the nextcloud config? go back to that and double check all the entries.
  5. DoItMyselfToo

    NextCLoud No webUI access

    it's been a little bit since i set mine up. there are a lot of parts to this setup. i would check all your settings.
  6. DoItMyselfToo

    NextCLoud No webUI access

    delete your browser cache.
  7. DoItMyselfToo

    Deleted VM, Can't Access PCI NIC

    if you were seeing the quad nic under network settings, even with the "append" statement installed in syslinux config (and had previously rebooted to get the append to take effect), i venture to guess that you're logging into unraid by booting into GUI mode. is that correct?
  8. DoItMyselfToo

    NextCLoud No webUI access

    did you use Spaceinvader One's videos on nextcloud and setting up a reverse proxy with let's encrypt?
  9. DoItMyselfToo

    Deleted VM, Can't Access PCI NIC

    can you narrow down what you did? because if it was only some changes in pfsense and you reinstalled pfsense, then you should be up and running. i first ran pfsense as a vm in unraid, following Spaceinvader One's video. it works. but because rebooting the server reboots the network, it requires more patience to allow the network to catch up. and it's especially important to avoid making impulsive and quick changes (not saying you did this), but ask me how I know. if you take out the "append" statement from the syslinux config and reboot, does your quad nic show up under network settings?
  10. DoItMyselfToo

    MCE Hardware Errors in unRAID - Full Sys Logs Attached

    i received another similar error notification from Fix Common Problems. checking the logs is see the following hardware error, which is similar to the one above, excepting it's for CPU1. full logs attached. i checked the SEL. no errors logged on the motherboard, either in the ipmi/bmc or the memory. seems like if the problem is with the motherboard dimm slot, then the ram wouldn;t be recognized. or if it's the ram, then i would expect to see error messages in the motherboard logs. but no logs posted. i've had only two errors, and they seem to show up under heavy load. recently i've been messing around with transcoding video and the ram gets hot, especially some ram modules for CPU1. i changed my fan settings from balanced to performance, to increase the cooling a little, though i don't expect this to be a fix. it just needed to be done anyway. i've researched mce errors. it looks like errors of this type mean that the ram is going bad. if you've experienced this issue or just have experience with mce hardware errors, i would love to hear from you. any input would be appreciated. thanks. diagnostics-20180918-1234.zip
  11. DoItMyselfToo

    really liking user shares

    really, i'm quite new to unraid. i grabbed my trial key in june '18, and i purchased my license shortly after. initially, i didn't care for user shares. likely this is because i had been so accustomed to my user experience so focused at the disk level. because of this, i managed my disks in each user share when i created them. after about three months my general feeling about user shares has changed; i love user shares. user shares made my life so much easier yesterday. i noticed a disk getting low on available space. i saw this coming. so i already had another empty disk formatted and ready. so, all i had to do was open the user share settings, and under the "included disks" setting add the empty disk and click apply. done. i didn't have to concern myself with pointing any programs to the new disk because the user share takes care of that for me. did i already say that i love user shares?
  12. DoItMyselfToo

    MCE Hardware Errors in unRAID - Full Sys Logs Attached

    well, i checked my hardware logs. no errors. i rebooted my system. fix common problems shows clean bill of health. at this point, i'll remain aware and see if any other log issues arise.
  13. periodically i run the fantastic Fix Common Problems plugin from Squid's repository. today, it kicked out this error message: Machine Check Events detected on your server. and the suggested fix: Your server has detected hardware errors. You should install mcelog via the NerdPack plugin, post your diagnostics and ask for assistance on the unRaid forums. The output of mcelog (if installed) has been logged. looking at the logs, i'm seeing a possible ram issue. a second set of eyes to be sure i'm not missing anything else would be appreciated. thank you in advance. diagnostics-20180915-0946.zip
  14. provisioning continued to fail, even after entering the custom option in pfsense dns resolver. finally, i had the idea to log out of pfsense and then log back in again. after doing so, provisioning completed successfully. i spent a good amount of time setting up ssl login on my unraid server. after searching the unraid forum and not finding a solution, i was able to get provisioning to finally work. the main thing with everything else set correctly was logging out/in of pfsense (above). so i thought i should share this. here are the steps to setup provisioning on your unraid server with pfsense as your firewall/router: Static ip/dns in unraid: 1. click on "settings" tab. 2. turn docker off by clicking on "docker" and setting "enable docker" to NO, and then click "apply", then click "done". 3. turn vm off by clicking on "vm manager" and setting "enable vms" to NO, and then click "apply", then click "done". 4. click "network settings" and check the following: ipv4 address assignment: <set this to "static" after the other settings are confirmed as follows> ipv4 address: <should be the local ip address of your unraid server> ipv4 default gateway <should be the ip address of your pfsense router> ipv4 dns server assignment: <set this to "static" after the other setting is confirmed as follows> ipv4 dns server <should be the ip address of your pfsense router> Provisioning: 1. in unraid go to "settings" tab. 2. click on the system settings "identification". 3. be sure that "use ssl/tls" is set to AUTO. 4. then login to pfsense. 5. go to "services" then "dns resolver". 6. scroll to the bottom of the screen and click on "display custom options". 7. in the custom options box type or paste the following: server: private-domain: "unraid.net" 8. click save. 9. click apply. 10. log out of pfsense. then log back in to pfsense again. 11. in unraid go to "settings" tab, then click on "identification". 12. scroll down the page and click "provision".
  15. DoItMyselfToo

    [Support] binhex - General

    Not sure what's taken me so long to find this thread, but it's one of the best docker support threads I've seen. Thanks on a number of levels: thanks for this thread; thanks for supporting unRAID and it's users with your Docker containers. Hopefully my donation helps a little.