Someone: “… the new php vulnerability”
Me: “wait what, another one?”
S: “Yes”
I had exposed services for years, never a problem. I don’t have time to be on top of all of this. Im going random high port wireguard access only.
What made me change:
I can know that there is a php bug. But I still need for nextcloud to patch/update.
Because im trying to be cool.
But serious. If ever a wireguard vulnerability is found, which I is not very probable and a terrifying prospect, the default port will be the main target.
Someone: “… the new php vulnerability”
Me: “wait what, another one?”
S: “Yes”
I had exposed services for years, never a problem. I don’t have time to be on top of all of this. Im going random high port wireguard access only.

Generated code was trully bad. These days? Not so much anymore…
Better tools, more acceptance.

Llm that reads my whatsapp chats and extract events then make calendar events for me
I sit like this and have no pain… I also climb 3 times a week, which, accoiding to my informal survey, helps inmensly with back pain.

Should not be allowed.

It never goes down :-) I just want to make it better.
Alright, im kind lying, it use to go down all the time cause my NICs would hang, but I did fix it. This problem did gave me the itch to make it even more avaliable.

The more I go into this rabbit hole, the more I understand this, and I understand now that I went into the hole with practically 0 knowledge of this topic. It was so frustrating to get my “HA” proxy on LAN with replicated containers, DNS and shared storage, hours sank into getting permission to work, just to realise “oh god, this only works on LAN” when my certs failed to renew.
I do not think I need this, truth is that the lab is in a state where I have most things I want[need] working very well and this is a fun nice to have to learn some new things.
Thanks for the info! I will look into it!

Super, thanks. I will look into this. I actually have some shared storage on my NAS for traefik configs which is already working on replicated instances.

Thanks for the info, I kinda wanted someone to confirm that could before I sank some hours into it :)

Def went into the rabbit hole without any idea how many of these single points I’d need to address, and the more I mitigate the more I find. Like you said, this is very much overkill, I am just doing it to learn and have some good old homelab fun before we are all forced to rent “cloud” PCs
Thanks for the suggestions, I’ll look into those!
So, just for the sake of it I’ve been trying to get my lab to be HA -or as HA as a small homelab can be-
My current set up is a follows:
3 proxmox servers with some Debian VMs, the VMs run docker swarm
A NAS, with Truenas
ISProuter -> OpenWRTRouter -> VM [Port fowards 80/443]
This works like a charm when I am in my LAN, but when I access from outside, if the VM that has 80/443 port forwarded to is down (which it never is) I’d loose connectivity.
I have now idea how to solve this little problem in a efficient way, maybe a reverse proxy running on my OpenWRT? (Which’d only move the point of failure to my router, but if my router goes down is gameover already anyways) has anyone attempted this?
Any opinions/ideas?
Update:
Solved! I moved my traefik data to a NFS share in my NAS, replicated the container across all manager nodes and then installed keepalived and now float a VIP between them.
Works like a charm and it was super easy to set up, literally 3 ansible tasks and 1 jinja template and you are done.
Thanks to all of ya!

/srv/[stack name]/volumes/[binds]
I just like so much /srv is the best folder

Had today some time to take the linux desktop client for a test drive. It works without problem.
It is a appimage wich is for my taste not idea but it works.

Im using the android client no problem. Not sure about the the desktop ones, if you want I cant do some basic testing and report back, just let me know which clients

Checkout opencloud, owncloud clients are compatible with it
I was a heavy stoner for years… I used 51420.
Funny is that once I forgot I configured that port and took me some hours of debugging to find out. :(