SpaceInvaderOne

Probably the problem is due to your isp blocking port 80, which some do. Because of this HTTP authentification will fail. But you can work around this but you will need to buy your own domain. Then sign up for a free Cloudflare account and add your domain to it You would point your own subdomains (using cname) to your duck DNS (example nextcloud. sonarr. radarr. yourdomain.com to myserver.duckdns.org) When this is set up you would then change the template for lets encrypt to use DNS authentification and Cloudflare like this. Then you will need to goto your appdata share then letsencrypt and the folder dns-config Here you will find a file called cloudflare.ini in this file you will need to put your email address which you used to sign up for cloudflare and also your cloudflare api key. Once you have done this, restart lets encrypt and it will validate and generate the certs that you need. Hope that helps.

Is there any reason why you need to have the same ip assigned to a container or to connect through hostname each time it starts. For most purposes you would use the servers ip address and the port which the container is using to access the container. For example for me nzbget is on port 6789. So to access it i type the ip of my Unraid server (10.10.20.199) the the port So 10.10.20.199:6789 So if i wanted to configure sonarr to talk to nzbget i would tell it to use that ip as that mapping will not change. However there may be use cases where by you might want to have containers talk by host name. For example using a reverse proxy it is easier to use hostnames. To do this you have to use a custom docker network. I showed how in the video i made on letsencypt reverse proxy here that you may want to check out. https://youtu.be/I0lhZc25Sro?t=688

If you are dropping into the UEFI shell then it is most likely a problem with the install media. It is trying to boot but not finding any UEFI compatible media to boot from. This could be one of 2 things 1. (most likely) that the win 10 media isn't UEFI compatible so doesn't boot. I have had old windows 10 images I downloaded a while back and they aren't UEFI compatible. So get a new image, try downloading Windows 10 directly from the Microsoft website here https://www.microsoft.com/en-us/software-download/windows10ISO 2. The VM template is trying to boot from the vdisk first. So the boot order means the windows 10 install media isn't being booted from. Its trying to boot from the vdisk and cant so dropping into UEFI shell. So delete the windows template that you are using now and start from scratch and start fresh to avoid this.

Thanks, Greygoose. I really appreciate your support Glad you have the macOS vm up and running.

The problem is is that the disk image clover.qcow2m is well a qcow2 image MacOS VM will boot a qcow2 image fine. But it seems like you forgot to set the disk type as qcow2 for this one and it is expecting a raw image. Easiest way to change it (as you cant change it in the template now) is just to change the xml from this. <driver name='qemu' type='raw cache='writeback'/> to this <driver name='qemu' type='qcow2' cache='writeback'/> Then it will boot fine and not hit the efi shell

You can enable bridging on the 10 gbe adapter in Unraid then pass a virtual adapter to pfSense. Using vmxnet3 ( <model type='vmxnet3'/> ) will probably give better performance than the virtual e1000 in the pfSense vm for the 10 gbe.

I have updated my guide for MacOS. Shows how to install Mojave and High Sierra and passthrough various hardware

If you create or change an existing vm to have no vdisk. Then try to add a vdisk ( from none to auto/manual) Once clicking update get the error VM creation error unsupported configuration: per-device boot elements cannot be used together with os/boot elements

Um did a bit of testing tonight. Not good news for us AMD guys. Forgot that AMD virtualisation is svm not vmx. So svm would need to be passed on amd cpus for that to work However, running sysctl machdep.cpu.features on osx it doesnt show svm as present. Strange as if i do the same on a debian vm then run cat /proc/cpuinfo I can see svm passed even through I am running that vm also with emulated penryn same as my osx vm Thing is I dont think that docker will ever work on a vm hackintosh using an AMD cpu. I think it will always look for vmx (not svm) because apple never thinks an AMD cpu and thus SVM will be present. So it will fail and not load complaining about the cpu. I dont have any intel hardware here to test with to see if docker would work on an intel based vm hackintosh with vmx & rdtscp passed. I think it should. Maybe @1812 , please if you have time could you on your intel vm hack try using <qemu:arg value='Penryn,vendor=GenuineIntel,kvm=on,vmx,rdtscp,+invtsc,vmware-cpuid-freq=on,'/> then run sysctl machdep.cpu.features and see if vmx is listed. Then if so check sysctl kern.hv_support and see if you get a 1. If so does docker work on osx?

Hi @dashtripledot yes you "should" be able to do this using penryn bu adding the needed features? first, you will have to make sure nested virtualisation is enabled on the Unraid server. I believe it is enabled in the latest Unraid by default. Older versions I am not sure You can check by running for AMD cpus cat /sys/module/kvm_amd/parameters/nested for intel cat /sys/module/kvm_amd/parameters/nested If you get a zero its disabled and if you get a 1 then its enabled If you get a zero then you can enable by unloading the module (also make sure all vms shutdown first) amd modprobe -r kvm_amd or intel modprobe -r kvm_intel then running amd modprobe kvm_amd nested=1 or intel modprobe kvm_intel nested=1 ------------------------------------------ Then you will have to pass through these CPU features to the XML line that you quoted - vmx and rdtscp so that line would look like <qemu:arg value='Penryn,vendor=GenuineIntel,kvm=on,vmx,rdtscp,+invtsc,vmware-cpuid-freq=on,'/> You can add any features to the cpu that the host has in this line to improve the cpu in the MacOS guest. This will improve the performance <qemu:arg value='Penryn,vendor=GenuineIntel,kvm=on,vmx,rdtscp,+invtsc,+avx,+avx2,+aes,+xsave,+xsaveopt,+ssse3,+sse4_2,+popcnt,vmware-cpuid-freq=on,'/> So either of the 2 above should make docker work in the MacOS vm. I

Hi @SpeedyVV Yes, its because the vm is on a different subnet. (using virbr0, not br0) If you change the XML for Xp's network adapter to the below it will be fine. <interface type='bridge'> <mac address='52:54:00:f3:15:da'/> <source bridge='br0'/> <model type='rtl8139'/> </interface> Hope this helps

@Squid its next weekend now!! Any chance you may have some time ?? 😁

This is a video about the Unraid Flash Drive and how it is used by the OS. It shows how to create the Unraid Flash drive on Windows, MacOS and Linux both with the Unraid Flash Creator and also manually. It covers how to backup and restore the Unraid USB flash device. And finally how to replace the Flash Drive with a new one and transfer the license to the new USB flash device. Hope its useful

Great thanks. Will do. .........Alexa set reminder.......whats the reminder for? .....to remind @Squid ...... when should i remind you? .... Next saturaday.....what time?.....10 oclock.....is that 10 oclock in the morning or the evening?.....the morning.....ok i will remind you to remind squid at 10 oclock on saturday......thankyou Alexa... Ok lets see if bloody Alexa will work !! 😁

Hi @Squid is there any chance you could make an option so that we could have a custom tab just open over the parent window. i would really like to have a link from each of my servers, to the other server's webGui like this. Then i could easily switch from server to server from with the Unraid webGui 😀Please! 😀