Irony: A robot that clicks for me on the "I'm not a robot" buttons.

(Firefox Addon by prowebmasters)

Finally finished setting up my private Git Repo.

First tried to install Gitlab, tried 2 hours to fix it. Holy shit the configs were a shit piece. Ended up at the end with a 502 error.

Fucking hate Gitlab, go die you piece of shit for dedicated servers.

Removed it and installed Gogs. Had 25 Minutes to set it up completly and I'm happy with it. ✌️

Dont won't to spent 7$ on private Repos for Github, when I have my own high power dedicated Server 😜

You know what, let me jump in on the "I hate PHP" bandwagon.

A couple months ago I upgraded my mail servers unattended. Roundcube got fucked for a couple of months, and I figured.. fuck it, I can still use Dovecot for authenticating with desktop mail clients like K-9.
Recently I unfucked it, turns out that it was an issue with the sock file in php-fpm. That's also when I noticed that PHP apparently hardcodes in its current version in the bloody socket file. Because why the fuck wouldn't you? It makes upgrades so much fucking easier!!! Said no fucking sysadmin ever!!!

And today I upgraded one of my mail servers to Ubuntu Server 18.04, finally, after a lot of hesitation. Bad decision, because now PHP got fucked YET AGAIN.
Again an issue with socket files? I have no fucking idea. systemctl shows no failed services (because you know PHP, why would you fail your service with an error message instead of throwing a meaningless 502 Bad Gateway, right?!!) and looking at the config files, well the socket file got its new php-fpm 7.2 file (still got the fucking version number hardcoded in) and thus I changed that socket file location in /etc/php/7.0...

devRant may just have been my rubber duck.

WHY THE FUCK DO YOU STINKING FUCKING PILE OF SHIT CALLED FUCKING PHP KEEP THE FUCKING 7.0 DIRECTORY OUT THERE WHEN YOU'VE UPGRADED, WITHOUT EVEN HAVING THE FUCKING BALLS TO RENAME THE MOTHERFUCKING DIRECTORY TO 7.2, IF YOU'RE GOING TO HARDCODE IN YOUR VERSION NUMBERS ANYWAY?!!!!!

Bloody fucking pile of fucking junk!!!!

~ Old McDonald's had a farm, 502 error? ~

```js
const app = require('express')()
app.get('/myname', (req, res) => {
res.status(502).send('Bad Gateway.\nUnknown header in brain response: "Hello world!".')
})
app.listen(80)
```

I don't understand wtf is happening today..

- in project A, terraform suddenly decided to stop working with kubernetes-related providers -- the CA cert mismatch error. I agree, it should be not working, because there are 2 kube-api severs behind an LB. But why now??? Why was it working for the last 2 months, until NOW????

- in project B, terraform suddenly decided to stop working _correctly_ with kubernetes-related providers -- it doesn't find resources randomly, even though they are available and I can see them via kubectl get. TF_LOG=DEBUG shows terraform sending correct requests to the kube-api, but the response is a 404. wtf... I see those resources present in another terminal window, only using kubectl. wtf....

- my PR in github was commented, I wanted to ask a question seconds later, and I'm getting a 502 from GH

wtf... I can't spot a pattern and that drives me freaking crazy.

Is this the Friday's curse...? IDK

Fucking hell this shitty web panel for my vps returns a cloudflare 502 error.
What the fuck