WashingtonMatt
Members
-
Joined
-
Last visited
Everything posted by WashingtonMatt
-
I started having this issue on 6.8.0 with a Ubuntu VM with multiple cifs mounts. Adding "vers=v1.0" seems to have cleared it up. Not the preferred solution though...
-
I recently upgraded from 3.10.8 to 3.10.10. I had been putting it off since I was pretty sure it would break, and it did. I saved the backup config prior to upgrading and followed the process posted previously, and imported old recodings, It really wasn't as big of a deal as I expected. Note: After starting up new 3.10.10 docker, it took forever (like 20 minutes) before the login page was accessible. Was still unable to login, and the restore from backup link was not available. In order to access the restore from backup link, I had to edit the system.proprties file and set "is_default=true".
-
All currently supported versions of FreeBSD (11, 12,12.1) do not detect any emulated network interface. I discovered this after upgrading from FreeBSD 11.2 to 11.3. Rolling back restores network interface. I have reproduced the issue by downloading the installer ISO for 11.2, 11.3, 12, 12.1, and creating new VMs. ONLY the 11.2 installer is able to detect a network interface. Q35-3.1 SATA primary vdisk e1000-82545em I believe something in unRAID needs to be updated for continued compatibility with supported versions of FreeBSD. I believe this is isolated to unRAID, but I don't have a way to confirm. I am currently unable to install security patches due to not being able to upgrade to a supported version of FreeBSD. I understand FreeBSD guest on unRAID is not popular, so please at minimum take a few minutes to confirm the issue, and state whether you intend to resolve the issue in future releases so I can make a decision on how to proceed. I have posted about this on the thread below, but have not gotten any responses. unraid-diagnostics-20191119-2116.zip
-
Thank you Leoyzen for all your recent input and explanations. I would love to see a guide to a get a proper base install of macOS on unRAID.
-
I had the same issue. I just rolled back clover to 46xx until I had time to dig into it more.
-
So that's showing you that your windows device is using a ipv6 dns server 2601:640... It should be your pi-hole ipv4 address .You need to check your dhcp server dns settings. Make sure it's only configured to hand out your pihole address.
-
Your windows device should only show a single ipv4 dns address of your pi-hole. I'm not even sure what that other address is... I assume it's a valid ipv6 short format. It's probably what's doing your dns name resolution. open a command prompt and run command: nslookup www.google.com
-
So I just updated without issue. My port stayed at 7080. I also just started with this docker last month v3.10.1.
-
So we're good to go on this update?
-
Same issue in this thread
-
I setup DHCP reservations for all VMs and name them accordingly. vmName12 - 192.168.0.12
-
I finally got iMessage to work by following the guide above, BUT only for older iCloud accounts. Only the two older accounts of my family of 5 work. I'm not sure if I got them blocked by not being aware of the iMessage issue, or I've read posts around the net suggesting newer accounts are being treated differently and will require a support call to Apple to activate iMessage.