Server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none

Bij het proberen te updaten van Proxmox 5 (Debian 8 gebasseerd) geeft deze de volgende foutmelding:
Server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none

Dit komt omdat het root certificaat van Letsencrypt verlopen is op 30 september 2021.

De oplossing hiervoor is als volgt:

  1. Open (bijvoorbeeld met nano) /etc/ca-certificates.conf en zet een ! voor /mozilla/DST_Root_CA_X3.crt
  2. update ca-certificates met update-ca-certificates

Bovenstaande werkt alleen mits ca-certificates geinstalleerd staat en /usr/share/ca-certificates/mozilla/ISRG_Root_X1.crt in /etc/ca-certificates.conf zit.

Remote server returned ‘550 5.7.520 Access denied, Your organization does not allow external forwarding. Please contact your administrator for further assistance. AS(7555)’

Wanneer een gebruiker probeert om e-mail doorsturen buiten de Microsoft 365 tenant aan te zetten of als de beheer probeert om een gedeeld postvak buiten de Microsoft 365 tenant te laten doorsturen dan krijgen de personen die naar de postvakken een e-mail sturen de volgende foutmelding te zien:

Remote server returned ‘550 5.7.520 Access denied, Your organization does not allow external forwarding. Please contact your administrator for further assistance. AS(7555)’

Dit is op te lossen door een uitgaande spamfilterbeleid aan te maken.

  1. Log in als beheerder binnen de Microsoft 365 tenant.
  2. Ga naar Microsoft Defender:
    https://security.microsoft.com
  3. Ga aan de linkerzijde naar E-mail en samenwerking -> Beleid en regels -> Bedreigingsbeleid -> Anti-spam.
  4. Klik op Beleid maken -> Outbound
  5. Vul een naam in zoals Allow forwarding from mike@ en een beschrijving zoals Forwarding from mike@source.nl to mike@destination.nl en klik op Volgende.
  6. Kies de gebruiker, bijvoorbeeld mike@source.nl en ik op Volgende.
  7. Zet Regels voor automatisch doorsturen op Aan – Doorsturen is ingeschakeld en klik op Volgende.
  8. Klik op Maken.
  9. Klik op Gereed.
  10. Controlleer dat Status op Aan staat.

Vragen?

Neem dan contact met ons op.

The command you tried to run isn’t currently allowed in your organization. To run this command, you first need to run the command: Enable-OrganizationCustomization

When trying to add an anti-spam policy in O365 Security Portal the following message occurs:

All the customers where we already added anti-spam policies without this message used Azure AD Connect, I think this activates the OrganizationCustomization option.

On Windows 10 of Windows 11, open elevated Powershell:

Install-Module -Name ExchangeOnlineManagement

Import-Module ExchangeOnlineManagement

Connect-ExchangeOnline -UserPrincipalName user@domain.tld

Enable-OrganizationCustomization

Just one extra step there for those who do not use PowerShell, after InstallModule, run this: Set-ExecutionPolicy RemoteSigned

Gareth

“Symantec Endpoint Protection has detected that there are pending system changes that require a reboot. Please reboot the system and rerun the installation.”

When trying to install Symantec Endpoint Security the following error may show up:
“Symantec Endpoint Protection has detected that there are pending system changes that require a reboot. Please reboot the system and rerun the installation.”

The first step would be to reboot, but sometimes this is not possible because of important system services, or after a reboot the error still shows.
Please try the following:

  1. Open the Windows Registry using regedit.exe.
  2. Search for the entry “PendingFileRenameOperations” in:
    • HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlSession Manager
  3. Restart the SEP installation; the install should finish without error.

Another service operation is currently in progress

When trying to install Symantec Endpoint Protection the following error may popup:
“Aanother service operation is currently in progress”

Try a reboot first, if not possible or problem still exists, try the following:

  1. Open Windows Registry Editor. Click Start > Run, type regedit, and click OK.
  2. Back up the registry.
    Note: For Windows Registry backup and restore instructions, see How to back up and restore the registry in Windows.
  3. In the left pane, navigate to the following key:
    HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionInstaller.
  4. In the left pane, right-click on the Inprogress key, and click Delete.
  5. Click Yes to permanently delete the entire Inprogress key and all of its subkeys.

Source: https://support.symantec.com/en_US/article.TECH218138.html

Default passwords

Below we will publish default passwords we encounter.

General (vendor):
3Com: admin/admin
Belkin: admin/admin
BenQ: admin/admin
Grandstream: admin/admin
D-Link: admin/admin
Digicom: user/password or admin/michelangelo
Linksys: admin/admin
Netgear: admin/password
Sitecom: sitecom/admin
Thomson: user/user
US Robotics: admin/admin
Zebra: admin/1234

Specific (device):
Brother MFC-L9570CDW: initpass
Brother LP844: admin/1234
Panasonic KX-UT133NE: admin/adminpass

Moving directory to another partition (part 1)

Due to the fact that the primaire virtual disk (containing the Debian OS and currently the /var) of one of our customers servers is on a SSD pool and almost reaching its capacity (>75%) we need to add a second virtual disk and move the /var folder (HDD space costs less and is fast enough to serve websites and email).

First we started with creating the new virtual disk and adding it to the VM.
Secondly we partitioned it:
1. Use “fdisk -l” to get the disk name (in our case vdb)
2. cfdisk /dev/<diskname>
3. Select new
4. Press enter at the “Specify size in MB” to use the whole disk.
5. “mkfs.ext4 /dev/<diskname>”
6. “mkdir /var2”
7. Get the UUID of the disk with the command “blkid”.
8. “echo “UUID=<UUID> /var2 ext4 errors=remount-ro 0 1″ >> /etc/fstab”

Next we can copy the data from /var to /var2 (we use rsync to preserve permissions).
We are currently running the following command to make a first copy:
“rsync -av /var/ /var2”

The next step would be stopping all services (apache, mysql, dovecot etc.) but we will continue on this after the data has been copied (which will take a full night).

Change network interface on FreeNAS Jail

Today we created a jail on our FreeNAS Server to compile a driver.
By default the jail got a IP Address from our management network and there was no GUI option to change the network interface.

We did the following:
1. Stop the jail.
2. SSH to FreeNAS server.
3. cd to /mnt/<dataset>/jails/.<jailname>
4. echo <interfacename> > iface
5. echo “<ipofgateway>” > defaultrouter-ipv4
6. warden start <jailname>