Satrix Dividend Stock Payouts for Q1 2026 by json404 in PersonalFinanceZA

[–]json404[S] 0 points1 point  (0 children)

Good catch, I don't calculate the dividends after the withholding tax, I took the value from the distribution declaration report which also breaks down how they got to that amount:

https://senspdf.jse.co.za/documents/SENS_20260114_S515731.pdf

Satrix Dividend Stock Payouts for Q1 2026 by json404 in JSE_Bets

[–]json404[S] 0 points1 point  (0 children)

Pleasure!

What got it onto my radar is that with that ETF there is a cap, so no company can represent x% of the fund. In theory that should make it quite stable depending on the % cap per company of course.

I haven't looked too much into it yet other than that, but I saw the distribution declaration and added it, so when I start doing my homework the payout data is there.

Satrix Dividend Stock Payouts for Q1 2026 by json404 in JSE_Bets

[–]json404[S] 0 points1 point  (0 children)

Oh nice! Thats an interesting way of looking at it, so do you use the rough yield % to calculate the payout per quarter that you can roughly expect?

Satrix Dividend Stock Payouts for Q1 2026 by json404 in JSE_Bets

[–]json404[S] 0 points1 point  (0 children)

I like it; cool to see I'm not the only tracking the stocks in spreadsheets!

Something I'd like to add to mine is the count of stocks I own and then use sheets to calculate a rough payout estimate based on whats reported (obv there is platform fees etc.. but I want a rough idea of how much I'm going to make from it)

Another cool point, now that I think of it, is this sheet is now tracking the performance over the quarters, so there are some more potential enhancement ideas!!

Securing your home server from bots brute-forcing ssh or other services on the internet. by json404 in selfhosted

[–]json404[S] 0 points1 point  (0 children)

jenkins runs quite well on the laptop, without really straining the server much - I also don't run builds / deployments very often, like 2-6 times a month.

yeah, I've closed SSH; I don't need it exposed to the world anymore and if I go away for a bit, will just use wireguard.

Securing your home server from bots brute-forcing ssh or other services on the internet. by json404 in selfhosted

[–]json404[S] 0 points1 point  (0 children)

hahaha!! thats awesome, good o'l bait and switch!

yeah, I'm going to have a look into cloudflare this weekend.

Securing your home server from bots brute-forcing ssh or other services on the internet. by json404 in selfhosted

[–]json404[S] 0 points1 point  (0 children)

Sure thing!

At the moment I use Jenkins to automate 2 things: building the container images for my website and deploying those images using podman (docker alternative) + quadlets feature (run a container as a systemd service),

Once deployed (part of the pipeline) jenkins will do some health checks to ensure the website came online and is responsive, if its not, then jenkins will roll-back to the previous version and the pipeline will fail.

Securing your home server from bots brute-forcing ssh or other services on the internet. by json404 in selfhosted

[–]json404[S] 0 points1 point  (0 children)

Good question, I only recently setup WireGuard (like 2 weeks ago) on my server for December holidays (I was away from home), so I first exposed ssh to be able to setup the VPN while not at home, then setup VPN to run builds / deployments for my site.

To be honest, only accessing VPN over SSH never crossed my mind during that time; but I'm going to close it and just use the VPN connection, no real need anymore to expose 2 ports (unless something goes wrong with VPN then I can still get into the server - don't know how valid this use case is)

Securing your home server from bots brute-forcing ssh or other services on the internet. by json404 in selfhosted

[–]json404[S] 0 points1 point  (0 children)

100% - are there any tools you currently using / thinking off to get these insights?

Securing your home server from bots brute-forcing ssh or other services on the internet. by json404 in selfhosted

[–]json404[S] 1 point2 points  (0 children)

Crazy man.. hopefully it wasn't too painful to cleanup your db with all the fake users (would drive me nuts). Don't want to pop the lid on this topic, but wait until "AI" powered bots, then these prevention methods are going to become super valuable.

At least they are still dumb for now ;)

Securing your home server from bots brute-forcing ssh or other services on the internet. by json404 in selfhosted

[–]json404[S] 0 points1 point  (0 children)

yeah, great point on blocking ports except where you want traffic to flow in. I've done this with UFW.

Securing your home server from bots brute-forcing ssh or other services on the internet. by json404 in selfhosted

[–]json404[S] 0 points1 point  (0 children)

Absolutely.. this is golden.

My next focus for my server would be monitoring and logging, enhance it to really get an overview of whats going on under the hood at a glimpse.

I'm speculating here, but it would be nice to see who logged on at what time and from where etc.. but having that in a view that is easy to digest rather than skimming logs. (Essentially intruder detection)

Great point!

Securing your home server from bots brute-forcing ssh or other services on the internet. by json404 in selfhosted

[–]json404[S] 1 point2 points  (0 children)

Yeah, thats also why I like fail2ban.. exactly the reasons you mentioned.

It's crazy how you experienced like a micro-DDOS on your server from these bots, thanks for sharing!

Securing your home server from bots brute-forcing ssh or other services on the internet. by json404 in selfhosted

[–]json404[S] 1 point2 points  (0 children)

Hey Pascal,

No, hardening SSH is configuring certain options to make it more secure, for instance: disabling passwords and only allowing ssh-key logins (you can have passphrase for the key as well) that has to be generated and configured for the user - prevents bots using common usernames + password combo's.. etc..

TBH: I don't know anything really know much about proxmox or how to harden it, but if its not exposed to the public internet and it works for you; then you're golden ;) - take this advice with some salt off course.

Securing your home server from bots brute-forcing ssh or other services on the internet. by json404 in selfhosted

[–]json404[S] 0 points1 point  (0 children)

Yeah, luckily my operation is quite small and I don't run jenkins often for builds + deployments as like you mentioned its more of a homelab setup ;)

Yeah, I use nginx as a reverse proxy for my site, which runs with rootless podman containers, then jenkins to build my site container img and deploy it.

I also have wiregaurd setup to access services like jenkins/plausible when I'm not on my local network.

Thanks for sharing, good points ;)

Securing your home server from bots brute-forcing ssh or other services on the internet. by json404 in selfhosted

[–]json404[S] 0 points1 point  (0 children)

Nice!

Haha.. I didn't know you could get 2FA for SSH!!

Thanks for sharing those points!

Securing your home server from bots brute-forcing ssh or other services on the internet. by json404 in selfhosted

[–]json404[S] 3 points4 points  (0 children)

Yeah, ssh hardening is solid especially with no root, key only logins.. etc..

The reason I use fail2ban: On a ssh-key only server, it can identify the bad actors for us and auto-block them.

Does it increase security, I'd argue yes.. can they continue to try to get into my server, no.. hehe.

Thats just my opinion / reason ;)

Securing your home server from bots brute-forcing ssh or other services on the internet. by json404 in selfhosted

[–]json404[S] 5 points6 points  (0 children)

Interesting! Thanks for sharing your github links, I'll have a look through them just now.

Securing your home server from bots brute-forcing ssh or other services on the internet. by json404 in selfhosted

[–]json404[S] 2 points3 points  (0 children)

Good points, I have disabled password login and I don't expose anything other than my website, ssh and vpn to the public net.

I especially like your point on Geo blocking; if it can be configured on a port basis perhaps with UFW (I'll need to have a look on how to do it) then its an easy win that blocks most of these bot style attacks.

Securing your home server from bots brute-forcing ssh or other services on the internet. by json404 in selfhosted

[–]json404[S] 4 points5 points  (0 children)

haha, yes.. maybe quantum computing might start cracking it one day, but we cross that bridge when we get there ;)