Automatic Renewals with BliKVM

My domain is: kvm.cshaheen.tech

I ran this command:

sudo kvmd-certbot certonly_webroot --agree-tos -n --email christian@cshaheen.tech -d kvm.c.tech --no-eff-email --pre-hook rw --post-hook ro
/usr/local/bin/rw && certbot renew && /usr/local/bin/ro

It produced this output:

root@kvm(ro):/home/cshaheen# /usr/local/bin/rw && certbot renew && /usr/local/bin/ro
Saving debug log to /var/log/letsencrypt/letsencrypt.log
The following error was encountered:
[Errno 30] Read-only file system: '/etc/letsencrypt/.certbot.lock'
Either run as root, or set --config-dir, --work-dir, and --logs-dir to writeable paths.
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details.

My web server is (include version): nginx/1.18.0 (Ubuntu)

The operating system my web server runs on is (include version): Ubuntu Jammy LTS

My hosting provider, if applicable, is: N/A

I can login to a root shell on my machine (yes or no, or I don't know): Yes

I'm using a control panel to manage my site (no, or provide the name and version of the control panel): No

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot): certbot 1.21.0

Hello! I have a BliKVM v4 AllWinner with installed PiKVM. What I'm having trouble with is BliKVM uses a read-only file system by default. It can be switched to read/write with the command rw and back with ro. I switches to rw to issue my certificate with certbot and I included the cert just fine. When I switch back to ro and try a renew, I get the output above. I tried chaining the commands together with && but that gave me the same output. Is there another way to automate this?

I can't seem to find ro or rw in the vendor's armbian image, do you know where these tools came from?

I started with the image for the device: GitHub - blikvm/blikvm: Open and cost-effective "KVM-over-IP". BliKVM comes in 4 different models, v1 CM4, v2 PCIe, v3 HAT and v4 Allwinner, based on Raspberry Pi and Allwinner SoC.

Then they suggest this guide for converting to PiKVM: GitHub - RainCat1998/Bli-PiKVM: Install Pi-KVM on BliKVM v4 Allwinner.

ro and rw should come from the first link.