fhahn

Thanks. Frank Hahn

It now looks to be working. I took one of the sample subdomain.conf files and copied it and named it after the VM that I have setup. I modified these lines: set $upstream_app 192.168.100.8; <-- IP address of the VM set $upstream_port 443; <-- Port that I want to forward to Apache on the VM set $upstream_proto https; 90% of my site now works. I have a couple of web pages that revert from https://www.example.com to https://example.com when I click on them but that may be a configuration error on my part. I need to investigate further. My last question is can I only do a reverse proxy on subdomains? For example, www.example.com? Or can I make it also work for just example.com? I was going to try and modify this line from this: server_name www.*; to this: server_name www.*,example.com; Thanks. Frank Hahn

There is a default file found here: /mnt/user/appdata/letsencrypt/nginx/site-confs/default It has the variable proxy_pass but it is commented out. There is also a proxy_pass statement in each of the individual *.subdomain.conf.sample files found here: /mnt/user/appdata/letsencrypt/nginx/proxy-confs/ Do I modify each of the ones that I have setup? Presently, I have these configured: deluge.subdomain.conf jellyfin.subdomain.conf nzbhydra.subdomain.conf sonarr.subdomain.conf Each of these have the proxy_pass statement which looks like this: proxy_pass $upstream_proto://$upstream_app:$upstream_port; So I should edit each of the above files with something like this: proxy_pass 192.168.100.20:8080; Frank Hahn

I have two Unraid servers. On server one, I have several virtual machines (VMs) running Ubuntu. In one of these, I have Apache and several applications running. On server two, I have several dockers running. These are the typical dockers like Sonarr, Deluge, etc. I also just installed the linuxserver/letsencrypt docker as a reverse proxy. The dockers that I have configured to use the reverse proxy are working as expected. I followed the directions in the video by SpaceInvader. What I would like to do is use this same Letsencrypt docker for my VMs on Unraid server one. I am guessing that I will need to create a new proxy.conf file but have not found anything online that points me to what I should include in that file. Thanks for any help. Frank Hahn

There is a video on Youtube by Spaceinvader One titled "How to Passthrough Harddrives, Convert Disks and test Vdisk Performance in unRAID VMs". Here is a link I hope: https://www.youtube.com/watch?v=QaB9HhpbDAI I do this for a VM running Ubuntu that I installed nZEDb on. I did not want to have to go through setting up nZEDb again. Frank Hahn

I think the problem has been solved though I am not sure what may have caused it in the first place. It does look to be caused by the Watch Dog system built in to the motherboard. The motherboard is a Supermicro X8DTL-iF and there is a jumper on the motherboard. Having pins 1 and 2 jumped are the default. The motherboard manual also says the Watch Dog BIOS setting must be enabled for this to work. Right now, with pins 1 and 2 jumped, the computer reboots about every five minutes no matter the Watch Dog BIOS setting. I have removed the jumper and things are now working again. I did clear the CMOS and reset the BIOS settings but if pins 1 and 2 of the Watch Dog jumpers are jumped, then the motherboard will consistently keep rebooting. My BIOS is at the latest version so I don't think flashing a new version would help. Thanks for the help. Frank Hahn

I have checked and it is disabled. I have changed the setting to enabled and saved the changes. I am rebooting and will chaage it back to disabled. I need to download the motherboard manual and make sure I am not missing a setting. I am going to take pictures of all of the BIOS setting pages and then do a reset of the BIOS and see if that helps. Thanks. Frank Hahn

I should also say that the IPMI plugin shows the power supply voltages and they all looked to be within range. I am going to try the system on a different outlet today and see if that makes a difference. Thanks. Frank Hahn

There are four fans in the system. One in the front, one in the back, and one on each of the processors and all are working. In the BIOS, the CPU temperatures are low enough that they are not displaying. When I had the CPU temperatures displaying on the unRAID web interface using the IPMI plugin, the temperature was around 40 Deg C. for each of them give or take a few degrees. I have unplugged all drives and it still reboots. I started a memory test and it rebooted. I then went into the BIOS and it rebooted there so there must be a hardware issue somewhere that I am not seeing. I'm going to try a different Linux distribution with all the drives disconnected to see if I can catch something in the log files. Thanks. Frank Hahn

I have disconnected all drives except for the Samsung cache drive and the computer is still rebooting. I plan on running the memory test tomorrow. I'm just not sure what could be going on. I don't think it is the bootable USB drive. I took it out and ran a chkdsk on it and no errors were found. I'm not sure if I can copy all of the files off, format the drive, copy unraid back on, make it bootable, and then copy all of the config files back without loosing my setup or not. Thanks. Frank Hahn

I updated my two system to 6.3.2 a few days ago without any issues. This evening, I install the IPMI plugin just to play around to look at the system parameters. I then decided to go into the BIOS and see what the settings were. Initially, the motherboard was set to grab the IP address statically. I then changed it to DHCP for no reason. I then rebooted the system. Since then, the computer keeps rebooting every 3-5 minutes. I am not seeing anything either in the logs or on the screen to give me a hint. The rebooting occurs with or without the disk array being mounted. I have also removed the IPMI plugin even though I don't think it has anything to do with what is going on. The motherboard is a SuperMicro X8DTL-iF. It has two processors and 24 GB of memory. I have attached the diagnostic files in case they prove useful. Thanks. Frank Hahn barney-diagnostics-20170222-2055.zip

Yes, it's only the very first boot of the installer that doesn't work with qxl. As soon as you have a running image, qxl works fine. In your screenshot, it has qxl listed for video. If you had changed that to cirrus, it would install properly. I changed the video option to cirrus and the Windows 7 installer worked like it should. Thank you. Frank Hahn

I'll read through these threads to see what they say. I was able to get a system running last night via a workaround. I created a Windows 7 VM on Virtualbox and saved the VM in *.qcow format. I was able to copy this file over and got the system to boot. I'll take a look at the above items and see if I can things figured out. Thanks. Frank Hahn

I'm pretty sure that I did but I will check tonight. Thanks. Frank Hahn

Hello: I am having issues creating a Windows 7 virtual machine. No matter what selections that I make when creating the VM, the install will start and it reaches the point where the screen displays "Starting Windows" and shows the four colored flag and that is where it ends. It will stay at that point indefinitely or at least an hour or so. By that point, I typically shut it down. I have attached a diagnostics file. The machine itself is a SuperMicro board with dual Xeon processors. The board has 48GB of memory. I have tried assigning different amounts of processors from 1 to 4. I typically assign the VM 4GB of memory. I am using VNC to view the VM. I am not trying to pass video cards or anything like that. I just want the VM to run in the background so that I can run a database on it. The first two screen shots show my VM selections from my last try. Let me know if there is additional information needed. Frank Hahn homer-diagnostics-20170131-1729.zip