Minty Trebor

Ahh, so it could have been wrong all the time! - makes sense - at least I know I'm not going crazy!!

Yes I spotted as I posted, edit reply above! Thanks Again

Thanks for replying, the LocalTLD setting is not set to the correct value, there was a typo. I could of sworn i did not change this during the upgrade... And i didn't spot it until i took a screen shot to post in this reply. I transposed 2 letters... Thanks !!

Having a real problem getting my pfsense self signed certs to work since the upgrade (they were working before upgrade). When I put the <name>_unraid_bundle.pem file into the certs folder, and either reboot or restart nginx the pem file gets immediately overwritten. I have tried re-issuing new certs, updating/changing the server name and issuing new certs, using wild card certs (which work in my docker nginx), and I am at a loss at to what I am doing wrong. This is the cert : The server name matches : I export the .key & .crt from pfsense and cat them together into the pem file on unraid, but it just gets overwritten immediately, with an internally signed cert. I have installed my ca into windows so any certs issued are trusted: but unraid its just: I'm obviously doing something wrong, or have misread something, can anyone shed any light please? Update: Validating the Subject in the pem file:

I am a recent convert to unRAID coming from a windows 2016 server, and despite everything else going smoothly I am having an issue with VLAN's. unRAID is running on the same physical h/w as my previous windows server incarnation, and connected to my LAN using the same configuration and ports on my switch. My VLANS (ID's 14 & 15) are operational and in use elsewhere on my LAN (serviced through PFSense), and the LAN topology has remained static since before switching to unRAID. I run a 4 port Intel PCI-E nic with ports eth0 & eth1 in a LAGG for normal filesharing access. Port eth2 is reserved for Docker & port eth3 for VM's exclusively - I do not assign IP's to ports 3 & 4 at the OS level. (Just to re-iterate this is arranged identically to my previous windows server configuration using the same switch ports) I am trying to create a VM guest which operates exclusively on VLAN 15. (In windows hyper-v I was able to configure the guests NIC to be tagged to a specific VLAN ID, and this worked with no issues.) In unRAID I have tried setting up both a VLAN in network configuration settings (eg eth3.15) and within the Guest O/S, neither worked, and due to my limited Linux VLAN experience I am at a loss as to how to proceed... PFSense runs DHCP pools for both VLANS, and I am unable to get unRAID (v6.8.2) to get an IP via DHCP on the VLAN. I run multiple (non VLAN) VM's and dockers and they all work fine within the current network config. As a workaround I have enabled the MB onboard nic as eth4 and set it up exclusively tagged on the VLAN through my switch's management interface (invisible to the OS) and this works, but is not ideal. Considering I have not changed my switch's VLAN configuration for the ports used by eth2 & eth3, and it worked with VLAN tagging from windows, I am not sure this is a switch configuration issue...I have checked just in case and it appears to be correct - but at this stage who knows.. I am sure I am doing something wrong or missing something obvious, but I would appreciate any ideas..... Thanks