selfhosting

533 views
5 Discussing
Finance_News
ยท
--
๐Ÿ“ฐ An unresponsive VPS was a crypto miner, dropped through a brute-forced SSH login The first sign wasn't a breach alert. It was my AI agent going quiet โ€” the thing that runs most of my infrastructure just stopped responding. When I finally got a terminal, top showed a process named /tmp/mysql burning 381% CPU and 2.4 GB of RAM. It wasn't MySQL. It was a crypto miner, dropped onto my VPS through a brute-forced SSH login. How it got in I'd left three doors open: PermitRootLogin yes password authentication enabled no brute-force protection The logs showed 30+ failed SSH logins per hour from a rotating set of IPs. Eventually one guessed a weak credential, and the miner came with it. The fix, step by step Kill the miner. kill -9 the process and delete the /tmp/mysql binary. Lock SSH to keys. PermitRootLogin prohibit-password and PasswordAuthentication no. No password = nothing left to brute-force. fail2ban. 24-hour bans (up from 1 hour) plus a recidive jail that bans repeat offenders for a week. rkhunter. A rootkit scan to confirm nothing else was hiding โ€” 498 rootkits in its database, 0 found. Unattended upgrades. So the next SSH or kernel CVE patches itself instead of waiting for me to notice. The numbers before and after CPU idle: 0% โ†’ 79% Load average: 6.06 โ†’ 1.54 Free RAM: 1.5 GB โ†’ 3.9 GB Within a week fail2ban had blocked 44 IPs and 15,678 failed SSH attempts. The brute-force noise never stopped โ€” it just stopped mattering. The lesson A $6 VPS exposed to the internet is a target the moment it boots. The whole incident โ€” from "why is everything slow" to "clean and hardened" โ€” took about two hours, and every fix was something I should have had on day one. If you self-host, do this before the miner finds you, not after. Full write-up with the before/after numbers and configs: https://igornews.com/2026/11/08/ssh-brute-force-crypto-miner-vps-hardening/ Source : Dev Community Time : 2026-11-22 03:57:47 Credit : igor rakov #selfhosting #devops #linux #security Share your opinion in the comment section below
๐Ÿ“ฐ An unresponsive VPS was a crypto miner, dropped through a brute-forced SSH login
The first sign wasn't a breach alert. It was my AI agent going quiet โ€” the thing that runs most of my infrastructure just stopped responding. When I finally got a terminal, top showed a process named /tmp/mysql burning 381% CPU and 2.4 GB of RAM. It wasn't MySQL. It was a crypto miner, dropped onto my VPS through a brute-forced SSH login. How it got in I'd left three doors open: PermitRootLogin yes password authentication enabled no brute-force protection The logs showed 30+ failed SSH logins per hour from a rotating set of IPs. Eventually one guessed a weak credential, and the miner came with it. The fix, step by step Kill the miner. kill -9 the process and delete the /tmp/mysql binary. Lock SSH to keys. PermitRootLogin prohibit-password and PasswordAuthentication no. No password = nothing left to brute-force. fail2ban. 24-hour bans (up from 1 hour) plus a recidive jail that bans repeat offenders for a week. rkhunter. A rootkit scan to confirm nothing else was hiding โ€” 498 rootkits in its database, 0 found. Unattended upgrades. So the next SSH or kernel CVE patches itself instead of waiting for me to notice. The numbers before and after CPU idle: 0% โ†’ 79% Load average: 6.06 โ†’ 1.54 Free RAM: 1.5 GB โ†’ 3.9 GB Within a week fail2ban had blocked 44 IPs and 15,678 failed SSH attempts. The brute-force noise never stopped โ€” it just stopped mattering. The lesson A $6 VPS exposed to the internet is a target the moment it boots. The whole incident โ€” from "why is everything slow" to "clean and hardened" โ€” took about two hours, and every fix was something I should have had on day one. If you self-host, do this before the miner finds you, not after. Full write-up with the before/after numbers and configs: https://igornews.com/2026/11/08/ssh-brute-force-crypto-miner-vps-hardening/
Source : Dev Community
Time : 2026-11-22 03:57:47
Credit : igor rakov
#selfhosting #devops #linux #security

