Month: January 2020

Others have identified this as a machine with the wrong OS on it, an incompatible version of the OS on a Mac.  However, I have found another cause. To resolve the issue if it occurs, if it is caused by circumstances like mine, you would hold option+command+R then go into recovery and choose time machine and roll back.  Then try again. In my case I saw the Mac had updates.  I selected to do the update which downloaded a 1.2gb file.  During that download process I noticed that this mac could have Catalina installed (a new version of the OS).  During this download the updater indicated that it wanted to reboot.  I cancelled that.  I let the Catalina downloader (no it hadn't installed anything, it was just downloading) go for…

This is one of those absolutely inherently bad policies -- to save your passwords online on a 3rd party's site.  It is one of those self-evident things such as all people being created equal.  We do not save our passwords onto a 3rd party site, especially Google's. I encountered this today and went looking for a way to turn it off, to turn off the prompt.  I'm someone uneasy with the idea that it is even there, because even if you say no they could still do it and you'd never know.  Google is known to be a company that tracks and monitors you at every angle, and giving them this sort of capability on Android is absolutely dangerous.  They have also been known to lie saying that they weren't…

One moment it worked the next it didn't.  Why proxmox would be fingerprinting the console is beyond me.  It shouldn't be. What's happening is that if you have canvas blocker then launching the console for a VM it can cause this error message.  Disable canvas blocker and you will be able to connect again properly. Now to find a way to keep canvas blocker enabled and get in.  As I said it worked one minute then not the next.  Did they update canvas blocker? I disabled it and launched the VM again from within Proxmox.  That worked.  I then turned canvas blocker back on and tried again.  Nope, wouldn't launch. I then decided to leave it enabled and I closed the browser and then relaunched and tried again.  This worked. …

Windows itself has one major failure and that is the registry.  This registry keeps all the settings for the operating system, the hardware, drivers, and varous components that go into making Windows work. https://www.ghacks.net/2019/06/29/microsoft-explains-the-lack-of-registry-backups-in-windows-10/ The problem is that this set of files that comprise the registry are no longer being periodically backed up by Windows 10 starting with Version 1803 and all subsequent versions. In my line of work having to deal with a bad registry can only be resolved by resorting to these backup files.  If the computer has a failing hard drive and this causes the registry to corrupt having a good version for the next reboot is important, even if it requires a little manual intervention.  Meaning, if I have to copy some files outside the OS…

Samba needs to be configured (at the share location) to allow the user that you are connecting with to actually connect.  In Linux you can create a Linux user and grant that user samba access.  The samba password can be different than the Linux account password.  Before you can add a samba password to this user you must have created a Linux user.  If you already have a Linux user then you can just add that user to samba. Ensure you have your "smbpasswd -a" set for the user. This would be something like "sudo smbpasswd -a joe".  Enter the samba password that you want to add for this Linux user. On the Proxmox storage setup screen you enter the samba password instead of the Linux user's password unless they…

I'd been attempting to switch from http preferred challenges for cert renewal/verification.  The reason is that the certbot program fails in cases where if I have existing domains in the cert adding more domains or subdomains to existing certs fails.  Basically when you try to add new domains or where the subdomain is new to an existing domain that's listed in the cert, certbot using "--preferred-challenges http" fails with error messages that do not make sense to the average person, even those that that used Letsencrypt since their inception. In my case I had to add two domains to my cert and also to add a series of subdomains for each new domain to make the domain operate just like the existing ones would.  I also had to add a…