IT can be happen sometimes, that the Issuer or Cluster Issuer can not be registred to the DNS01 / Cloudflare challenge..
Did you already had this strange error message?
Get "https://acme-v02.api.letsencrypt.org/directory": tls: failed to verify certificate: x509: certificate is valid for ingress.local, not acme-v02.api.letsencrypt.org
Custom Python Crontab Script with DNS01 Challenge / Cloudflare DNS for Letsencrypt
This was an urgent issue fix - because these TLDs require an SSL Cert already in place
HTTP-01 Challenge is also working over HestiaCP, NOW!
Hint: crontab not required anymore
If u are the lazy admin and user of an "Hosting Control Panel" like HestiaCP you maybe already had the following problem:
ITs just totally easy to install amdgpu-dkms kernel driver with ROCm/AMDGPU on OpenSUSE Tumbleweed or better MicroOS/AEON, if you know what to do...
sudo transactional-update --continue pkg install kernel-longterm kernel-longterm-devel
If you get any policykit issue, by running some software updates over Discover at KDE, even when system patches will be installed, the default installation of OpenSUSE Micro is missing the wheel group, which gots checked by policykit.
I dont recommend to modify / add any rules to policykit, so if you dont want be asked again and again for the user password, simply add the wheel group and your users to that group!
groupadd wheel
If your FIDO Key gots locked, because the fingerprint was not OK, then its quite easy to unlock the Yubikey FIDO BIO USB Key (if you know it!)
For me, only reset was possible over GUI with yubikey-manager, so the unlock requires shell command!
Install the yubikey-manager package:
Its possible, if you know - to use OpenGL Support over Spice at Virt-Manager, e.g. for a WindowsVM Instance.
Just install the following dependencies to the Host:
transactional-update pkg install qemu-ui-spice-core libvirglrenderer1 qemu-ui-opengl
It is really easy to configure a user-space systemd autostart for Containers on OpenSuSE MicroOS with Podman-Compose.
When your Podman Container YourContainerService is running, then generate the systemd user unit:
podman generate systemd --new YourContainerService > ~/.config/systemd/user/YourContainer.service
Info: This solution is not recommended because of selinux Security - use it at your own Risk!
If you run into the Issue, that Games can not be started finally - then please check if selinux is working correctly:
| For Example Age Of Empires 4, look: HowTo|
I recommend to install steams as RPM Package, because then all the dependencies e.g. for Proton Experimental will be installed.
Fell free to use with Flatpak, if thats working fine for you. See Packages list!
These steps I used to run Steam with AMD Radeon Vega System: ASUS Mini PC PN52 BBR959XD - Barebone - Mini-PC - 1 x Ryzen 9 5900HX / 3.3 GHz
If you run into the issue, that DNS Resolving is not possible with K3S, Rancher, OpenSuSE MicroOS and SELinux enabled:
Please make sure, that the following Settings at K3S SystemD Unit are enabled:
ExecStart=/usr/local/bin/k3s \