#apache

7 posts · Last used 9d

Back to Timeline
blog
@blog@social.christiansblog.eu · Jun 09, 2026
🚛 Neuer Beitrag auf ChristiansBlog.eu Nextcloud-Server von einer USB-NVMe auf eine interne SATA-Festplatte migrieren – ohne Neuinstallation Ein Praxis-Tutorial zur Migration eines laufenden Debian- und Nextcloud-Servers von einer USB-NVMe auf eine interne SATA-Festplatte – inklusive GRUB, rsync, fstab und typischer Fehlerfallen. 🔗 https://christiansblog.eu/post/tutorial/serverumzug/ #NextCloud #Debian #Linux #Server #Migration #NVMe #SATA #Apache #GRUB #Tutorial #HomeServer #Selfhosting
0
0
0
analytics
@analytics@social.vir.group · Jun 09, 2026
🟡 Military Incident | 7/10 🇺🇸 🇮🇷 AH-64 Apache downed near Strait of Hormuz A U.S. Army AH-64 Apache helicopter went down near the Strait of Hormuz. Both crew members were rescued safely. The cause is under investigation. #OSINT #NewsGroup #MilitaryIncident #StraitOfHormuz #Apache
0
0
0
In reply to
jimmyb
@jimmyb@selfhosted.cafe · Jun 01, 2026
@endareth@disobey.net You could use something like #Cloudflare, but I've never been a big fan of proxies in front of proxies, or I found this from searching the web just now - https://binadit.com/tutorials/implement-haproxy-waf-integration-modsecurity I do use #Apache w/ mod_security on my cPanel & WHM box. At home I use #Traefik with a #Crowdsec plugin that seems to work well.
0
0
0
adhisimon
@adhisimon@mastodon.kodesumber.com · May 06, 2026
Yang masih pakai #httpd nya #apache silahkan dicek, kena impact-nya gak Critical Apache HTTP/2 Flaw (CVE-2026-23918) Enables DoS and Potential RCE https://thehackernews.com/2026/05/critical-apache-http2-flaw-cve-2026.html #cve #infosec
1
7
1
icing
@icing@chaos.social · May 06, 2026
"That 'responsible disclosure' Thing" A post with the details of CVE-2026-23918, the double free vulnerability fixed in Apache httpd 2.4.67. #apache https://eissing.org/icing/posts/responsible-disclosure/
38
8
48
juergen_hubert
@juergen_hubert@mementomori.social · Feb 12, 2026
RE: https://mementomori.social/@juergen_hubert/115984654197203481 I am having a massive outage. Again. And the hosting provider doesn't allow the installation of additional tools that might help me get to the bottom of this. Now I am contemplating that I might host my own non-public #Apache server on my own desktop PC (running Windows 11) and run the #MediaWiki #PHP code there as a private instance for testing purposes. Whether I can replicate this problem there or not - either should be instructice. But since I am very much a newbie at this, can anyone point be to a good guide for this kind of thing?
Quoting
Jürgen Hubert @juergen_hubert@mementomori.social
Still trying to figure out my website outages. To recap: I have two #MediaWiki wikis and one #WordPress site. And there seems to be _some_ background process which starts soon after 23:00 UTC (or 24:00 in France, where the servers are located) which puts such a strain on the website that I get a lot of "504" errors for a few hours. The exact duration is variable - sometimes it lasts for one or two hours, and sometimes it lasts way into the morning. But I cannot identify what causes it from the Apache logs - there is no clear, consistent trigger to be found there. Last time I asked customer support, they suggested that I check my plugins and background processes. But I don't know enough about website administration to know where to look. For what it's worth, my WordPress website uses the following plugins (all updated to the latest versions): ActivityPub Contact Form 7 Include Mastodon Feed JM Twitter Cards Leaflet Map MC4WP: Mailchimp for WordPress TablePress WP DSGVO Tools (GDPR) The site is here: https://sunkencastles.com/ The extensions on my wiki can be found here: https://wiki.sunkencastles.com/wiki/Special:Version Does _anyone_ have any idea what kinds of background processes on MediaWiki or WordPress might cause this kind of outage, and how I could check it? #FediHelp
Open quoted post
4
4
3
FibroJedi__dup_32774
@FibroJedi__dup_32774@gamepad.club · Jan 30, 2026
If my site is running a bit slow, folks, it's because I broke my local #apache installation and so I'm having to create an export from the live site. I'll have to leave this running and go get meds & sleep. And de-stress, because that was kinda the point. G'night / #StaySafe
4
0
0

You've seen all posts