We have this critical error message on our dashboard of FreePBX:
We appear to have fixed the underlying cause of the notification, but when we click the (-) button to Ignore it, it comes back again after refreshing. There is no (x) Delete button for this notification.
How can we permenantly delete this stubborn notification?
We are getting notifications of two CA's expiring in pfSense - shown below in a yellow colour:
These are:
Acmecert: O=(STAGING) Internet Security Research Group, CN=(STAGING) Pretend Pear X1, C=USAcmecert: O=Internet Security Research Group, CN=ISRG Root X1, C=USI found a thread on Netgate's forum from extremely recently, which seems similar. It talks about X1 CA's, and the two that are expiring for us are also X1's.
There is no 
Renew button for these CA's.
Is it safe to delete these two CAs?
Afterwards how can we test that it has not caused any issues?
We are getting daily notifications:
A customer's server I'm administering runs the latest version of VMware ESXi - 8.0U2 Enterprise Plus, but I believe this has been a thing ever since I started using ESXi many versions ago.
Every time you login to the web client for vSphere and click VMs, the list displays in a random order (possibly in the order in which they were added). You have to remember to sort them A-Z. Sometimes if you're not paying attention, VMs with similar names can appear in the place of where you'd usually expect to see another (when sorted A-Z).
How can we keep the list of VMs sorted alphabetically, permanently?
Talking about in ESXi/vSphere on each individual server, not in vCenter.
I looked online and the answer does not appear to be readily apparent.
Here's an example screenshot from another user:
I am observing an odd behaviour in PowerShell. I can echo hi but I can't echo. to get a newline:
It does work in Command Prompt:
One answer suggests that the .ps1 file might have a BOM in it. I tried converting my script to ANSI but this did not help, and as you can see from the above it still fails even without a script file.
Another answer suggests that there might be a file named echo. in the same directory, but there isn't.
How can I fix echo. or otherwise how can I echo a newline please?
Running just echo without the . halts and prompts for input.
Running write hi works but write. fails, in the same way as echo. The same goes for Write-Output and Write-Host.
I have tried manually installing the latest version of PowerShell (v7.4.1) but this did not help.
About a month ago I installed the latest version of Docker on Debian 12 on a VMware ESXi 8.0U2 virtual machine (latest vSphere version).
I tried to get VNC running but other priorities took over, so for now I'm just accessing the VM via VMware Remote Console, using Gnome.
It has the latest version of VMware Tools installed:
$ sudo apt-get install open-vm-tools open-vm-tools-desktop
open-vm-tools is already the newest version (2:12.2.0-1+deb12u2).
open-vm-tools-desktop is already the newest version (2:12.2.0-1+deb12u2).
There is only ever 1 single container running at the same time. I regularly do docker image prune -f and docker system prune
Whenever the VM is running "on it's own" (without me connected to it via Remote Console on Gnome), it runs like a champ, and never ever goes down.
Whenever I am accessing the VM and doing stuff, it randomly hangs, and my "fix" is to reboot the VM. Trying to access the nginx server running on the container from another machine whilst it is hanging results in our reverse-proxy returning Error 503 Service Unavailable - No server is available to handle this request.
The entire Debian Docker host VM totally locks up when it does this and doesn't let me click/type and the screen freezes. I am not doing anything overly demanding. I am usually just editing a file in nano in the Terminal or something.
Sometimes I'm doing nothing whatsoever on the VM, I am simply just connected to it via VMware Remote Console - and it will go down. It does it at random intervals, but I usually get about an hour or 2 before it crashes, but this seems to change at random, sometimes I get a few hours - lately I'm getting less time before it crashes.
If I wait and don't reboot the VM then Remote Console does eventually come back to life after 5-10 minutes, the screen unfreezes, and I can give input again. The Docker daemon dies. I am not using Docker Deskop. It is installed but it is not set to startup automatically on boot/login.
Sometimes there are no containers running when it crashes. The container that I do use on there is a very simple webserver that only I access.
Sometimes (but not always) even issuing a Reboot to the VM from within VMware Remote Console while the VM is hanging won't work the 1st time (but it usually works the 2nd time):
Within vSphere when the VM is hanging I am [sometimes?] seeing the CPU sustaining 100% usage! I have reduced the CPU cores from 4 to 2 as it was causing very high CPU consumption on the VMware host server with a 6c 12t Xeon E5-1650V3. The VM has 8GB RAM.
I have no problems with any of my other (Linux, FreeBSD & Windows) non-Docker VMs.
Where do I begin trying to troubleshoot this please?
My feeling is that this is either VMware Tools or Gnome related. Whenever I'm running a Dockerfile build (but also whilst doing nothing sometimes), I have noticed that these processes often consume very high CPU:
qemu-system-x86_64
gnome-shelldocker-scoutcom.docker.backendOften the build will complete successfully, but those processes still remain using high CPU for a little while afterwards - sometimes causing a crash (when nothing is building any more).
I am not adverse to trying something on a brand new install of Debian, but I'm not convinced it will help if I change nothing else in my setup.
My basic question is: is it possible to use vCenter to apply a component update to the host, seeing as how I would need to shutdown the VMs in order to do it, and crucially 1 of them is a router VM and another 1 is vCenter itself?
I have just done a clean install of the latest ISO of ESXi, 8.0 U2. I have installed a router VM + deployed the vCenter Server Appliance latest version. It will be my only server for now - I can't really use another server to migrate these VMs to.
I see in vCenter 8 that they want you to use Lifecycle Manager Images since they will remove Lifecycle Baselines/VUM in the next version of vCenter 9. I haven't used either of them before.
My server is up-to-date with the latest image, according to the Updates tab in vCenter; however it contains an older version of the smartpqi driver (version 4495) and I'd like to install the latest version of this component driver (smartpqi version 4600) which isn't yet available in the latest ESXi ISO.
I have gone to Lifecycle Manager and done an Import Update with the Offline Bundle provided by VMware for the driver - which is version 4600 compared to the latest version available on the image which is 4495.
I have then edited the image attached to the host to add the additional component, then ran a pre-check:
I see that I need to powerdown my VMs in order to run the update.
If I do this then I would need to shutdown pfSense (router VM) + vCenter.
How will vCenter apply the update if it's VM is shutdown and it has no routing?
Will it just start applying the update once I've shutdown all VM's?
Will it require any user interaction from me during the update process? (The server is remote to me, I could order a KVM session but it's not free)
Is this the correct method to apply the component update?
This one is just the driver for the piece of hardware. I have some more vib's to install for other related things though, and the documentation from the manufacturer of the hardware suggests using esxcli software vib install to do these. Would using this method to install the driver be a better idea than Lifecycle Manager Images? This is what is suggested in the manufacturer's documentation for the driver also, using their own provided .vib file.
I am concerned that the extra .vib files the hardware manufacturer wants me to install after this driver might expect the 4600 version of the main driver component.
As an aside: I notice in the screenshot that it says Quick Boot is not supported on this host but then when I click Remediate it is enabled in the options - should I disable this?
I have a public DNS server running on a Windows server with the hostname dc01.
A nameserver for this hostname (dc01) keeps getting added to the DNS zone:
If I try to delete it, then reload the zone and refresh; the record is immediately recreated.
Running a DNS check for my domain name on MX Toolbox shows an RFC 1035 violation for Primary Name Server Not Listed At Parent in that Windows DNS Server is publishing 3 records, but only 2 records are listed at the parent DNS server (ns1 and ns2).
I could fix this by adding dc01 as a nameserver record in my parent DNS server (domain registrar), but I don't actually want 3 nameservers - I just want the 2.
How can I prevent Windows DNS Server from creating the dc01 NS-record?
As an aside, I know that the 2 nameservers should be on separate IP's.
Also, the following changes have been made to DC01 and the DNS Server service was subsequently restarted:
DNS > Zone > General > Dynamic Updates = None
NIC > Properties > Advanced > DNS > Register this connection's addresses in DNS = Unchecked (disabled)
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DNS\Parameters\RegisterDnsARecords = 0
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DNS\Parameters\PublishAddresses = 116.202.233.75
These changes prevent the internal 192.x.x.x IP address for DC01 from being published publicly to the world in the zone as an A-record. Instead the external public IP is published to the dc01 A-record.
I need to gain root access to a newly-created VM hosted on Microsoft Azure. This is done on FreePBX (running CentOS) by sending the keys Alt+F9 on the console and issuing the command !passwd root.
How can I send modifier keys to Azure's Serial Console?
We have a pfSense server in two offices. Our main office has a VPN server configured, and our satellite office has a VPN client configured, using the IP 123.156.88.253 (just an example).
We have just got a 2nd internet connection in our main office. We are about to setup link aggregation within pfSense. This will be on IP 88.175.198.87 (again, an example).
How can we alter the client VPN settings to be able to reach the VPN on either 123.156.88.253 or 88.175.198.87?
Is there a service we can buy like DDNS, except for IP addresses, rather than hostnames? I.e. we buy 189.66.78.145, which - in the background - routes to both IPs?
Or how can this be done within pfSense?
The goal is to have the satellite office be able to reach our client VPN, irrespective of whether one internet connection is down; without causing some sort of conflict that might be introduced by adding the same client VPN connection twice.
I've installed Windows Server 2016 Datacenter on a physical machine called LOKI. It is allocated the static IP 192.168.1.77 by the router. It is also set manually in TCP/IPv4 on the NIC. The gateway is set to 192.168.1.1 (the router). The Primary DNS Server is set to 127.0.0.1. The Secondary DNS Server is blank. When adding the Active Directory Domain Services, and DNS roles - I chose to create a new forest: acme.com (I'm using this as the example, but it is actually set to a valid domain that I own). The NetBIOS domain name was set to ACME.
I've tried joining a physical server (BALDER) to the domain, as well as VM's running on BALDER. I have BALDER's Primary DNS Server in TCP/IPv4 set to 192.168.1.77. It has a static IP assigned by the router of 192.168.1.75. I've also tried setting it manually in TCP/IPv4 with a gateway of 192.168.1.1.
When joining the domain, I'm using the full domain, with the TLD: acme.com.
Occasionally I'm prompted for credentials. I've tried the following users:
acme\administratoracme.com\administratoracme\dbacme.com\db(where db is an Enterprise Admin). Upon entering any credentials, I get:
---------------------------
Computer Name/Domain Changes
---------------------------
The following error occurred attempting to join the domain "acme.com":
The specified domain either does not exist or could not be contacted.
---------------------------
OK
---------------------------
...but most of the time I immediately get this error message, without being prompted for credentials:
Note: This information is intended for a network administrator. If you are not your network's administrator, notify the administrator that you received this information, which has been recorded in the file C:\Windows\debug\dcdiag.txt.
The following error occurred when DNS was queried for the service location (SRV) resource record used to locate an Active Directory Domain Controller (AD DC) for domain "acme.com":
The error was: "DNS name does not exist."
(error code 0x0000232B RCODE_NAME_ERROR)
The query was for the SRV record for _ldap._tcp.dc._msdcs.acme.com
Common causes of this error include the following:
- The DNS SRV records required to locate a AD DC for the domain are not registered in DNS. These records are registered with a DNS server automatically when a AD DC is added to a domain. They are updated by the AD DC at set intervals. This computer is configured to use DNS servers with the following IP addresses:
192.168.1.77
- One or more of the following zones do not include delegation to its child zone:
acme.com
com
. (the root zone)
I've ran dcdiag /fix on LOKI. All tests pass.
I've ran the following:
nslookup
set type=all
_ldap._tcp.dc._msdcs.acme.com
On LOKI (the DC) I get:
Server: UnKnown
Address: ::1
_ldap._tcp.dc._msdcs.acme.com SRV service location:
priority = 0
weight = 100
port = 389
svr hostname = LOKI.acme.com
LOKI.acme.com internet address = 192.168.1.77
LOKI.acme.com AAAA IPv6 address = 2a02:c7d:894d:6d00:8dce:ebee:6510:b61c
LOKI.acme.com AAAA IPv6 address = fdc6:f573:1ff9:0:8dce:ebee:6510:b61c
On BALDER I get:
Server: UnKnown
Address: fdc6:f573:1ff9:0:7250:afff:fe35:beec
*** UnKnown can't find _ldap._tcp.dc._msdcs.acme.com: Non-existent domain
I've tried running this on LOKI, which completes succesfully:
dcdiag /test:registerindns /dnsdomain:acme.com /v
I've also restarted the DNS server, and restarted the NetLogon service.
I've tried running ipconfig /flushdns on both LOKI and BALDER.
I can successfully ping the DC (LOKI) from BALDER, as well as my VM's. I don't know if it matters that it's replying with an IPv6 address rather than an IPv4 addess. IPv6 addresses are set dynamically by DHCP on the router. Either way, it's successfully resolving the FQDN.
C:\Windows\system32>ping loki
Pinging loki.acme.com [2a02:c7d:894d:6d00:8dce:ebee:6510:b61c] with 32 bytes of data:
Reply from 2a02:c7d:894d:6d00:8dce:ebee:6510:b61c: time=1ms
Reply from 2a02:c7d:894d:6d00:8dce:ebee:6510:b61c: time<1ms
Reply from 2a02:c7d:894d:6d00:8dce:ebee:6510:b61c: time<1ms
Reply from 2a02:c7d:894d:6d00:8dce:ebee:6510:b61c: time<1ms
Ping statistics for 2a02:c7d:894d:6d00:8dce:ebee:6510:b61c:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 1ms, Average = 0ms
The machines are connected by a single GigE switch (running this on BALDER):
C:\Windows\system32>tracert loki
Tracing route to loki.acme.com [2a02:c7d:894d:6d00:8dce:ebee:6510:b61c]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms LOKI [2a02:c7d:894d:6d00:8dce:ebee:6510:b61c]
Trace complete.
Per Greg's comment, I have ran this command:
nltest /dsgetdc:acme.com
The output appears to be the same from the DC and a joining server.
Here is the output from LOKI (the DC):
DC: \\LOKI.acme.com
Address: \\2a02:c7d:894d:6d00:8dce:ebee:6510:b61c
Dom Guid: b0408a6c-7960-4908-9fbf-1b4ca506a31e
Dom Name: acme.com
Forest Name: acme.com
Dc Site Name: Default-First-Site-Name
Our Site Name: Default-First-Site-Name
Flags: PDC GC DS LDAP KDC TIMESERV GTIMESERV WRITABLE DNS_DC DNS_DOMAIN DNS_FOREST CLOSE_SITE FULL_SECRET WS DS_8 DS_9 DS_10
The command completed successfully
Here is the output from BALDER (a joining server):
DC: \\LOKI.acme.com
Address: \\2a02:c7d:894d:6d00:8dce:ebee:6510:b61c
Dom Guid: b0408a6c-7960-4908-9fbf-1b4ca506a31e
Dom Name: acme.com
Forest Name: acme.com
Dc Site Name: Default-First-Site-Name
Our Site Name: Default-First-Site-Name
Flags: PDC GC DS LDAP KDC TIMESERV GTIMESERV WRITABLE DNS_DC DNS_DOMAIN DNS_FOREST CLOSE_SITE FULL_SECRET WS DS_8 DS_9 DS_10
The command completed successfully
Just to mix it up a bit, I ran PortQueryUI from a different server - ODIN (a VM on BALDER). I entered LOKI in the Destination IP/FQDN to query field, and left the rest of the options as the defaults (Service to query: Domains and Trusts).
My post is exceeding the char limit, so I've uploaded the results to Pastebin.
I've ran ipconfig /all on a couple of joining servers — a physical server (BALDER) and a VM (ODIN). Here are the results.
BALDER:
Windows IP Configuration
Host Name . . . . . . . . . . . . : BALDER
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : Home
Ethernet adapter Ethernet:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : QLogic BCM5708C Gigabit Ethernet (NDIS VBD Client) #50
Physical Address. . . . . . . . . : 00-22-19-61-D7-D3
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Ethernet adapter vEthernet (INTERNET):
Connection-specific DNS Suffix . : Home
Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter
Physical Address. . . . . . . . . : 00-22-19-61-D7-D1
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2a02:c7d:894d:6d00:15f2:deb5:93d3:460d(Preferred)
IPv6 Address. . . . . . . . . . . : fdc6:f573:1ff9:0:15f2:deb5:93d3:460d(Preferred)
Link-local IPv6 Address . . . . . : fe80::15f2:deb5:93d3:460d%17(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.75(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : 12 June 2017 23:05:03
Lease Expires . . . . . . . . . . : 13 June 2017 23:05:02
Default Gateway . . . . . . . . . : fe80::7250:afff:fe35:beec%17
192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DHCPv6 IAID . . . . . . . . . . . : 335553049
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-20-AD-3F-C1-00-22-19-61-D7-D3
DNS Servers . . . . . . . . . . . : fdc6:f573:1ff9:0:7250:afff:fe35:beec
192.168.1.77
NetBIOS over Tcpip. . . . . . . . : Enabled
Tunnel adapter Teredo Tunneling Pseudo-Interface:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e76:146b:3e88:3f57:feb4(Preferred)
Link-local IPv6 Address . . . . . : fe80::146b:3e88:3f57:feb4%15(Preferred)
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 201326592
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-20-AD-3F-C1-00-22-19-61-D7-D3
NetBIOS over Tcpip. . . . . . . . : Disabled
Tunnel adapter Reusable ISATAP Interface {8620C56F-EB4F-484B-A9DA-5C135F83D4F6}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : Home
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter isatap.{91D42D6A-0FF8-4541-AF50-FE8AB4C11F3D}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #3
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
ODIN:
Windows IP Configuration
Host Name . . . . . . . . . . . . : ODIN
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Ethernet:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Hyper-V Network Adapter
Physical Address. . . . . . . . . : 00-15-5D-01-4C-05
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2a02:c7d:894d:6d00:6912:438f:9808:ad47(Preferred)
IPv6 Address. . . . . . . . . . . : fdc6:f573:1ff9:0:6912:438f:9808:ad47(Preferred)
Link-local IPv6 Address . . . . . : fe80::6912:438f:9808:ad47%10(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.85(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : fe80::7250:afff:fe35:beec%10
192.168.1.1
DHCPv6 IAID . . . . . . . . . . . : 50337117
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-20-BF-D2-65-00-15-5D-01-4C-05
DNS Servers . . . . . . . . . . . : fdc6:f573:1ff9:0:7250:afff:fe35:beec
192.168.1.77
NetBIOS over Tcpip. . . . . . . . : Enabled
Tunnel adapter Teredo Tunneling Pseudo-Interface:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e76:c7e:2db:fd81:f39(Preferred)
Link-local IPv6 Address . . . . . : fe80::c7e:2db:fd81:f39%15(Preferred)
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 134217728
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-20-BF-D2-65-00-15-5D-01-4C-05
NetBIOS over Tcpip. . . . . . . . : Disabled
Tunnel adapter Reusable ISATAP Interface {16673442-3677-41AD-94B2-86C728C55B62}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
I've also tried setting the DNS suffix to acme.com, but this didn't help.
What is preventing me from joining any machines to the domain?
I've just got a couple of 2010 Dell servers. One of them has 4x 1TB disks. I configured them in the RAID controller to use all of them in RAID5 to give me 3TB of storage + 1TB for parity. There are no other HDDs in the server. I wanted to just have one 3TB VD, and have Windows Server 2016 installed on it, too.
When I go to install Server 2016, it correctly shows me a single disk, 2.7TB in size; but when I click New, it gives me a 2048GB partition, plus 746GB of unallocated space. Trying to click New on the unallocated space results in a error code, that returns 0 results on Google.
From searching the internet, I've found that it's because MBR does not support disks >2TB — the disk instead needs to use GPT... but by the looks of it, you can only use GPT on a non-boot disk. So if I'm booting Windows Server from it, I can't use GPT.
Is that correct? So am I stuck with having 1x 1TB HDD for the OS, using MBR; and 3x 1TB HDD's to use in a 2TB+1TB RAID5 configuration? Leaving me with only 2TB usable on my main VD? :(