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

1258259261263264339

Comments

  • foitinfoitin Member

    @Murata_Chink_Best said:
    Another funny story about Double Bandwidth:

    There was some MJJ bought the VPS from a NERD provider, got the double bandwidth. And they always reached the bandwidth limit for several months.
    https://hostloc.com/thread-659900-1-1.html
    https://hostloc.com/thread-662949-2-1.html

    In time, they got refunded and ware kicked out.

    So if there were users always reach bandwidth limit, will you kick them out @VirMach ?

    The same abusers that are causing skyhigh steal time in Tokyo storage?
    SSH is so choppy that I can't even type a single line command without few seconds of interrupts
    @VirMach should kick all abusers out whether it's bandwidth abuser or CPU abusers

    Thanked by 1lemoncube
  • My VPS on TYOC026:

    • ssh halts before shell fully loads
    • clientarea prompts Operation Timed Out After 90001 Milliseconds With 0 Bytes Received after a long delay
    • managed to login into solusvm and powered it down. 2022/06/16 02:21:26 AM Hard Power Off ... Complete
    • vnc shows systemd is still trying to start Journal Service (and failed)
    • reboot in solusvm took too long and failed with Unknown Error with vnc remain the same as above.

    Is it only my vm or the node is acting up?

  • JonesJones Barred

    @VirMach said:

    @lowendclient said:

    @keterjelly said:
    Ticket open for going on 10 days without a response, this is 1/3 of the billing period that I already paid for.

    As JabJab said, once you reply to the ticket, it will move to the end of the queue automatically. Assume they left some tickets to the next day and you reply the ticket everyday as well, you'll never get an answer.

    Once in a while we notice it bouncing around for a while and step in and do it sooner in the queue. I remember doing two such tickets recently with like 10-20 replies on them. It could've been the guy complaining, it could've been someone else.

    That's why I have been afraid to take the initiative to reply to the ticket

    Hey ~ @VirMach
    maybe you can take care of me. The last reply to my ticket was ten days ago.

    Ticket # 571560

    Can you cut a small piece of cake for me to taste
    Maybe you can find a server with some remaining resources to migrate it?
    It's really not easy to spend a lot of time dealing with tickets every day

  • @foitin said:

    @Murata_Chink_Best said:
    Another funny story about Double Bandwidth:

    There was some MJJ bought the VPS from a NERD provider, got the double bandwidth. And they always reached the bandwidth limit for several months.
    https://hostloc.com/thread-659900-1-1.html
    https://hostloc.com/thread-662949-2-1.html

    In time, they got refunded and ware kicked out.

    So if there were users always reach bandwidth limit, will you kick them out @VirMach ?

    The same abusers that are causing skyhigh steal time in Tokyo storage?
    SSH is so choppy that I can't even type a single line command without few seconds of interrupts
    @VirMach should kick all abusers out whether it's bandwidth abuser or CPU abusers

    The best way to reduce abuse is to increase the price, so that many people can be persuaded. Abuse requires script monitoring, but it cannot solve itself

  • edited June 2022

    The network is unstable as proxy by far with my subjective experience.

    Below is ping from GreencloudVPS at the same data center.

    PS: I will post the tcpdump diagnosis later on.

    PING XXX.chinkchinkgo.cf (88.214.22.XXX) 56(84) bytes of data.
    64 bytes from 88.214.22.XXX.static.xtom.com (88.214.22.XXX): icmp_seq=1 ttl=61 time=1.55 ms
    64 bytes from 88.214.22.XXX.static.xtom.com (88.214.22.XXX): icmp_seq=2 ttl=61 time=0.430 ms
    64 bytes from 88.214.22.XXX.static.xtom.com (88.214.22.XXX): icmp_seq=3 ttl=61 time=5.56 ms
    64 bytes from 88.214.22.XXX.static.xtom.com (88.214.22.XXX): icmp_seq=4 ttl=61 time=1645 ms
    64 bytes from 88.214.22.XXX.static.xtom.com (88.214.22.XXX): icmp_seq=5 ttl=61 time=2549 ms
    64 bytes from 88.214.22.XXX.static.xtom.com (88.214.22.XXX): icmp_seq=7 ttl=61 time=616 ms
    64 bytes from 88.214.22.XXX.static.xtom.com (88.214.22.XXX): icmp_seq=8 ttl=61 time=105 ms
    64 bytes from 88.214.22.XXX.static.xtom.com (88.214.22.XXX): icmp_seq=9 ttl=61 time=0.232 ms
    64 bytes from 88.214.22.XXX.static.xtom.com (88.214.22.XXX): icmp_seq=10 ttl=61 time=10.7 ms
    64 bytes from 88.214.22.XXX.static.xtom.com (88.214.22.XXX): icmp_seq=11 ttl=61 time=19.6 ms
    64 bytes from 88.214.22.XXX.static.xtom.com (88.214.22.XXX): icmp_seq=12 ttl=61 time=15.6 ms
    64 bytes from 88.214.22.XXX.static.xtom.com (88.214.22.XXX): icmp_seq=13 ttl=61 time=2.49 ms
    64 bytes from 88.214.22.XXX.static.xtom.com (88.214.22.XXX): icmp_seq=14 ttl=61 time=0.590 ms
    64 bytes from 88.214.22.XXX.static.xtom.com (88.214.22.XXX): icmp_seq=15 ttl=61 time=7.95 ms
    64 bytes from 88.214.22.XXX.static.xtom.com (88.214.22.XXX): icmp_seq=16 ttl=61 time=14.5 ms
    64 bytes from 88.214.22.XXX.static.xtom.com (88.214.22.XXX): icmp_seq=17 ttl=61 time=26.0 ms
    64 bytes from 88.214.22.XXX.static.xtom.com (88.214.22.XXX): icmp_seq=18 ttl=61 time=3.26 ms
    64 bytes from 88.214.22.XXX.static.xtom.com (88.214.22.XXX): icmp_seq=23 ttl=61 time=152 ms
    64 bytes from 88.214.22.XXX.static.xtom.com (88.214.22.XXX): icmp_seq=24 ttl=61 time=0.379 ms
    64 bytes from 88.214.22.XXX.static.xtom.com (88.214.22.XXX): icmp_seq=25 ttl=61 time=3.32 ms
    64 bytes from 88.214.22.XXX.static.xtom.com (88.214.22.XXX): icmp_seq=26 ttl=61 time=28.0 ms
    64 bytes from 88.214.22.XXX.static.xtom.com (88.214.22.XXX): icmp_seq=27 ttl=61 time=0.246 ms
    64 bytes from 88.214.22.XXX.static.xtom.com (88.214.22.XXX): icmp_seq=28 ttl=61 time=0.374 ms
    64 bytes from 88.214.22.XXX.static.xtom.com (88.214.22.XXX): icmp_seq=29 ttl=61 time=0.242 ms
    64 bytes from 88.214.22.XXX.static.xtom.com (88.214.22.XXX): icmp_seq=30 ttl=61 time=17.2 ms
    64 bytes from 88.214.22.XXX.static.xtom.com (88.214.22.XXX): icmp_seq=31 ttl=61 time=21.2 ms
    64 bytes from 88.214.22.XXX.static.xtom.com (88.214.22.XXX): icmp_seq=32 ttl=61 time=0.298 ms
    64 bytes from 88.214.22.XXX.static.xtom.com (88.214.22.XXX): icmp_seq=37 ttl=61 time=0.266 ms
    64 bytes from 88.214.22.XXX.static.xtom.com (88.214.22.XXX): icmp_seq=38 ttl=61 time=0.238 ms
    64 bytes from 88.214.22.XXX.static.xtom.com (88.214.22.XXX): icmp_seq=39 ttl=61 time=0.291 ms
    64 bytes from 88.214.22.XXX.static.xtom.com (88.214.22.XXX): icmp_seq=40 ttl=61 time=0.243 ms
    64 bytes from 88.214.22.XXX.static.xtom.com (88.214.22.XXX): icmp_seq=41 ttl=61 time=8.31 ms
    64 bytes from 88.214.22.XXX.static.xtom.com (88.214.22.XXX): icmp_seq=42 ttl=61 time=0.245 ms
    64 bytes from 88.214.22.XXX.static.xtom.com (88.214.22.XXX): icmp_seq=43 ttl=61 time=0.322 ms
    64 bytes from 88.214.22.XXX.static.xtom.com (88.214.22.XXX): icmp_seq=44 ttl=61 time=0.303 ms
    64 bytes from 88.214.22.XXX.static.xtom.com (88.214.22.XXX): icmp_seq=45 ttl=61 time=92.1 ms
    64 bytes from 88.214.22.XXX.static.xtom.com (88.214.22.XXX): icmp_seq=48 ttl=61 time=1296 ms
    64 bytes from 88.214.22.XXX.static.xtom.com (88.214.22.XXX): icmp_seq=49 ttl=61 time=353 ms
    64 bytes from 88.214.22.XXX.static.xtom.com (88.214.22.XXX): icmp_seq=50 ttl=61 time=0.228 ms
    64 bytes from 88.214.22.XXX.static.xtom.com (88.214.22.XXX): icmp_seq=51 ttl=61 time=0.414 ms
    64 bytes from 88.214.22.XXX.static.xtom.com (88.214.22.XXX): icmp_seq=52 ttl=61 time=0.464 ms
    64 bytes from 88.214.22.XXX.static.xtom.com (88.214.22.XXX): icmp_seq=53 ttl=61 time=1.97 ms
    64 bytes from 88.214.22.XXX.static.xtom.com (88.214.22.XXX): icmp_seq=54 ttl=61 time=35.0 ms
    64 bytes from 88.214.22.XXX.static.xtom.com (88.214.22.XXX): icmp_seq=55 ttl=61 time=18.1 ms
    64 bytes from 88.214.22.XXX.static.xtom.com (88.214.22.XXX): icmp_seq=56 ttl=61 time=0.453 ms
    64 bytes from 88.214.22.XXX.static.xtom.com (88.214.22.XXX): icmp_seq=57 ttl=61 time=0.571 ms
    64 bytes from 88.214.22.XXX.static.xtom.com (88.214.22.XXX): icmp_seq=58 ttl=61 time=0.222 ms
    64 bytes from 88.214.22.XXX.static.xtom.com (88.214.22.XXX): icmp_seq=59 ttl=61 time=443 ms
    64 bytes from 88.214.22.XXX.static.xtom.com (88.214.22.XXX): icmp_seq=61 ttl=61 time=1750 ms
    64 bytes from 88.214.22.XXX.static.xtom.com (88.214.22.XXX): icmp_seq=62 ttl=61 time=1152 ms
    64 bytes from 88.214.22.XXX.static.xtom.com (88.214.22.XXX): icmp_seq=63 ttl=61 time=499 ms
    64 bytes from 88.214.22.XXX.static.xtom.com (88.214.22.XXX): icmp_seq=64 ttl=61 time=0.252 ms
    64 bytes from 88.214.22.XXX.static.xtom.com (88.214.22.XXX): icmp_seq=65 ttl=61 time=0.580 ms
    64 bytes from 88.214.22.XXX.static.xtom.com (88.214.22.XXX): icmp_seq=66 ttl=61 time=0.220 ms
    64 bytes from 88.214.22.XXX.static.xtom.com (88.214.22.XXX): icmp_seq=67 ttl=61 time=7.20 ms
    64 bytes from 88.214.22.XXX.static.xtom.com (88.214.22.XXX): icmp_seq=68 ttl=61 time=0.367 ms
    64 bytes from 88.214.22.XXX.static.xtom.com (88.214.22.XXX): icmp_seq=69 ttl=61 time=0.310 ms
    64 bytes from 88.214.22.XXX.static.xtom.com (88.214.22.XXX): icmp_seq=70 ttl=61 time=1.04 ms
    64 bytes from 88.214.22.XXX.static.xtom.com (88.214.22.XXX): icmp_seq=71 ttl=61 time=0.253 ms
    64 bytes from 88.214.22.XXX.static.xtom.com (88.214.22.XXX): icmp_seq=72 ttl=61 time=264 ms
    64 bytes from 88.214.22.XXX.static.xtom.com (88.214.22.XXX): icmp_seq=73 ttl=61 time=1850 ms
    64 bytes from 88.214.22.XXX.static.xtom.com (88.214.22.XXX): icmp_seq=77 ttl=61 time=0.275 ms
    64 bytes from 88.214.22.XXX.static.xtom.com (88.214.22.XXX): icmp_seq=78 ttl=61 time=0.297 ms
    64 bytes from 88.214.22.XXX.static.xtom.com (88.214.22.XXX): icmp_seq=79 ttl=61 time=0.245 ms
    64 bytes from 88.214.22.XXX.static.xtom.com (88.214.22.XXX): icmp_seq=80 ttl=61 time=3.48 ms
    64 bytes from 88.214.22.XXX.static.xtom.com (88.214.22.XXX): icmp_seq=81 ttl=61 time=15.5 ms
    64 bytes from 88.214.22.XXX.static.xtom.com (88.214.22.XXX): icmp_seq=82 ttl=61 time=0.260 ms
    64 bytes from 88.214.22.XXX.static.xtom.com (88.214.22.XXX): icmp_seq=83 ttl=61 time=0.285 ms
    64 bytes from 88.214.22.XXX.static.xtom.com (88.214.22.XXX): icmp_seq=84 ttl=61 time=0.366 ms
    64 bytes from 88.214.22.XXX.static.xtom.com (88.214.22.XXX): icmp_seq=85 ttl=61 time=6.93 ms
    64 bytes from 88.214.22.XXX.static.xtom.com (88.214.22.XXX): icmp_seq=86 ttl=61 time=5.98 ms
    64 bytes from 88.214.22.XXX.static.xtom.com (88.214.22.XXX): icmp_seq=87 ttl=61 time=506 ms
    64 bytes from 88.214.22.XXX.static.xtom.com (88.214.22.XXX): icmp_seq=91 ttl=61 time=271 ms
    64 bytes from 88.214.22.XXX.static.xtom.com (88.214.22.XXX): icmp_seq=92 ttl=61 time=0.300 ms
    64 bytes from 88.214.22.XXX.static.xtom.com (88.214.22.XXX): icmp_seq=93 ttl=61 time=9.47 ms
    64 bytes from 88.214.22.XXX.static.xtom.com (88.214.22.XXX): icmp_seq=94 ttl=61 time=1.01 ms
    64 bytes from 88.214.22.XXX.static.xtom.com (88.214.22.XXX): icmp_seq=95 ttl=61 time=7.19 ms
    64 bytes from 88.214.22.XXX.static.xtom.com (88.214.22.XXX): icmp_seq=96 ttl=61 time=0.633 ms
    64 bytes from 88.214.22.XXX.static.xtom.com (88.214.22.XXX): icmp_seq=97 ttl=61 time=0.304 ms
    64 bytes from 88.214.22.XXX.static.xtom.com (88.214.22.XXX): icmp_seq=98 ttl=61 time=0.995 ms
    64 bytes from 88.214.22.XXX.static.xtom.com (88.214.22.XXX): icmp_seq=99 ttl=61 time=0.401 ms
    64 bytes from 88.214.22.XXX.static.xtom.com (88.214.22.XXX): icmp_seq=100 ttl=61 time=3.41 ms
    
    --- XXX.chinkchinkgo.cf ping statistics ---
    100 packets transmitted, 82 received, 18% packet loss, time 99544ms
    rtt min/avg/max/mdev = 0.220/168.996/2549.066/465.240 ms, pipe 3
    ****
    
  • edited June 2022

    @foitin said: The same abusers that are causing skyhigh steal time in Tokyo storage?

    It is due to oversell rather than abuse I suppose. Since the BF specials have the same level of CPU steal time.

    Network issue is the more severe problem for me

  • kzedkzed Member

    @lemoncube said:
    Is it only my vm or the node is acting up?

    My vps has been down for 6 hours now..same node.

  • VirMachVirMach Member, Patron Provider
    edited June 2022

    @Murata_Chink_Best said:

    @foitin said: The same abusers that are causing skyhigh steal time in Tokyo storage?

    It is due to oversell rather than abuse I suppose. Since the BF specials have the same level of CPU steal time.

    Network issue is the more severe problem for me

    Not sure what you're saying we could be overselling here that would cause the problem, I guess CPU is always technically oversold? But compared to all our previous storage nodes and plans and based on the last usage levels when I checked, it's definitely really low CPU usage. Just spikes especially during Asia peak hours since everyone is trying to move data onto it at once. It's just not ideal how they are activating together, nothing that can really be done about it unless we stagger creations over several months.

    We've been transparent about the exact node specifications, but I'll provide it here again and you can decide if you think it's oversold. I'm paraphrasing here so I apologize if a par is not exactly correct.

    16 x 18TB Exos X18 Enterprise HDD
    Broadcom 9460-16i RAID controller w/ CacheVault
    Ryzen 5950X Processor
    4 x 32GB DDR4 3200MHz ECC
    ASRock X570D4U-2L2T Motherboard
    2 x 2TB Gen4 Mushkin NVMe SSD

    12 of the hard drives are on 3 x 4 port SATA to SFF-8643 backplanes, as provided by Silverstone (chassis manufacturer.) 4 of the hard drives are on another custom 4 port SATA to SFF-8643. Four SFF-8643 ports go into RAID controller.

    • Disk is not oversold in any way.
    • RAM is oversold but we discussed this, we just raised it at same price we would have provided just so people can burst, this is based on actual usage levels on existing storage.

    Current usage levels, as of right now:

    54% CPU by users directly
    25% CPU by system/indirect (network, disk, etc.)
    778Mbps network usage
    56% Active memory usage (rest is buffered, cached, unused, etc.)

    So again anything you're experience is most likely related to disk wait depending on when and what you're trying to do while other people are doing it. Even though it's RAID10, it's still HDD.

    Network ends up getting affected negatively by the disk spikes too, and it's probably the cause of the CPU steal as well. Otherwise again users are only using 54% of the CPU directly. The 10Gbps NIC is much more capable in multiple ways other than just the throughput so once that's ready it should improve of course.

    (edit) Oh and it's 173 services on here. Mostly 250GB and 500GB (quantity-wise.) Total 130TB~ disk assigned. Again, disk isn't oversold.

    Thanked by 2Lurkrazy FrankZ
  • VirMachVirMach Member, Patron Provider
    edited June 2022

    @kzed said:

    @lemoncube said:
    Is it only my vm or the node is acting up?

    My vps has been down for 6 hours now..same node.

    It's up, just overloading in a bad way. No emergency phone alert sent since it's been pinging on our end but I assume it's bad enough to where it's nearly unusable, I've been aware for a couple hours, trying to work in network status now since it got worse, I thought initially it would subside. And then taking another look.

    (edit) Overloading isn't related to node being full or anything like that, it looks more like unrelated to direct abuse and potentially CPU software lockup related or zombie processes.

    (edit) Something with the disk, but disk looks healthy from what I could see and none of them went away.

  • VirMachVirMach Member, Patron Provider

    Yeah, can't find anything wrong at all. Little vague clues here and there but essentially it's what I described, some random hung task. No disk, RAM, or CPU hardware errors. Nothing else breaking afterward, just this one thing caused a runaway overloading.

    I assume CPU soft lockup but no messages on that either. Logs didn't break either, it continued, just nothing abnormal logged.

    Node looked perfect before this one event, which by itself also isn't that abnormal. I'll monitor the node throughout the day and ensure it's stable (hopefully.)

  • fanfan Veteran

    On TYOC029 right now, it was fine after the random reboot but gradually degraded ever since.

    Thanked by 1nick_
  • @VirMach Laxa005 is still in fault code?the migrated machine is always offline.

  • clanclan Member
    edited June 2022

    China mobile need help :'( https://ping.pe/149.57.198.49

  • yoursunnyyoursunny Member, IPv6 Advocate

    @clan said:

    China mobile need help :'( https://ping.pe/149.57.198.49

    China Mobile connects all international traffic through Hong Kong.
    Your best bet is getting a server in Singapore, which is well connected from China Mobile Hong Kong.
    Japan and USA are not good for China Mobile.

    Thanked by 2FrankZ tototo
  • clanclan Member

    @yoursunny said:

    @clan said:

    China mobile need help :'( https://ping.pe/149.57.198.49

    China Mobile connects all international traffic through Hong Kong.
    Your best bet is getting a server in Singapore, which is well connected from China Mobile Hong Kong.
    Japan and USA are not good for China Mobile.

    Really? Why does another LA work fine?

  • foitinfoitin Member
    edited June 2022

    @VirMach said:

    Not sure what you're saying we could be overselling here that would cause the problem, I guess CPU is always technically oversold? But compared to all our previous storage nodes and plans and based on the last usage levels when I checked, it's definitely really low CPU usage. Just spikes especially during Asia peak hours since everyone is trying to move data onto it at once. It's just not ideal how they are activating together, nothing that can really be done about it unless we stagger creations over several months.

    I had no problem on the first day and it's becoming worse and worse after massive storage VPS deployment. SSH is choppy even in 2/3 AM JST which is the most off-peak hour in Asia.

    Latency is not a problem for me it's just 4-5ms but the SSH lag is a huge issue.

    Even though it's RAID10, it's still HDD.

    Is it NVMe cached? from fio test result.

    The 10Gbps NIC is much more capable in multiple ways other than just the throughput so once that's ready it should improve of course.

    TYOC002S will receive 10Gbps upgrade after other storage node?

    edit: I'm talking about my storage VPS of course. NVMe one is working fine.

  • jeffsheadjeffshead Member
    edited June 2022

    I’ve been satisfied with the uptime and resource allocation of the VPS service from Virmach since 2019 but the way your organization handled a renewal/cancellation ticked me off enough to cancel all services with Virmach.

    I wasn’t going to renew an unused VPS service that had a renewal date of 5/22. That date was listed in the Virmach billing portal. Without notice, it auto-renewed on 5/19. I submitted a ticket on 5/19 as soon as I saw the charge. No one responded and the ticket was closed. I submitted another ticket and it was marked rejected and no one responded.

    I thought I had until 5/22 to cancel. I didn’t realize it was going to auto-renew 3 days early. I explained this in the tickets, asked for the service to be cancelled and for a refund of the recent charge. What did I get… A closed door in my face! That’s the reason for this public post. What an extremely poor manner in which to run a business.

  • tcwltcwl Member

    TYOC030

  • FrankZFrankZ Barred
    edited June 2022

    Reposting this from a few pages back...

    @FrankZ said:

    Just a note for those that do not know this already.

    1. VirMach sends invoices for yearly plans 30 days before the due date.

    2. If you have account credit, the invoice amount will be deducted from your account credit automatically and the service will be renewed for another year.

    3. If you do not have account credit and you receive an invoice for a service that you end up wanting to cancel, you can cancel the service in the billing panel at least 3 days before the due date and the invoice will be canceled automatically, you will not be charged any late payment fees, and your service will not renew.

    4. If you submit a cancellation request to cancel a yearly service at the end of the billing cycle, more than 30 days before your next renewal date, you will not receive an invoice for that service.

    5. If you cancel a yearly service more than 30 days before your renewal date, and then later change your mind and want to keep the service. You can cancel the cancellation no less then 3 days before the renewal date and you will be invoiced before your service expires and if you pay the invoice promptly the service will renew for another year.

    6. You should pay all invoices for services you wish to keep at least 3 days before the due date.

    NOTE: The 3 days stated in the above are best practices and not hard rules. The billing panel sometimes is unavailable, can be overloaded if there is a flash sale going on, etc. The invoices generate based on cron jobs and this gives you time in case there are unforeseen circumstances so things do not fall through the cracks.
    You may be able to push these limits, but you do so at your own risk.

    And I will add for monthly services:
    1. You must cancel a monthly service in the billing panel more than 3 days before the due date, or else you will be invoiced, and the service will be automatically renewed for another month.
    2. For a monthly service if you set it to cancel at the end of the billing period in the billing panel, you can remove the cancellation if you do so more than 3 days before the due date.
    3. You will need to pay any invoices that you receive for monthly services before the due date to keep your account in good standing and avoid late fees.
    4. If you have an auto payment method set up on your account, or have account credit and you receive an invoice for a service and it is automatically paid via the auto payment method or by account credit, there are no refunds solely for the reason that you did not cancel the service in the billing panel more than 3 days before the end of the billing period.

    Thanked by 1ZA_capetown
  • @FrankZ said:
    Reposting this from a few pages back...

    1. VirMach sends invoices for yearly plans 30 days before the due date.

    2. If you have account credit, the invoice amount will be deducted from your account credit automatically and the service will be renewed for another year.

    I personally do not care for #2. In my opinion if I have account credit it should be deducted on the due date. I keep account credit on there because sometimes things go wrong and I don't want drama but I'm not always thinking two months in advance if I want to keep a machine or not. Or more accurately, I'm thinking about it but I'm also thinking, "I've got two months until that renews," when I actually only have one.

    Thanked by 1foitin
  • VirMachVirMach Member, Patron Provider

    @skorous said:

    @FrankZ said:
    Reposting this from a few pages back...

    1. VirMach sends invoices for yearly plans 30 days before the due date.

    2. If you have account credit, the invoice amount will be deducted from your account credit automatically and the service will be renewed for another year.

    I personally do not care for #2. In my opinion if I have account credit it should be deducted on the due date. I keep account credit on there because sometimes things go wrong and I don't want drama but I'm not always thinking two months in advance if I want to keep a machine or not. Or more accurately, I'm thinking about it but I'm also thinking, "I've got two months until that renews," when I actually only have one.

    This is just how WHMCS does it, we have no customizations on that nor do we agree with how they do their entire credit system, we just try our best to make our policies match the limitations of how the software works.

  • FrankZFrankZ Barred
    edited June 2022

    @skorous said:

    @FrankZ said:
    Reposting this from a few pages back...

    1. VirMach sends invoices for yearly plans 30 days before the due date.

    2. If you have account credit, the invoice amount will be deducted from your account credit automatically and the service will be renewed for another year.

    I personally do not care for #2. In my opinion if I have account credit it should be deducted on the due date. I keep account credit on there because sometimes things go wrong and I don't want drama but I'm not always thinking two months in advance if I want to keep a machine or not. Or more accurately, I'm thinking about it but I'm also thinking, "I've got two months until that renews," when I actually only have one.

    I have removed the WHMCS part of this post as VirMach beat me to it. :)
    But...
    Since I always deposit account credit in advance to pay for soon to renew services in case I have a snafu on my end. I do a #4 on yearly services I am not sure I want to keep. I normally can make that decision within 2 weeks of the due date and do a #5 to remove the cancellation if I decide to keep it. So it's all good. Of course I do understand that there is some risk involved in this practice.

    EDIT: I have one provider that invoices me 45 days in advance of due date on yearly deals.

    Thanked by 1skorous
  • @VirMach pls see ticket #446493

  • @VirMach said:

    This is just how WHMCS does it, we have no customizations on that nor do we agree with how they do their entire credit system, we just try our best to make our policies match the limitations of how the software works.

    Thanks for clarifying that. I'll have to pay attention to some of my other vendors. Maybe I'm the variable here...

  • edited June 2022

    @VirMach said: We've been transparent about the exact node specifications, but I'll provide it here again and you can decide if you think it's oversold. I'm paraphrasing here so I apologize if a par is not exactly correct.

    Sorry for my harsh assumption.

    I wonder the issue won't be solved until migrate to 10Gbps and the majority settles down.

    The high packages loss, Waaagh!!! I will double my outgoing traffic on port 443.

    https://github.com/SiyaChieng/packet-doubler

  • @skorous said:

    @FrankZ said:
    Reposting this from a few pages back...

    1. VirMach sends invoices for yearly plans 30 days before the due date.

    2. If you have account credit, the invoice amount will be deducted from your account credit automatically and the service will be renewed for another year.

    I personally do not care for #2. In my opinion if I have account credit it should be deducted on the due date. I keep account credit on there because sometimes things go wrong and I don't want drama but I'm not always thinking two months in advance if I want to keep a machine or not. Or more accurately, I'm thinking about it but I'm also thinking, "I've got two months until that renews," when I actually only have one.

    The credit system in WHMCS is not how any credit system would work - accounting wise the way it works is completely incorrect and this has been a known issue probably since WHMCS was launched.

    You are right that the credit should be applied to invoices on the due date whereas WHMCS applies the credit on the day the invoice is created which means that if credit is added after that date for whatever reason the credit would never apply automatically to the invoice.

    WHMCS only offers two options for applying credit, either automatically which works as I explained above or just not applying the credit automatically. Both options are useless IMO.

    Thanked by 2FrankZ xpreboun
  • xprebounxpreboun Member
    edited June 2022

    @VirMach Any updates to IPv6 and new PTR rollout?

    I think people are going to hate me again for asking "unrelated" questions.. but here it come:

    @VirMach said: 16 x 18TB Exos X18 Enterprise HDD

    How well do you think that's performed for your machines?
    I have one in my NAS and was debating between Exos X18 18TB or WD drives (for other NAS bay, and for camera) ...

    Also, for port blocks... I'm not a big fan of blocking ports but I do understand it...
    It always plagues me why people would still need port 25 though. You can almost always connect to other servers using Port 587 for outbound, and (I think) if you setup your SMTP-TLS correctly, other servers can also use Port 587 to send emails to your server.

    Thanked by 1FrankZ
  • @VirMach

    Node Name:  ATLZ005
    
    root@virmach:~# tshark -i eth0
    

    There are a lot of arp broadcasts. In the case of no operation, receiving data packets of about 100MiB per hour, there are 100MiB * 24 ≈ 2GiB in one hour, which greatly affects the network quality.

  • @xpreboun said:
    @VirMach Any updates to IPv6 and new PTR rollout?

    I think people are going to hate me again for asking "unrelated" questions.. but here it come:

    @VirMach said: 16 x 18TB Exos X18 Enterprise HDD

    How well do you think that's performed for your machines?
    I have one in my NAS and was debating between Exos X18 18TB or WD drives (for other NAS bay, and for camera) ...

    Not VirMach, but personally I don't buy Seagates anymore. I've had a mostly equal number of failures between WD and Seagate, maybe slightly higher Seagate, but what sealed it for me is the RMA process. The refurb drives that Seagate sends out as RMA replacements seem like they're all garbage, every single one failed in less than a year of use for me. The drives WD sends back haven't given me any more troubles than any other drive in my setup.

    Thanked by 2xpreboun lemoncube
  • drwindrwin Member

    I paid for VPS 4 days ago, still hanging as "pending". Ticket also unanswered 4 days

This discussion has been closed.