Share your opinion in the comment section below
ยท
--
Stop! ๐Ÿ›‘ Never run an installer with elevated admin privileges from a random blog link. Before any automated trading software touches your keys, you must verify its origin and integrity to prevent unauthorized access. Here is the non-negotiable checklist for safely downloading and setting up any trading bot: 1. Always restrict downloads to the official GitHub repository or designated community website. Any file from a random blog or direct message should be treated as unverified. โš ๏ธ 2. To confirm file integrity, manually compare the SHA-256 digest of the downloaded file against the digest published by the maintainers on official release notes. If they don't match, do not install. โœ… 3. For extra assurance, technically inclined users can verify the cryptographic signature of the release against the project's public key to confirm the builder's identity. 4. Be wary of red flags: mismatched digests, unknown download sources, or any request to run an installer with elevated admin privileges from an unverified location. ๐Ÿšฉ 5. Remember, transparency is key to safe self-hosting, letting you verify exactly what software is running on your system. For a detailed walkthrough of these verification steps, review our documentation here: https://community.wolfbot.io/docs/how-to-verify-a-downloaded-trading-bot #CryptoSecurity #TradingBot #SelfHosting #Crypto #DevOps
Stop! ๐Ÿ›‘ Never run an installer with elevated admin privileges from a random blog link.

Before any automated trading software touches your keys, you must verify its origin and integrity to prevent unauthorized access.

Here is the non-negotiable checklist for safely downloading and setting up any trading bot:

1. Always restrict downloads to the official GitHub repository or designated community website. Any file from a random blog or direct message should be treated as unverified. โš ๏ธ
2. To confirm file integrity, manually compare the SHA-256 digest of the downloaded file against the digest published by the maintainers on official release notes. If they don't match, do not install. โœ…
3. For extra assurance, technically inclined users can verify the cryptographic signature of the release against the project's public key to confirm the builder's identity.
4. Be wary of red flags: mismatched digests, unknown download sources, or any request to run an installer with elevated admin privileges from an unverified location. ๐Ÿšฉ
5. Remember, transparency is key to safe self-hosting, letting you verify exactly what software is running on your system.

For a detailed walkthrough of these verification steps, review our documentation here: https://community.wolfbot.io/docs/how-to-verify-a-downloaded-trading-bot

#CryptoSecurity #TradingBot #SelfHosting #Crypto #DevOps
ยท
--
Choosing between Community and Cloud in WolfBot feels less like a feature difference and more like choosing your operational mindset. ๐Ÿง Both editions offer the same core operating model: โ€ข Unified crypto support โ€ข Futures integration โ€ข MT5 compatibility โ€ข Portfolio-level risk management on one surface The real divergence point is who handles the 'boring work.' ๐Ÿ› ๏ธ Community requires you to own the host, updates, backups, and uptime. You manage the infrastructure. Cloud delegates all that infrastructure management entirely to WolfBot. How to decide? Weigh these three factors: 1. Your tolerance for system administration tasks. 2. The value of your time vs. the cost of hardware/VPS. 3. Whether you need absolute control over data location. If you are comfortable running your own PC or VPS and commit to weekly maintenance, Community is flexible. If your time is better spent on strategy development than system administration, and you prefer hands-off, Cloud is recommended. โ˜๏ธ Good news: migrating between editions is straightforward because the operating model is the sameโ€”your strategies translate directly. Review this deep dive to help weigh the factors against your technical comfort level: https://community.wolfbot.io/docs/community-or-cloud-deep-dive If avoiding server management is key, Cloud is the path. If autonomy matters most, Community is ready. โœ… #WolfBot #CryptoAutomation #TradingStrategy #SelfHosting #CryptoTech
Choosing between Community and Cloud in WolfBot feels less like a feature difference and more like choosing your operational mindset. ๐Ÿง

Both editions offer the same core operating model:
โ€ข Unified crypto support
โ€ข Futures integration
โ€ข MT5 compatibility
โ€ข Portfolio-level risk management on one surface

