Unifi Controller Java CPU 100%

Wednesday, 19 January 2022 14:52
Tim Ramsey
0 Comments

If java is using too much CPU you can try the following modification. I was using a 1GB Memory droplet from Digital Ocean, but I needed to upgrade to 2GB to be able to make this adjustment.

While I didn’t make this additional adjustment, Unifi says you can enable a high-performance garbage collector with the following setting.

https://help.ui.com/hc/en-us/articles/115005159588-UniFi-How-to-Tune-the-Controller-for-High-Number-of-UniFi-Devices

It looked good for about 4 hours, but then it spiked to 100% again. I tried upgrading MongoDB, so we will see

Update Unifi Controller on Linux

Wednesday, 12 January 2022 21:11
Tim Ramsey
0 Comments

If you have a controller on a Linux box, use the following commands to update the system and install the new update

Code Signing Desktop App

Tuesday, 04 January 2022 14:22
Tim Ramsey
0 Comments
  1. Open a Powershell prompt.
  2. Create a new self-signed certificate for Code signing using “New-SelfSignedCertificate -DnsName “yourdomain.com” -Subject “CN=The Name of Your App” -Type CodeSigningCert -CertStoreLocation cert:\CurrentUser\My“. This will create a certificate in the Personal\Certificates folder of the Certificate Manager. You can view this by running “certmgr.msc” from a Run box.
  3. Export the certificate’s public key to an external file for import into the trusted publishers folder of Certificate Manager using “Export-Certificate -Cert (Get-ChildItem Cert:\CurrentUser\My -CodeSigningCert)[0] -FilePath “My Code Signing Cert.cer”. Note the “[0]” brackets after the Get-ChildItem call. This implies that the certificate that you want to export is the first child item found. If you have multiple code signing certificates in your Personal storage you may need to modify this parameter. You can always double-click on the CER file that is exported to see if you’ve gotten the correct certificate.
  4. Import the certificate file that you just exported to the trusted publishers storage using “Import-Certificate -FilePath ‘.\My Code Signing Cert.cer’ -Cert cert:\CurrentUser\Root“. This will trust the certificate on your development workstation.
  5. Finally, sign the executable file using “Set-AuthenticodeSignature .\MyApp.exe -Certificate (Get-ChildItem cert:\CurrentUser\My -CodeSigningCert)[0]”. The same caveat regarding the “[0}” array index applies here. This is the command that I could not locate. I kept using SignTool to sign the executable but it never worked. I’m not sure if it was the trusted publisher problem, or this step. This command specifies Authenticode so I think this may have had the most impact.

After that you should have the executable show up with a certificate when authenticating with Quickbooks.

https://help.developer.intuit.com/s/question/0D54R00007GdUpJ/how-to-use-signtool-to-certify-my-quickbooks-application

Note: I got most of the information that I used from this StackOverflow Q&A, particularly the answer from @chaami:

https://stackoverflow.com/questions/84847/how-do-i-create-a-self-signed-certificate-for-code-signing-on-windows

Github publickey denied

Thursday, 30 December 2021 21:04
Tim Ramsey
0 Comments

If you ever get a publickey denied error while trying to setup a github repo on a hosting account follow these steps.

  1. Create a new Public/Private SSH on server
  2. Copy public key and add a “deploy key” on github
  3. Add your privatekey to the git config