coderandcreator

Full-Stack Dev | UI/UX |
Building & breaking things on the web | Tech Blogs at

[coderandcreator @coderandcreator]

@buildwithsid You are appearing on 1 because you visit it much often, try in incognito or private window.

[coderandcreator @coderandcreator]

Me : I will do something I'm really good at.
AI : Sorry ?

[coderandcreator @coderandcreator]

@vineetwts @interfaze_ai W

[coderandcreator @coderandcreator]

A critical vulnerability was recently disclosed affecting NGINX servers. Here's exactly how a production Linux server was patched - zero downtime, zero dropped connections.

Step 1 - Verify available security updates

After logging in, package lists were refreshed and upgradable packages were checked:

apt update
apt list --upgradable

Ubuntu had already released a patched build:
nginx 1.24.0-2ubuntu7.8

Ubuntu often backports fixes without bumping the major version — always check the full package revision.

---

Step 2 - Upgrade only NGINX first

Rather than upgrading the entire server at once, only the exposed web server was patched first:

apt install --only-upgrade nginx nginx-common -y

Surgical upgrades = fewer unrelated service interruptions. Risk minimized.

---

Step 3 - Validate config before touching anything live.

Before any service action, the configuration syntax was verified:

nginx -t

Output confirmed: ✅ syntax is ok / test is successful

Never skip this in production.
A broken config on restart = outage.

---

Step 4 - Gracefully reload, don't restart

This is the key move:

systemctl reload nginx ✅
systemctl restart nginx ❌

A reload lets existing connections finish while new workers load the patched binaries.

A restart kills active connections. Avoidable downtime.

---

Step 5 - Verify the patched version

NGINX's version string can be misleading. The actual package revision was confirmed via:

dpkg -l | grep nginx

Result: 1.24.0-2ubuntu7.8 — the patched Ubuntu build. Version strings alone don't tell the full story.

---

Step 6 - Audit vulnerable directives

The reported exploit path involved rewrite and set directives. All configs were audited:

grep -R "rewrite\|set " /etc/nginx/

This surfaces overly complex rewrites, user-controlled rewrites, unsafe regex, and legacy configs nobody remembers writing.

---

Step 7 - Verify ASLR + PIE hardening

The disclosure noted that ASLR significantly reduces exploit reliability. Verified:

cat /proc/sys/kernel/randomize_va_space → 2

readelf -h $(which nginx) | grep Type → DYN

Modern Ubuntu enables both by default. Still worth confirming.

---

Step 8 - Monitor post-patch for worker crashes

Even after patching, the server was monitored carefully:

systemctl status nginx
tail -f /var/log/nginx/error.log

Watched specifically for: segfaults, worker crashes, signal 11 errors, unexpected reloads.

Everything stayed stable.

---

Steps 9 - Remaining packages upgraded, server confirmed online

apt upgrade -y

Ubuntu flagged a kernel update requiring a reboot -intentionally deferred until off-peak.

Final check:
systemctl status nginx → active, stable, serving traffic.

The entire process got zero dropped connections.
Zero downtime. ✅

I hope this helps.

[International Cyber Digest @IntCyberDigest]

‼️🚨 MAJOR IMPACT: AI just found an 18-year-old NGINX critical remote code execution vulnerability. It has been disclosed on GitHub including PoC code.

- Affects NGINX 0.6.27 through 1.30.0
- Triggered via the rewrite and set directives in config
- Update NGINX ASAP
- NGINX is a widely used HTTP web server, be sure to check its prevalence in other products

[coderandcreator @coderandcreator]

If your Taskbar is frozen on Windows 11:

Press Ctrl + Shift + Esc → find Windows Explorer → right click → Restart

Fixes instantly.

PS: I kept restarting my whole PC before discovering this

[coderandcreator @coderandcreator]

I repeat : always choose the hard way.

[coderandcreator @coderandcreator]

@sanjeevs91 Noted sir

[coderandcreator @coderandcreator]

@priyanshudotsol I approve this content, keep creating , big hug 🫂

[coderandcreator @coderandcreator]

Locked in for 3 hours straight.

[coderandcreator @coderandcreator]

@git_cuber Switch to Nariyal pani ASAP.

[coderandcreator @coderandcreator]

For me : Since I started using claude, my gpt usage has decreased significantly.

I love the way Claude provides response.

Thank you @claudeai ❤️

[Striver | Building takeUforward @striver_79]

At this point, @claudeai new launches are not upto the mark. They launch something and quickly move on to the next.

They don’t care about fixing the bugs, nor do they work on it post-launch.

Standard template:

> Launch something with a fancy video
> Pay people to write “abc is dead”
> Move on to the next

A decade later, @Google is going to win this AI race when it comes to end users by some margin. For enterprise and all, you may see others around.

[coderandcreator @coderandcreator]

@kunalmpawar_ @claudeai Just wait for a while , it is still facing downtime. And keep fingers crossed 🤞 😄

[coderandcreator @coderandcreator]

Perks of vibe coding 💀

Is @claudeai down ?

[coderandcreator @coderandcreator]

@maestroalvarez @ChainCoderCG @claudeai I have checked but there were no reports of the downtime there.

[coderandcreator @coderandcreator]

@kunalmpawar_ @claudeai Damn , maybe you pulled out all the tokens 🤣

[coderandcreator @coderandcreator]

@ChainCoderCG @claudeai Claude status shows no report of downtime but it is down.

[coderandcreator @coderandcreator]

@kairveee Only if Kanye east is coming