I'm glad that @GMMKE seems to be working again. My plan for a while was to move it off of #pipedream and onto #cloudflare workers. That's something that would need to wait for a few weeks, though.
So, #GitLab has decided to become completely unusable, by showing this #Cloudflare "prove that you're human" screen and then redirecting back to it in an infinite loop.
It is stunning with how #enshittification does nothing to convince me to change my habits (it's probably due to the pi.hole), and I just decide not to use that site ever again.
Obwohl ich bei #STRATO mehrere Domains in unterschiedlichen Paketen liegen habe, bleibt die maximale Anzahl meiner Sub-Domains auf insgesamt 10 begrenzt. Das ist zwar total Banane, aber der Support will mir höchstens teurere Pakete verkaufen.
Früher habe ich meine Domains mal über die Nameserver von #Cloudflare verwaltet – da ist die Anzahl der Subdomains natürlich unbegrenzt. Da ich Cloudflare aber nicht mehr nutzen wollte, nutze ich wieder die Nameserver von STRATO.
UPDATE: The service is accessible by its domain (#Ingress) as soon as I set the DNS server of my client machine to my PiHole. For other systems not using my local DNS (so outside my network), the domain remains unreachable. My suspicion is an issue with the Port Forwards, but idk what's wrong w em as it is.
Note: this may not be in the exact order. If the order to any of this is important, feel free to point that out.
I've added to #Cloudflare, to my zone (domain), the hostname foo pointing to my network's public IP.
I've deployed everything you'd need including #MetalLB (which determines the dedicated Ingress private IP), #nginx-ingress (type set to LoadBalancer instead of NodePort), and #cert-manager (with both HTTP/DNS clusterissuers). If you want to take a peek at how I've deployed/configured them, more details are on here: https://github.com/irfanhakim-as/orked.
I've added foo.domain to the closest thing resembling to a DNS server that I have, #PiHole, pointing to the dedicated Ingress private IP.
I've set my router's only DNS server to the PiHole's IP.
I've set all my Kubernetes nodes' (Masters and Workers) DNS1 to the Router's IP (DNS2 set to Cloudflare's, 1.1.1.1).
I've created a port forwarding rule for HTTP on my router with 1) WAN Start/End ports set to 80, 2) Virtual Host port set to its nodePort (acquired from kubectl get svc -n ingress-nginx ingress-nginx-controller -o=jsonpath='{.spec.ports[0].nodePort}' i.e. 3XXXX), 3) Protocol set to TCP, and 4) LAN Host address set to the dedicated Ingress private IP.
I've created a port forwarding rule for HTTPS on my router with 1) WAN Start/End ports set to 443, 2) Virtual Host port set to its nodePort (acquired from kubectl get svc -n ingress-nginx ingress-nginx-controller -o=jsonpath='{.spec.ports[1].nodePort}' i.e. 3XXXX), 3) Protocol set to TCP, and 4) LAN Host address set to the dedicated Ingress private IP.
I've deployed a container service, and an Ingress for it, using #LetsEncrypt's DNS validation clusterissuer.
Current result:
Cert-manager creates a certificate automatically and is in a Ready: True state as expected.
The subdomain (foo.domain) however remains unreachable, no 404 errors, no nothing. Just "The connection has timed out" error.
Describing the container service's ingress (foo.domain), shows that it's stuck at "Scheduled for sync".
#Kubernetes and #Networking experts - please tell me what I've done in any of this that were either wrong or unnecessary, or what I'm currently missing here for me to reach my goal of being able to get my container accessible via foo.domain through that Ingress. I suspect that I might be doing something wrong with this whole DNS mess I literally cannot fathom. I feel like I'm insanely close to getting this thing to work, but I fear I'm also insanely close of blowing up my brain.
cc: @telnetlocalhost (thanks for bearing w me and getting me this far)
The issue is: #Cloudflare is gratis and secure for yourself, but privacy-invading for your users. #DynDNS is fine for your users, but insecure and not privacy-friendly for yourself. Hosting providers are privacy-invading for everyone, and they also charge money while often not liking what you're doing.
The Blender software is a free and open-source 3D computer graphics application. However, their servers have been under a DDoS attack since last weekend, which has affected their online availability. This is why I use Cloudflare to stay online. Some people engage in malicious activities like DDoS attacks against non-profit organizations for no apparent reason. I hope they come back online soon.
#wordpress devs, how do and more importantly your readers feel about the wordpress toolbar?
I've had it hidden on https://sirtaptap.com for years to keep it clean, but the fediverse Friends plugin needs it (or some way to log in and add), and I've been thinking about adding more social features to the site like bbpress or buddypress, which would require signups.
It really doesn't waste a lot of space, so I guess I'm just worried about the WP version of the "Made in unity splashscreen" effect
In fact if you're spooked, here's a crazy easy way to get started with an impressively durable baby server:
Get a $5 #Linode#VPS. Use a stackscript to install Wordpress + apache (or 1 click install most popular web software). Wordpress is #FOSS, 0 coding required, yet fully customizable if you want
#Cloudflare 's free tier adds security,cache, DDOS protection, and their domain name prices can't be beat, they're wholesale.
Now for ~$70 a year and 2 new logins, you have a fully functional site
#CloudFlare had an #incident late last week affecting their #services. This has been widely commented upon, because #reliability is their raison d'etre (sorry if my French spelling is bad...).
To me, this should count as a resounding success. Even with a #cascading#failure of systems, backups, and #recovery procedures, customers' sites still didn't go down - they lost access to analytics and the ability to make changes, but no actual outage.
#Cloudflare is really impressing me with how transparent they're being with their recent outage. Not only did they write a great post-mortem, but they're letting customers hear directly from leadership on what happened.
It's one reason I really like the #GCP take on a status page. People complain about how many "outages" there are, but it's great that I have a high degree of confidence that if a problem is present in the stack I'm going to see it there vs #aws where their status page is legendarily useless and false. #devops#infrastructure
@Marielle_W@politicalscience@tanyalokot#Freedomhouse totally belongs in the #hypocrisy dog house. They claim to “Protect a Free and #OpenInternet” and yet their own website is on a repressive exclusive #Cloudflare site. WTF. They actually claim¹ CF can talk about “Internet blocking and the consequences for human rights.” I had a medical emergency & could not access health info because of Cloudflare.