The real divergence point is who handles the 'boring work.' ๐Ÿ› ๏ธ

Community requires you to own the host, updates, backups, and uptime. You manage the infrastructure.
Cloud delegates all that infrastructure management entirely to WolfBot.

How to decide? Weigh these three factors:
1. Your tolerance for system administration tasks.
2. The value of your time vs. the cost of hardware/VPS.
3. Whether you need absolute control over data location.

If you are comfortable running your own PC or VPS and commit to weekly maintenance, Community is flexible.
If your time is better spent on strategy development than system administration, and you prefer hands-off, Cloud is recommended. โ˜๏ธ

Good news: migrating between editions is straightforward because the operating model is the sameโ€”your strategies translate directly.

Review this deep dive to help weigh the factors against your technical comfort level:
https://community.wolfbot.io/docs/community-or-cloud-deep-dive

If avoiding server management is key, Cloud is the path. If autonomy matters most, Community is ready. โœ…

#WolfBot #CryptoAutomation #TradingStrategy #SelfHosting #CryptoTech
ยท
--
Tired of the recurring expense and overhead of renting a dedicated Windows VPS just for MetaTrader 5? ๐Ÿ˜ฉ Moving your MT5 infrastructure to a self-hosted model keeps your positions and keys on hardware you directly manage, offering clear cost savings and superior control. Here is the path to consolidating your trading environment: 1. Self-hosting means running your MT5 terminal on infrastructure you personally control (like your own Linux box or VPS), instead of relying on a machine rented solely for that purpose. 2. With this setup, you keep a fully functional MT5 terminalโ€”including your broker login, charts, and open ordersโ€”while dropping the need for that second, dedicated remote machine. ๐Ÿ’ฐ 3. The primary benefits are avoiding an extra Windows-VPS bill and gaining increased control over your operational hardware. 4. WolfBot integrates this by running the MT5 terminal inside a container on your existing machine, making it accessible via your browser without needing a separate Windows server or remote-desktop client. โœ… 5. If you are comfortable managing your own server environment, this path offers a single browser interface for both your crypto accounts and your MT5 trading, simplifying your setup compared to managing multiple rented desktops. If you are ready to explore this level of infrastructure control, review the detailed documentation here: https://community.wolfbot.io/docs/mt5-self-hosted-trading #MT5 #SelfHosting #CryptoAutomation #LinuxVPS #TradingTech
Tired of the recurring expense and overhead of renting a dedicated Windows VPS just for MetaTrader 5? ๐Ÿ˜ฉ

Moving your MT5 infrastructure to a self-hosted model keeps your positions and keys on hardware you directly manage, offering clear cost savings and superior control.

Here is the path to consolidating your trading environment:

1. Self-hosting means running your MT5 terminal on infrastructure you personally control (like your own Linux box or VPS), instead of relying on a machine rented solely for that purpose.
2. With this setup, you keep a fully functional MT5 terminalโ€”including your broker login, charts, and open ordersโ€”while dropping the need for that second, dedicated remote machine. ๐Ÿ’ฐ
3. The primary benefits are avoiding an extra Windows-VPS bill and gaining increased control over your operational hardware.
4. WolfBot integrates this by running the MT5 terminal inside a container on your existing machine, making it accessible via your browser without needing a separate Windows server or remote-desktop client. โœ…
5. If you are comfortable managing your own server environment, this path offers a single browser interface for both your crypto accounts and your MT5 trading, simplifying your setup compared to managing multiple rented desktops.

If you are ready to explore this level of infrastructure control, review the detailed documentation here: https://community.wolfbot.io/docs/mt5-self-hosted-trading

#MT5 #SelfHosting #CryptoAutomation #LinuxVPS #TradingTech
Log in to explore more content
Join global crypto users on Binance Square
โšก๏ธ Get latest and useful information about crypto.
๐Ÿ’ฌ Trusted by the worldโ€™s largest crypto exchange.
๐Ÿ‘ Discover real insights from verified creators.
Email / Phone number