avinyc

Members
  • Content Count

    23
  • Joined

  • Last visited

Community Reputation

2 Neutral

About avinyc

  • Rank
    Newbie

Recent Profile Visitors

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

  1. Thank you so much, these steps are what I needed to remove my last errors and get back to all checks passed. Much appreciated!
  2. Curious how everyone updates their nextcloud with unraid. Mine is still on 20.0.5 and I see 20.0.7 available in the admin panel. I assumed the docker updates would also trigger the upgrades similar to plex, but I see from the first post there are 3 recommended options. Which is the safest approach or is it all practically the same?
  3. It looks like your interface is showing virtio instead of e1000-82545em. If you change CPU and RAM, you'll have to re-run the helper script again. Run it (maybe more than once if it doesn't return a message saying vm fixed) and then start it up.
  4. I still followed SI1's instructions for bigsur (labeled the disk and same settings in the docker) and after I finished with Catalina I upgraded to Big Sur. No issues (but it is another step of course).
  5. So I went into the vm a tried to test safari and of course it was blocked by my router. I had set up access control to prevent new devices from connecting without approval. So turned that off and started this from scratch. Selecting big sur still brings up catalina instead, but no more server connection issues. Will finish the install and see if upgrading through the VM works. My apologies for wasting others time with this stupid mistake on my end. Until the next one!
  6. I've been trying other troubleshooting options. Shutting down my only othe VM and stopping all dockers except macinabox. Still nothing. I tried googling for this error, but none of the solutions work for VM. Clock is set correctly. I don't know how to copy the installer log from VNC (copy and paste doesn't work) but there are errors in there that might be helpful too.
  7. I have a windows VM running as well. That was an easier experience:)
  8. Yes, I also echo my thanks to all those taking the time to help here! I am a complete novice so I would assume I am making some ridiculous error on my end:)
  9. That seems like the most promising explanation. It has to be something going on either in my server or router if this connection issue is not universal. I'll see if I can figure out if somehow there is a firewall problem or something causing this to fail.
  10. I am running the helper script before running the VM. After the last fresh install, the VM wouldn't show up until the script was executed.
  11. I edited the VMs XML and changed to e1000-82545em, still not working. The recovery server error persists.
  12. I tried running a fresh install and selecting method 2, none of the isos were downloading. I re-ran as method 1 and then tried method 2 afterwards, sill returns the same error that recovery server could not be contacted.
  13. Tried installing catalina and posted this yesterday. Unfortunately, once I get to the steps after formatting the drive, I click to continue and the error message is "The recovery server could not be contacted."
  14. If there are instructions on how to create or download the proper qemu BigSur-install.img file, I am guessing it can be copied to the ISO folder and the installation would work. If it's easier to wait for the update at this point, that might be better.
  15. It looks like Big Sur has been updated so maybe that's why it's not downloading through the container. Running method 2 the machinabox_Big Sur.log shows "Product ID 001-86606 could not be found." index-10.16-10.15-10.14-10.13-10.12-10.11-10.10-10.9-mountainlion-lion-snowleopard-leopard.merged-1.sucatalog has been updated to show Product ID 071-00838 which I suspect is the 11.2 (20D64) update. Not entirely sure about this, but if somewhere in the script it is looking for an old build it needs to be updated to this one now: https://mrmacintosh.com/macos-big-sur-11-2-u