Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


Shells Virtual Desktop
BMail.ag - Secure Email Service
Server.net
CPLicense.net
VPS Server
Buy VPN
Vultr
VMs for AI
HostDare
ReliableSite White-Label Dedicated Hosting for Resellers
InterServer VPS
BMail.ag - Secure Email Service
Best VPN
High-Performance Bare Metal Server Solutions
Karvl.com
Server Mania Cloud Hosting
DataWagon Hosting
AlphaVPS Hosting
Evoxt.com
Clouvider
VPS Hosting with NVMe
Residential IPs in the US & 4G Mobile Proxies in EU & US with Unlimited Bandwidth
ReliableSite White-Label Dedicated Hosting for Resellers
Rabisu - Hosting Solutions
Shells Virtual Desktop
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

★ VirMach ★ RYZEN ★ NVMe ★★ $8.88/YR- 384MB ★★ $21.85/YR- 2.5GB ★ Instant ★ Japan Pre-order ★ & More

1133134136138139339

Comments

  • miaumiau Member
    edited April 2022

    @AlwaysSkint said:
    ^ broadcast/multicast packets? Port scans from your 'friendly neighbours'?

    Apparently our IP range is bot magnet.
    Less than 48 hours up, my sshguard permaban is already filling up long list of ip.

    # nft list table ip sshguard
    table ip sshguard {
            set attackers {
                    type ipv4_addr
                    flags interval
                    elements = { 45.134.26.137, 61.177.172.59,
                                 61.177.172.61, 61.177.172.76,
                                 61.177.172.87, 61.177.172.89,
                                 61.177.172.91, 61.177.172.98,
                                 61.177.172.108, 61.177.172.124,
                                 61.177.172.160, 61.177.172.174,
                                 61.177.172.175, 61.177.173.20,
                                 61.177.173.35, 61.177.173.36,
                                 61.177.173.37, 61.177.173.39,
                                 61.177.173.40, 61.177.173.41,
                                 61.177.173.42, 61.177.173.44,
                                 61.177.173.46, 61.177.173.50,
                                 61.177.173.51, 61.177.173.54,
                                 85.202.169.124, 122.194.229.10,
                                 141.98.11.29, 159.65.113.87,
                                 159.65.205.82, 159.223.212.234,
                                 161.35.89.112, 161.35.89.214,
                                 163.123.142.166, 164.92.135.120,
                                 179.43.154.137, 179.43.154.138,
                                 194.165.16.5, 208.115.245.222,
                                 218.92.0.221 }
            }
    
    Thanked by 1FrankZ
  • I gave up on SSH fail2ban long time ago.
    It'll be filled up with hundreds of thousands of IPs in just a few days.

    If IPv6 is available I'll just turn off listening on 0.0.0.0, connect via IPv6 instead and enjoy the peace.

    Wonder if routed IPv6 will be available when my Tokyo storage VPS gets deployed.

  • Close port 22 and be happy. CSF and country blocks helps a little.

  • Three hours on, Debian 11 is still running on node 39.

    Thanked by 1qwerttaa
  • @VirMach said: Maybe I'll sprinkle in some free RAM upgrades to people who made 0 tickets, 0 comments with their ticket ID, etc, since we have so much extra. I already regret saying that because the people that made the most tickets are probably going to start making tickets asking for free RAM now.

    Yes pls

    I have 0 ticket and 0 comments about ticket id B)

    Thanked by 1tototo
  • FrankZFrankZ Barred
    edited April 2022

    @add_iT said:

    @VirMach said: Maybe I'll sprinkle in some free RAM upgrades to people who made 0 tickets, 0 comments with their ticket ID, etc, since we have so much extra. I already regret saying that because the people that made the most tickets are probably going to start making tickets asking for free RAM now.

    Yes pls

    I have 0 ticket and 0 comments about ticket id B)

    and so starts another I wish I did not say that moment for VirMach.

    I really though VirMach said that as a joke, but just in case he was serious...
    0 ticket and 0 comments about ticket id here as well :sunglasses:

    Let the bumps begin !

  • >

  • @add_iT said:

    @ VirMach said: Maybe I'll sprinkle in some free RAM upgrades to people who made 0 tickets, 0 comments with their ticket ID, etc, since we have so much extra. I already regret saying that because the people that made the most tickets are probably going to start making tickets asking for free RAM now.

    Yes pls

    I have 0 ticket and 0 comments about ticket id B)

    I opened a ticket requesting proof that I made 0 tickets.
    Ticket #999XYZ777

  • cybertechcybertech Member
    edited April 2022

    i would love some ram sprinkle on my 2560mb plan. just saying. not that it would be used though.

    Thanked by 1tototo
  • Boss, can you tell me how much it started today? How long is the rest?

  • @NoComment said:

    @qwerttaa said:

    @VirMach said:

    @qwerttaa said:

    @nick_ said:
    Nice! I'm still excitedly waiting for my tiny 384 MB VPS to be activated. Wonder what else I can do with it besides using it as a VPN.

    384 too, i just use it for vpn but i have auto shitdown issues

    If it's just for VPN, let me see if I can get any older templates working for you that have lower resource usage levels. Since everything's calmed down, the ones I've tested so far have worked okay without kernel panic issues so maybe older ones should be fine too.

    first, let me try the pure debian11, then debian10
    but in other providers, 256 ovz works perfectly..................here is 384 kvm...

    What exactly are you running? What debian are you installing? Try installing debian 11 minimal and if you still crash from apt commands then something's really wrong here. 384 MB of ram is definitely enough.

    You only get shutdown if there's really not enough ram and no processes to kill. But you know, maybe this is a result of overselling ram.

    yep, it is debian 11 minimal

    top - 09:43:30 up 21:41, 1 user, load average: 0.00, 0.00, 0.00
    Tasks: 68 total, 1 running, 67 sleeping, 0 stopped, 0 zombie
    %Cpu(s): 0.0 us, 0.0 sy, 0.0 ni, 92.3 id, 0.0 wa, 0.0 hi, 0.0 si, 7.7 st
    MiB Mem : 346.0 total, 46.7 free, 64.4 used, 234.9 buff/cache
    MiB Swap: 473.0 total, 472.7 free, 0.3 used. 270.0 avail Mem

  • @qwerttaa said:

    @nick_ said:
    Nice! I'm still excitedly waiting for my tiny 384 MB VPS to be activated. Wonder what else I can do with it besides using it as a VPN.

    384 too, i just use it for vpn but i have auto shitdown issues

    remember to flush the shit down

    Thanked by 3mrTom bdl karjaj
  • @xiaotom said:
    Boss, can you tell me how much it started today? How long is the rest?

    Have you checked this page?
    https://virmach.com/ryzen-special-offer-news-updates/

    Thanked by 1FrankZ
  • @cybertech said:

    @qwerttaa said:

    @nick_ said:
    Nice! I'm still excitedly waiting for my tiny 384 MB VPS to be activated. Wonder what else I can do with it besides using it as a VPN.

    384 too, i just use it for vpn but i have auto shitdown issues

    remember to flush the shit down

    oh no

    its shutdown...

    just look at your keyboard about i and u......

  • @FrankZ said:
    Three hours on, Debian 11 is still running on node 39.

    top - 09:53:17 up 21:51, 1 user, load average: 0.00, 0.00, 0.00
    Tasks: 68 total, 2 running, 66 sleeping, 0 stopped, 0 zombie
    %Cpu(s): 0.0 us, 0.0 sy, 0.0 ni, 94.5 id, 0.0 wa, 0.0 hi, 1.9 si, 3.6 st
    MiB Mem : 346.0 total, 46.6 free, 64.5 used, 234.9 buff/cache
    MiB Swap: 473.0 total, 472.7 free, 0.3 used. 269.9 avail Mem

    vpn only
    general kernel, not cloud version

  • @miau said:

    @AlwaysSkint said:
    ^ broadcast/multicast packets? Port scans from your 'friendly neighbours'?

    Apparently our IP range is bot magnet.
    Less than 48 hours up, my sshguard permaban is already filling up long list of ip.

    # nft list table ip sshguard
    table ip sshguard {
            set attackers {
                    type ipv4_addr
                    flags interval
                    elements = { 45.134.26.137, 61.177.172.59,
                                 61.177.172.61, 61.177.172.76,
                                 61.177.172.87, 61.177.172.89,
                                 61.177.172.91, 61.177.172.98,
                                 61.177.172.108, 61.177.172.124,
                                 61.177.172.160, 61.177.172.174,
                                 61.177.172.175, 61.177.173.20,
                                 61.177.173.35, 61.177.173.36,
                                 61.177.173.37, 61.177.173.39,
                                 61.177.173.40, 61.177.173.41,
                                 61.177.173.42, 61.177.173.44,
                                 61.177.173.46, 61.177.173.50,
                                 61.177.173.51, 61.177.173.54,
                                 85.202.169.124, 122.194.229.10,
                                 141.98.11.29, 159.65.113.87,
                                 159.65.205.82, 159.223.212.234,
                                 161.35.89.112, 161.35.89.214,
                                 163.123.142.166, 164.92.135.120,
                                 179.43.154.137, 179.43.154.138,
                                 194.165.16.5, 208.115.245.222,
                                 218.92.0.221 }
            }
    

    -A INPUT -p tcp -m tcp --dport "ssh port" -j ACCEPT
    -A INPUT -p tcp -m tcp --dport "vpn port" -j ACCEPT
    -A INPUT -i lo -j ACCEPT
    -A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT
    -A INPUT -j DROP
    -A FORWARD -p tcp -m tcp --tcp-flags SYN,RST SYN -j TCPMSS --clamp-mss-to-pmtu

    with iptables-persistent :wink:

  • cybertechcybertech Member
    edited April 2022

    @qwerttaa said:
    just look at your keyboard about i and u......

    you are right.

    next time i wanna breakup with someone over the internet:

    "between u and i.....shit happened"

  • @qwerttaa said:

    @FrankZ said:
    Three hours on, Debian 11 is still running on node 39.

    top - 09:53:17 up 21:51, 1 user, load average: 0.00, 0.00, 0.00
    Tasks: 68 total, 2 running, 66 sleeping, 0 stopped, 0 zombie
    %Cpu(s): 0.0 us, 0.0 sy, 0.0 ni, 94.5 id, 0.0 wa, 0.0 hi, 1.9 si, 3.6 st
    MiB Mem : 346.0 total, 46.6 free, 64.5 used, 234.9 buff/cache
    MiB Swap: 473.0 total, 472.7 free, 0.3 used. 269.9 avail Mem

    vpn only
    general kernel, not cloud version

    my Debian 11 on TYOC039

    top - 11:12:36 up 1 day, 12:46,  1 user,  load average: 0.07, 0.16, 0.17
    Tasks:  72 total,   1 running,  71 sleeping,   0 stopped,   0 zombie
    %Cpu(s):  0.7 us,  1.3 sy,  0.0 ni, 94.7 id,  0.0 wa,  0.0 hi,  0.3 si,  3.0 st
    MiB Mem :    347.1 total,    197.1 free,     65.2 used,     84.9 buff/cache
    MiB Swap:   2048.0 total,   2016.9 free,     31.1 used.    270.4 avail Mem
    
    Thanked by 1FrankZ
  • FrankZFrankZ Barred
    edited April 2022

    @qwerttaa - I'm running Debian 11.2 with only ssh server, basic system utilities, and iptables installed. Kernel is 5.10.0-13-amd64 #1 SMP Debian 5.10.106-1 (2022-03-17) x86_64 GNU/Linux

    The question I am trying to answer is if the auto shutdown issue is related to RAM, the basic install or something else. Since this is installed on a 2.5 GB VPS, RAM should not be an issue. As described above it is a basic install. It has been previously said that the VPS auto shutdown multiple times in 24 hours. I figure I'll give it a couple of days and see what happens. I was not planning on using this VPS for a few more days anyway.

    EDIT: So is the auto shutdown thing on Debian 11 not happening anymore?
    I see uptimes above of 21 hours, and 36 hours.

    Thanked by 2qwerttaa ZA_capetown
  • @FrankZ said:
    @qwerttaa - I'm running Debian 11.2 with only ssh server, basic system utilities, and iptables installed. Kernel is 5.10.0-13-amd64 #1 SMP Debian 5.10.106-1 (2022-03-17) x86_64 GNU/Linux

    The question I am trying to answer is if the auto shutdown issue is related to RAM, the basic install or something else. Since this is installed on a 2.5 GB VPS, RAM should not be an issue. As described above it is a basic install. It has been previously said that the VPS auto shutdown multiple times in 24 hours. I figure I'll give it a couple of days and see what happens. I was not planning on using this VPS for a few more days anyway.

    EDIT: So is the auto shutdown thing on Debian 11 not happening anymore?
    I see uptimes above of 21 hours, and 36 hours.

    Thanks for the test, I also have close to 24 hours without any problems at the moment, the last time this was recorded was 1 day and 19 hours to be exact, but further back I confirmed over 3 days without any problems - this is from a Chinese machine translation as my mind is now focused on another thing, sorry

    Thanked by 1FrankZ
  • My 768MB tokyo 39 is 47h online, had one or two shutdowns on ubuntu 20.04, almost no memory use but system alone cash duno what and use 90% of all ram for it

  • is everyone use cloud kernel or not?
    anyway, this time i will keep the general kernel and see what happen

    top - 11:21:22 up 23:19, 1 user, load average: 0.00, 0.00, 0.00
    Tasks: 76 total, 1 running, 75 sleeping, 0 stopped, 0 zombie
    %Cpu(s): 0.0 us, 0.0 sy, 0.0 ni, 90.8 id, 0.0 wa, 0.0 hi, 1.6 si, 7.6 st
    MiB Mem : 346.0 total, 44.6 free, 78.0 used, 223.4 buff/cache
    MiB Swap: 473.0 total, 471.2 free, 1.8 used. 256.4 avail Mem

  • @qwerttaa said: is everyone use cloud kernel or not?

    Which cloud kernel? This one? https://packages.debian.org/sid/linux-image-cloud-amd64

  • @xpreboun said:

    @qwerttaa said: is everyone use cloud kernel or not?

    Which cloud kernel? This one? https://packages.debian.org/sid/linux-image-cloud-amd64

    yes
    improve memory usage
    i have tested many vps and there are no compatibility issues
    vir case, im using the general kernel just for now, do some test about shutdown

  • maybe i will do some dig about solusvm api
    https://docs.solusvm.com/Boot+Virtual+Server.html

  • @qwerttaa said:

    @xpreboun said:

    @qwerttaa said: is everyone use cloud kernel or not?

    Which cloud kernel? This one? https://packages.debian.org/sid/linux-image-cloud-amd64

    yes
    improve memory usage
    i have tested many vps and there are no compatibility issues
    vir case, im using the general kernel just for now, do some test about shutdown

    I always use generic or whatever specific on the platform (Azure, AWS)... But yeah I almost never buy any VPS with lower than 1GB ram.

  • @xpreboun said:

    @qwerttaa said:

    @xpreboun said:

    @qwerttaa said: is everyone use cloud kernel or not?

    Which cloud kernel? This one? https://packages.debian.org/sid/linux-image-cloud-amd64

    yes
    improve memory usage
    i have tested many vps and there are no compatibility issues
    vir case, im using the general kernel just for now, do some test about shutdown

    I always use generic or whatever specific on the platform (Azure, AWS)... But yeah I almost never buy any VPS with lower than 1GB ram.

    i have 4 low end stuff only for vps

    and my digitalocean has 2g ram, also cloud kernel now

  • zhuyijunzhuyijun Member
    edited April 2022

    @VirMach said:
    I forgot to provide an update on the page and maybe here, the staggers were marked as not running but were running for some time. We're up to about 77% now.

    Now it's not running.

    unfortunately I am on the 23%

  • miaumiau Member
    edited April 2022

    @qwerttaa said:

    @miau said:

    @AlwaysSkint said:
    ^ broadcast/multicast packets? Port scans from your 'friendly neighbours'?

    Apparently our IP range is bot magnet.
    Less than 48 hours up, my sshguard permaban is already filling up long list of ip.

    # nft list table ip sshguard
    table ip sshguard {
            set attackers {
                    type ipv4_addr
                    flags interval
                    elements = { 45.134.26.137, 61.177.172.59,
                                 61.177.172.61, 61.177.172.76,
                                 61.177.172.87, 61.177.172.89,
                                 61.177.172.91, 61.177.172.98,
                                 61.177.172.108, 61.177.172.124,
                                 61.177.172.160, 61.177.172.174,
                                 61.177.172.175, 61.177.173.20,
                                 61.177.173.35, 61.177.173.36,
                                 61.177.173.37, 61.177.173.39,
                                 61.177.173.40, 61.177.173.41,
                                 61.177.173.42, 61.177.173.44,
                                 61.177.173.46, 61.177.173.50,
                                 61.177.173.51, 61.177.173.54,
                                 85.202.169.124, 122.194.229.10,
                                 141.98.11.29, 159.65.113.87,
                                 159.65.205.82, 159.223.212.234,
                                 161.35.89.112, 161.35.89.214,
                                 163.123.142.166, 164.92.135.120,
                                 179.43.154.137, 179.43.154.138,
                                 194.165.16.5, 208.115.245.222,
                                 218.92.0.221 }
            }
    

    -A INPUT -p tcp -m tcp --dport "ssh port" -j ACCEPT
    -A INPUT -p tcp -m tcp --dport "vpn port" -j ACCEPT
    -A INPUT -i lo -j ACCEPT
    -A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT
    -A INPUT -j DROP
    -A FORWARD -p tcp -m tcp --tcp-flags SYN,RST SYN -j TCPMSS --clamp-mss-to-pmtu

    with iptables-persistent :wink:

    Uhh.. thanks I guess? but what im showing was already part of nftables filter chain rules that blocking ssh ports to listed address, in addition of base default block rules.

    Moving ahead, you should migrate from iptables and start using the modern nftables instead.

  • @VirMach

    1398471 has not been opened for a month. Please deal with it. thank you.

This discussion has been closed.