ljm42

Administrators
  • Posts

    2688
  • Joined

  • Last visited

  • Days Won

    11

ljm42 last won the day on September 28 2021

ljm42 had the most liked content!

8 Followers

Converted

  • Gender
    Undisclosed
  • Personal Text
    the answer to life, the universe, and everything

Recent Profile Visitors

18591 profile views

ljm42's Achievements

Proficient

Proficient (10/14)

471

Reputation

1

Community Answers

  1. Just to level set... On the login screen there is a "password recovery" link that takes you here: https://wiki.unraid.net/Manual/Troubleshooting#Lost_root_Password It says to delete all three of these files from the flash drive and then reboot: config/passwd config/shadow config/smbpasswd Are you deleting all three or just config/shadow?
  2. Sorry, at this time we only make the latest backup available for download
  3. Oh that screenshot helps a lot - it looks like both NICs are in IOMMU group 12. You can only assign an entire IOMMU group to vfio-pci, you can't assign partials. Since eth0 is in use by Unraid, everything in IOMMU group 12 is effectively "in use". For starters I would see if there is an updated bios for your motherboard. Here is a recently example of someone who got a beta bios that did a better job of splitting IOMMU groups: https://forums.unraid.net/topic/118297-iommu-bind-group-devices-vfio-pciids/?tab=comments#comment-1083855 It isn't ideal, but another option is to go to Settings -> VM Manager -> Advanced View -> and take a look at the help for "PCIe ACS override", it is a way of splitting IOMMU groups up.
  4. Thank you for the kind words The connection that allows the dashboard to show how many apps are installed/started, vms created/running, etc has gone offline. You can bring it online by opening a webterminal and typing: unraid-api restart We are readying a new release that will hopefully resolve this. I don't have anything to announce regarding encrypted flash backup.
  5. It looks like you ping'd the internal host, please ping the external host (has 'www' up front): ping www.yourpersonalhash.unraid.net you want to confirm that the external host IP matches the 98.1.x.x IP address you got from the curl command. Also, I'd really recommend that you use something other than port 443 as the WAN port. In the docs we say "We highly recommend you choose a random port over 1000 rather than using the default of 443. i.e. something like 13856, 48653, etc"
  6. For anyone who finds this topic in the future, please see this thread for an explanation and discussion of the updated certificate/DNS/LocalTLD tests in Fix Common Problems:
  7. Hi folks, if you think you were hitting some false positives with the recent certificate and LocalTLD tests, please update to the latest Fix Common Problems and run the tests again. If it is still flagging issues I'd recommend cleaning them up before moving to 6.10. If you have a custom certificate this tests that the "Subject: CN" of that certificate matches the [servername].[LocalTLD] settings of your server. If you use a custom wildcard cert, it verifies that the "Subject: CN" is *.[LocalTLD] . Unraid does not use the "Subject Alternative Name" fields. See Settings -> Identification to set the [servername] and Settings -> Management Access to set the [LocalTLD] If there are warnings about a "Missing or Wrong DNS Entry for host" that means the server is not able to lookup an IP address for [servername].[LocalTLD] . In other words, if your servername is "Tower" and you specify the LocalTLD as "mydomain.com" then this tests that Unraid is able to do a DNS lookup for "Tower.mydomain.com". The point of this is to catch errors where people have provided an invalid LocalTLD. (i.e. don't add your ISP's domain name to the LocalTLD, unless Tower.myispsdomain.com actually resolves to the server's IP) (There is a corner case where you might have Unraid setup to use a different DNS server than the rest of your network. In this case, as long as the rest of the network is able to resolve the server's IP, it should be ok to ignore the test.) If you get warnings about having a blank LocalTLD, you should either set that to "local" or an actual domain name. This will help with any SMB connections that rely on MDNS (including Windows 11) regardless of the version of Unraid that you are running. Need clarification on something? Feel free to ask if the above does not cover it
  8. It sounds like you need to generate a set of private and public keys, hopefully when you give them the public key they will give you a full config file and not just an ip addess. There are many ways to generate a set of keys, probably the easiest would be to go into the webgui and create a dummy wireguard tunnel and peer, and then press "Generate Keypair". You can delete this dummy tunnel and peer, but be sure to keep a copy of the public and private keys. Once you get the config file from the provider you would import it per the instructions on the first post of this thread. Then add the public and private keys you created earlier as the "Local" public and private keys. If they expect you to build the config file on your own I would probably move on to a different provider.
  9. Probably best to start fresh by following the instructions here: https://wiki.unraid.net/My_Servers#Configuring_Remote_Access_.28optional.29 Pressing the "check" button after applying the changes is critical. If the check succeeds then you are good to go. If it fails then it is most likely a port forward issue, although it could potentially be a DDNS issue. DDNS can be tested by opening a webterminal and typing: curl https://wanip4.unraid.net/ That will tell you Unraid's WAN IP. Then type: ping www.yourpersonalhash.unraid.net The ping itself may fail but if it resolves to your WAN IP then we know DDNS is working properly. The "check" button has a remote server try to access: https://www.yourpersonalhash.unraid.net:WANPORT/robots.txt If that fails, but DDNS is good, then pretty much the only thing it can be is a bad port forward.
  10. If I had to guess based on the information here, I would say that your port forward is pointing at the wrong port on your Unraid system, so whatever is responding is responding with the wrong certificate. Please see these instructions for setting up the optional Remote Access feature of My Servers: https://wiki.unraid.net/My_Servers#Configuring_Remote_Access_.28optional.29
  11. In your browser, visit https://wanip4.unraid.net/ and note the ip address. This is your WAN IP address that your browser is using to make its Internet connection. Then from the Unraid webgui open a webterminal and type: curl https://wanip4.unraid.net/ That shows Unraid's WAN IP. If those IP addresses are the same then the systems are on the same network and the dashboard will display the Local Access url. If they are different then the systems are on a different network and so we show the Remote Access url.
  12. That is great news, it will help with whatever you decide to virtualize!
  13. Not sure what went wrong, but glad you are back up and running
  14. Please test again when the next version of Fix Common Problems is available, thanks!