Receiving emails from Ubuntu Landscape with warnings, subject line “[Landscape Alert] N computers haven’t contacted Landscape within the last 5 minutes“.
Solution:
Log in to the machine(s) mentioned in the warning and do:
sudo systemctl restart landscape-client
If you got an error message (unable to locate package libvirt-daemon-system) while uppgrading from GNS3 2.2.45 VM to a newer version. Do as follow.
go to shell
sudo apt update
sudo rm -r /usr/share/doc/libvirt-deamon-system-systemd
sudo rm -rf /var/cache/apt/archives/libvirt-daemon*
sudo apt –fix-broken install libvirt-daemon-system-systemd
exit from shell and do the upgrade
According to the manual sheet you should just push the extender section to the bottom for 6m (50 MHz) but this did not work for me. Using a NanoVNA I could find a workable configuration for both 6m (50 MHz) and 4m (70 MHz) bands.
For both bands I only used only one base pin (instead of two for HF), the coil pushed down to it’s lowest position and the tuning was done using the telescopic top part. The telescopic top part was extended partly:
| 6m | 8 sections of the top part extended, top part length 79 cm |
| 4m | 2.5 sections of the top part extended, top part length 28 cm |
If anyone has a better take on tuning on these bands please let me know 🙂 I have just tuned on SWR, no clue what the radiation pattern might be. Also, note that these are measurements that worked for me. Check your SWR.
To import a codeplug for Anytone AT-D878UV into the CPS for AT-D578UV or AT-D168UV, the only way is to export it to CSV from the AT-D878UV CPS and then import it. But for some strange reason, Anytone has decided to make the CSV formats slightly incompatible… Come on, Anytone. Why??? This bug/feature seems to be related to splitting Color Codes into RX and TX that was implemented in the 3.06 release of the CPS.
The import into the CPS for AT-D578UV or AT-D168UV will silently fail. No error message is displayed but upon investigation I discovered that the Color Codes for the DMR Channels were wrong (set to CC1 in all cases). I maintain a codeplug for AT-D878UV with almost 900 channels, so fixing this manually is not an option.
I use the latest CPS for all models, that is for AT-D878UV version 3.07, for AT-D578UV version 1.21 and for AT-D168UV version 1.06.
A workaround is to edit one of the column headers in the CSV file before importing. Which column depends if you are importing to AT-D578UV or AT-D168UV.
| AT-D878UV -> AT-D578UV | Change “RX Color Code” to “Color Code” |
| AT-D878UV -> AT-D168UV | Change “TxCC” to “TxCc” |
If you have found more incompabilities that needs to be handled, please let me know and I will add it to the article.
If you get a SIP account from a provider which isn’t really a trunk it can be configured as a trunk in FreePBX but DID on incoming calls is set to “s” so it is impossible to get an inbound route working.
The trunk in this case will only have one DID so a workaround is to set the DID “hardcoded” on the trunk in order to get the inbound route working.
Edit extensions_custom.conf and add something like this, but replace “123456789” with the DID you wish to set:
[custom-123456789]
exten => s,1,Noop(Setting DID to 123456789)
exten => s,n,Goto(from-trunk,123456789,1)Now edit the trunk and go to the pjsip tab and enter custom-123456789 (replacing “123456789” with your DID) in the Context field.
Now all incoming calls in this trunk will get your desired DID and your inbound route will be able to catch them by the DID.
It turned out that the extension earlier had been a dynamic agent for the queue, and it was logged in as an active agent for the queue when the extension was removed from the queue. This caused calls in the queue being sent to the extension still.
Solution: Edit the Queue, add the extension as a dynamic agent, call *45 from the extension (“agent logged off”), dial *45 again (“agent logged in”) and finally dial *45 one more time (“agent logged off”). Now edit the Queue again and remove the extension from dynamic agents.
The email account was set up as an IMAP account.
The reason turned out to be the fact that the Inbox of the account contained many emails (>18.000) so I just moved all emails from the Inbox to an Archive folder and the problem was resolved.
Using the template JA Simpli with a menu item displaying featured articles in a blog layout. I had set up a 3 column layout but after upgrade to Joomla! 4 and 5 the featured articles was displayed full width stacked on eachother.
Solution:
The blog layout now displays correctly and the old menu item can be deleted.
If you unable to submit forms through Contact Form 7 while not logged in (i.e. test in incognito mode) and All in one WP security and firewall is used, make sure that the Disallow unauthorized REST requests is NOT enabled in AIOWP Security and Firewall. (It is mentioned in the yellow info box *hint* *hint*.)
The settings are found in WP Security -> Firewall -> WP REST API tab
I
If you want to do a connection to SharePoint Online with a PowerShell script. You will need to make a connecting user and a certificate for logon. The legacy function with plain text user/password does not work anymore.
The PowerShell CMD-let SharePoint Online PnP has been beprecated and is replaced with PnP PowerShell. Do the following to confirm right installed CMD-let
To check if you have the right version of PowerShell. You will need at least PowerShell 7.3
1 $PSVersionTable.PSVersion
Get all installed SharePoint Online PnP PowerShell Modules
1 Get-module -ListAvailable *pnp*
If both or PnP Classic is installed
1 Uninstall-Module PnP.PowerShell -AllVersions -Confirm:$False
2 Uninstall-Module SharePointPnPPowerShellOnline -AllVersions -Confirm:$False
Some versions of PowerShell need to change the TLS to version 1.2 for uninstall and install to work
1 [Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12
Install the latest version of PnP.PowerShell. Choose install option Yes to All
1 Set-ExecutionPolicy RemoteSigned
2 Install-Module PnP.PowerShell
You have now installed the new Module
To make a connection to SharePoint Online you will need a global account to your Tenant and some information.
Make a folder for your certs at the local computer “c:\mycertificates”. Do not use spaces or local characters for the folder name. Register the account.
$result = Register-PnPEntraIDApp -ApplicationName “[MySharePointAppName]” -Tenant [TenantName].onmicrosoft.com -OutPath c:\mycertificates -Interactive
$result
Sign in with your Admin account and the script will return a client ID on success. Store the client ID for feature use. You will receive two certificates in your certificate folder.
To make a connection to SharePoint
Connect-PnPOnline [TenantName].sharepoint.com/sites/[folder] -ClientId [ClientIDNo] -Tenant [TenantName].onmicrosoft.com -CertificatePath “C:\mycertificates\[MySharePointAppName].pfx”