Common Server issues – FAQs and answers from those in the know
Zeppelin Helm installation behind a client proxy
22 November 2025 @ 12:10 pm
I have installed Zeppelin with Helm, using the duyet/zeppelin chart on a client's Microk8s cluster and this client has a proxy configured.
When I try to run a notebook that installs packages,
%python
# Install packages in the current Python environment
!pip install --upgrade pip
!pip install pyais pandas minio pyarrow
it correctly creates the interpreter pod, but fails due to the proxy:
WARNING: The directory '/opt/zeppelin/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
Requirement already satisfied: pip in /opt/conda/envs/python_3_with_R/lib/python3.9/site-packages (24.2)
WARNING: Re
Adding disk in failover cluster manager fails due to no disks available [closed]
22 November 2025 @ 6:25 am
No disks suitable for cluster disks were found.
For diagnostic information about disks available to the cluster, use the Validate a Configuration Wizard to run Storage total tests.
What should I do?
Debian Trixie Wifi-Bridge: Clients are losing connection every midnight
22 November 2025 @ 12:16 am
sorry if my English is a bit rough, I'm using a translation service because I have a cold and can't concentrate very well on translating with my brain cells ;-)
Anyway: I'm using a LAN-to-WLAN bridge to connect some older smart home components, as they unfortunately don't work with my main Wi-Fi network.
I set it up following the instructions at https://www.elektronik-kompendium.de/sites/raspberry-pi/2002161.htm. The only difference is that I'm not using a Raspberry Pi, but I thought the instructions were generally applicable to Debian, and I assigned the bridge a static IP address.
This worked flawlessly and reliably under Bookworm, but since I upgraded Debian to Trixie, all the Wi-Fi clients lose their connection every night at exactly midnight. Unfortunately, restarting networkd, br0, or wlan0 doesn't help; only a complete server restart restores the co
Docker acme-companion can't connect to get certificate
21 November 2025 @ 10:55 pm
I have reverse proxy with acme-companion on my docker stack - all behind ufw. I was using different solution before - but similar, and it worked. I had to change it since old solution were not updated for a long time.
Now I have this:
reverse proxy docker-compose.yml
services:
nginx-proxy:
image: nginxproxy/nginx-proxy
container_name: nginx-proxy
restart: always
ports:
- "80:80"
- "443:443"
volumes:
- /var/run/docker.sock:/tmp/docker.sock:ro
#- nginx-conf:/etc/nginx/conf.d
#- nginx-vhost:/etc/nginx/vhost.d
- html:/usr/share/nginx/html
- certs:/etc/nginx/certs:ro
- ./uploadsize.conf:/etc/nginx/conf.d/uploadsize.conf:ro
acme-companion:
image: nginxproxy/acme-companion
container_name: nginx-proxy-acme
restart: always
environment:
- [email protected]
volumes_from:
- nginx-proxy
v
Intermittent VPN/Routing Issues Led to Machine Trust Failure — DC Health Appears Normal. Root Cause?
21 November 2025 @ 9:09 pm
I have a Windows 10 domain-joined workstation that recently lost its machine account secure channel. Symptoms:
• Test-ComputerSecureChannel consistently returns False
• The workstation stopped accepting previously cached domain credentials
• RDP to domain servers intermittently fails
• VPN connectivity stays up, but routing/DNS performance is extremely inconsistent
• Access to domain resources is unreliable unless the VPN happens to be in a “good” state
These issues affect only this workstation. Other domain-joined systems authenticate normally and do not experience VPN latency or routing issues. We have two domain controllers; both are fully functional and show no replication or DNS issues. All domain controller health checks pass:
• repadmin /replsummary → 0 failures, both DCs synchronized
• repadmin /showrepl → all inbound neighbors successful
• dcdiag /test:dns → domain DNS tests pass
• SYSVOL/DFSR healthy
• No replication backlog
• No Kerb
Multi SSID Hotspot config through NetworkManager USB WiFi dongle [migrated]
21 November 2025 @ 3:54 pm
short recap: I'm moving my NFS booted RPi-4B from Raspbian-bookworm to Raspbian-trixie, so I create a new logical volume on the NAS and started new fresh installation.
This time I'm trying to avoid all the scripts customizations (hostapd, bind9, isc-dhcp-server, iptables, openvpn-client) and I'm trying to use NetworkManager, shared IPs config and nftables, but I need some help.
I have an external USB Wifi dongle with multi SSID capabilities and before I easily configured a second virtual device and multiSSID adding below settings in the hostapd.conf:
...
bss=wlan2
ssid=MyWifi-Guest-5G
bssid=e6:aa:bb:cc:dd:ee
...
but I don't know how to do in NetworkManager ?
below my current NetworkManager config:
! nmcli connection show
NAME UUID TYPE DEVICE
Hotspot-MyWifiMain 0f6bc26c-a44dda4ea6b4 wifi wlan1
Hotspot-OnbBoard 9f0b42e9-a2e503c5f709 wifi wlan0
eth0 193e
AD DNS update works initially for Samba client, then fails
21 November 2025 @ 7:00 am
We have a large AD domain with three Windows Server 2022 DCs. DNS registration and renewal works with Windows domain members. I do not have control over the DCs (although I can access them for troubleshooting purposes. I just don't know where to look in the event log).
With a Samba member (version 4.15.13, running Ubuntu 22.04) the automatic (daily) DNS record renewal fails, and the DNS record is removed by the cleanup process after 30 days. I can manually re-register, but haven't been able to do this in a script.
Question 1:
I haven't figured out why the DNS registration isn't automatically renewed "out of the box"
Question 2:
I suspect this may actually have the same cause as Q1:
As a workaround, I tried creating a cron script to automatically renew the DNS registration. It works for a few days when using the machine account (the net ads ... -P option) before failing. It works reliably when I use my own credentials (-U <u
Domain Name Service (DNS) resolving Content Delivery Network (CDN) name
21 November 2025 @ 12:23 am
We have contracted a company to provide the new web server, and they use a company called Vercel to provide infrastructure for the site. They demand that we make the DNS for the site a CNAME which points to a Vercel domain name which works in the same way as the CDN, and that this will be an instant world wide change. I don't understand how this works.
I used to run a DNS server (named on Solaris) when I worked for the University, our DNS server was allowed to be authoritative for our faculty, and we could apply for more IPs from a pool given to our faculty by the central IT services. I assumed they were granted their pool from another regulated body which assigns IPs for the country, and they in turn get it from an international body (in America?).
When I made DNS changes, say for our site, I would update the forward and backward resolution files to link the domain name with ONE IP address, and then update the serial number on the configuration which told the DNS serv
Ansible’s docker-compose plugin and bullseye nodes
20 November 2025 @ 8:00 pm
With the upgrade of the Ansible control node to Debian trixie, the docker_compose module is gone.
However, the community.docker.docker_compose_v2 module fails to work with a Debian bullseye target node.
There is no available upgrade for Docker in Debian bullseye to make this work, and a switch to Docker-upstream-provided packages is undesirable.
As someone who merely has to occasionally run the playbooks and needs to make them continue to work until the box can be upgraded to bookworm and then trixie, what are my options?
Can I just download/clone the community.docker collection at release 3.9.0 (the last one before the removal) and put it as old.docker (i.e. rename the directory), or are the collection names also hardcoded in the collections themselves and relevant for execution? If so, can I just s/community\.docker/old.docker/g over all files?
RapidSSL wildcard - Issuer of this certificate could not be found
20 November 2025 @ 7:27 pm
I imported it into the Exchange server. But there is a warning for the certificate as follows.
Issuer of this certificate could not be found
Issued by : RapidSSL TLS RSA CA G1
Issuer:
CN = RapidSSL TLS RSA CA G1
OU = www.digicert.com
O = DigiCert Inc
C = US
My question: How do I find the Root CA and intermediate certificates here?
ROOT CA : DigiCert Global Root G2