SpaceInvaderOne

+1 from me. Very useful

Heres what to do if your isp blocks port 80 and you cant use http authentication to create your certificates. Also how to make a wildcard certificate.

Yep that will be because there is no config file that uses that subdomain. Just edit a config file to direct to whichever container you want to access from outside.

try passing through this aswell along with the other devices "

The error that you get "internal error: qemu unexpectedly closed the monitor" what is after that. What is the complete message please.

Were you forwarding port 443 to your Unraid server to access the webUI from outside? If not you need make no changes. If you were then you will need to change the forwarding of external port 443 to internal port 443. Change it to forward external port 443 to for example internal port 1443. Then map in the letsencrypt template port 1443 to 443 in the container like below You dont have to use duckdns if using your own domain. But you need to make sure that your subdomain is always pointing to your wan Ip if you dont have a static wan IP. So you would need to have some dynamic dns tracker. If you are using cloudflare you can setup cloudflare dns in pfSense and use that with your subdomain. Hope thats helps.

Yes that will be fine using the gtx 1050ti on its own. Like you say so long as you don't use gui mode or a vm whilst any gpu transcoding is going on then you will be fine.

Ah glad that worked Alot of private trackers don't allow these features as it allows connecting to clients which are not registered with the tracker.

Can you check in deluge preferences/network that you dont have peer exchange or dht enabled

click on the container and goto console then run curl ifconfig.co That will show the ip inside the container. Then goto https://www.iplocation.net/ you will see your wan ip here (not through the vpn) they should be different Then paste the ip from the curl command into the ip lookup page on the above location. It should report the location as CA Toronto. If it doesnt maybe something wrong with your openvpn config files

It looks like the nic that you are passing through isnt in its own iommu. You will need to break it up or passthrough everything in that group. have a look at my vid here https://www.youtube.com/watch?v=qQiMMeVNw-o&t=791s

I made a video on what the new 6.7.0 looks like etc. There is a mistake in this video where I talk about the webgui: VM manager: remove and rebuild USB controllers. What I thought it was, I found out after it was available in 6.6.6 as well so wasnt it !! Also shows how to upgrade to rc for those who don't know and downgrade again after if needs be. https://www.youtube.com/watch?v=qRD1qVqcyB8&feature=youtu.be

@limetech I have these 2 nics as part of the motherboard [8086:1539] 04:00.0 Ethernet controller: [8086:1539] 06:00.0 Ethernet controller: I was using in the syslinux configuration: xen-pciback.hide=(06:00.0) to stop Unraid from using that nic for itself as it had the same id as another nic on the motherboard as above. I have upgraded to 6.7 yet the nic is still hidden from the OS and it passes through fine to the vm. So the is this something that works now. But this kernel option will no longer work in future/final 6.7 so we are moving to the config/vfio-pci.cfg file in preparation?

It should work just changing the container name to the server ip resolver 127.0.0.11 valid=30s; upstream collabora { server 10.10.20.199:9980; } This part above sets the name collabora to 10.10.20.199:9980 so then nothing else needs changing after its defined. Then later when collabora is in the config as below, it relates to what was defined above. # static files location ^~ /loleaflet { proxy_pass https://collabora; proxy_set_header Host $host; } So then the https://collabora is the same as https://10.10.20.199:9980; But how your file is will work too specifying the IP and port each time instead.

I don't like your office chair much

Ah, @Squid I was about to post a request for a feature then read the thread to realize that I never said thank you for what you did last time. So I should just be told to f off for being an ungrateful sod. Well if you forgive me for forgetting could I ask for something else for you to consider? It would be awesome to be able to have a custom tab that runs a user script. That would be awesome. I use a script with one of my VMS at the moment. What it does is delete the vdisk of that VM then copy another 'backup' of it when the VM was first set up. So it kind of resets the windows VM to factory defaults! I use it for things that I would trust running/doing on a normal VM. Then afterward I just run the script and the VM is back how it was. Would be great to be able to click a custom tab to run that script the have it do that then start the VM. I know not many people would have the same use case as me for that but it would be cool to just be able to do things such as run a script that you often use right from any web UI page. I am sure that it would take quite a bit of work to do and I am sure that you have enough to do already. But maybe I could do a deal with you. In exchange as I live in the UK and not too far away from @CHBMB If he annoys you on the forums I could try and find his house and cut his telephone line so he has no internet

Just thought I would point out your disk 3 and 4 being ssds. You should not use ssds in part of a parity protected array as the garbage collection can break parity. It's fine to use them as unassigned drives or in the cache (or in an array with no parity drive) Just thought i would mention in case you had them in the array

Hey guys here is a tutorial on how to install and setup a Collabora Document Server and configure it to work with Nextcloud as a Docker container on Unraid. It shows how to set it up running through a reverse nginx proxy. Collabora is a LibreOffice Online document suite. this gives you control over your own documents and integrates with nextcloud. So no longer any need for google drive and google docs! This video guide makes use of @chvb great container.

The error Unknown PCI header type '127' is because the card isn't resetting correctly. This is a problem that can happen with some AMD cards. However, you have no problem with the windows VM. So why is this? Well by default there is a difference in a Windows VM and a Linux VM. The Windows VM will use a machine type of i440fx whilst the Linux VM will use a machine type of pc-Q35. I have found that you can start and stop as many VMS as you want using machine type i440fx without this error occurring. However, if you start and stop a VM using pc-Q35 then you will get this error and only a reboot will fix it. You could make a Linux VM using i440fx so then you could stop your windows VM then start the Linux one without having to reboot the server.

Yes any container that you pin cores/hyperthreads to will be restricted to running only on those cores Glad you like the videos.

part 2 now added https://youtu.be/NA_sO3rH2mU @Josh.5 sent you a pm