I started by following this video https://www.youtube.com/watch?v=NyOSoLn5T5U. Once i customised the compose file I managed to setup my first playbook. I decided to store playbooks on my nas for safety and the first one I made was a apt update. I then started tinkering with more complicated ones for proxmox and my dns settings. This is still what I am doing as proxmox is working through proxmoxer and if not exactly simple but I am happy with the progress I am making.
It started when I was trying to install change detection. I was getting a error about not having space on the drive so I decided to delete some unused docker volumes. This lead to a new far more concerning error “mkdir /data/compose: no such file or directory”. After looking online I realised this could be bad so I decided to download a copy of passbolt and then reboot. The first thing I noticed was proxmox stopped working but I realised this was just my dns. The when I did a docker ps it showed that everything was starting fine. However when I went to Portainer it told me to setup a new install. ...
I recently decided to fully explore obsidian. I had installed it when I setup my arch linux install however I had never actually done anything more advanced that make a list of tasks. I began thinking how I could make use of obsidian I my mind went quite quickly to documentation of my homelab. I had been doing this with wordpress however I had been considering replacing that, so i began to look. One quick google search later and i found mkdocs. While this is currently not very astetic I hope to be able to fix that. The other thing I had to sort was syncing the files between the website, PC and phone. For the website I already knew I wanted to use gitea with a custom push action. However for the PC and phone I found that the Git plugin would work on my PC but not my phone. You may be able to get it working using ISH and the shortcut app however I could not so i resorted to a second plugin called Remotely save. This is still not ideal as it goes through both onedrive and obsidian to reach my server however that may be fixable with a s3 bucket on truenas and some more scripting.
I began by trying to move my mailcow install from running on docker volumes to storing data on my nas. I started copying the files however after around the 5th volume I remembered the continers were still online. After I continued even finding a copy of the docker compose. However when I ran the compose I got serveral errors about mysql. I realised I had corrupted the mysql database. I tried several edits to the mysql files and failed. After that I went to launch the old copy and realised that was corrupted as well. ...
The one feature of Icloudpd that I dislike is the requirement to constantly redo 2fa. I also would have no way of knowing when this is untill I set up one of the notification options. I decided since there was no smtp which would be my normal choice I would try out the discord web hook function which I hadn’t used before. The setup went fine untill I went to test it I restarted the container and got a notification that it started however, almost strait after that I got a message that it couldn’t access the folder that stored my photos. I re aplied the acl which fixed it but I need to find a away to re do the acl on a schedual.
I have been using the default syncthing windows client for a while. However, the task sceudular setup had never worked properly and there for I had been forced to run it manually every now and then. Luckily I came across a reddit post that mentionted SyncTrayzor at first I thought it was a different software but then I found out it worked with my existing syncthing server. I downloaded the installer and ran it. It worked even better than expected as it managed to use my existing config with the only change needed was to add an allow newer config flag in the settings.
I wanted to setup a more simple shareable alternative to VMs. Kasm was a great option which I was very excited to try. I began by setting up the normal docker compose with my normal bind mounts. However it kept getting stuck in a loop after accepting the terms. So I had to switch to a full install on a vm. After that I followed the stock install guide and it all went fine. I setup the workspaces I wanted and they installed fine. However the other issue I ran into was when I tried to add ssh to a vm. No matter what I tried it just wouldn’t work so in the end I decided I could just use the Ubuntu workspace and manually ssh in.
I wanted to try and find a better way to backup my photos from my iPhone to my NAS. I had been using Nextcloud with the app on my phone to do this however is was slow and nextcloud pritiy much always ran so slow a page could take around 60 seconds to load. I had seen iCloudpd before as a application on TrueNAS and so wanted to try it out. I set up a docker compose and signed in. However I then started getting a message to create the .mounted file which I had already done. This prity much instantly told me that there was somthing wrong with my mount. However when I looked it all seemed fine so I was forced to ssh in and relook at the new mount I had made to my NAS. After some failed ideas I noticed that the mount only had empty folders in it. This finaly reminded me that my Photos folder was acutualy a dataset so I switched the nsf share to that and it started to run a backup. ...
I began to notice issues when my passwords in the ios passbolt app when it was’t showing my passwords. I quickly found a range of posts about historical issues with ios 17 batas but as far as I could see they had been solved in app version 15 and I was on 18. The next step I took was to run the health check this found that I had two issues: my install didn’t force https which is fine because if uses cloudflare; and my install was very out of date. Updating is one of the big draw backs of docker in my opinion and while there was a page about updating on the passbolt website I decided to just figure it out through portainer. ...
The first thing I noticed was wrong was that my Iphone was giving me a pop up telling me it could verify the identity of mail.keldo.uk. My first though was that the ssl cert had expired but as far as I knew Mailcow should automaticly refresh the cert. Luckily it was easy to debug as Mailcow has a nice selection of logs and I just open the acme logs and Imedialty saw the issue “mail.keldo.uk - Found AAAA record for mail.keldo.uk: 2a00:23c7:82c2:6401:be24:11ff:fe6d:10fa - skipping A record check” was apearing every hour. I setup ipv6 records when I set up mailcow however since I have a dynamic IP and haven’t set up a ddns for ipv6 it was seeing ipv6 skiping ipv4 and then seeing the ipv6 didn’t match. The simple solution was I just removed the ipv6 record and then the next hour it was fixed.