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

1130131133135136339

Comments

  • VirMachVirMach Member, Patron Provider

    @keyupai said:

    @VirMach said:
    Update: We're around 67% activated for Tokyo.

    67% include storage services? :|

    Actually, I think yes, but storage is much lower quantity and definitely not ready yet but it's part of the 100%

    Thanked by 1FrankZ
  • VirMachVirMach Member, Patron Provider

    Refunds are being processed now. I noticed some of these already got activated, so if that happens it will default to it being rejected per the terms of the sale. Otherwise it will be processed, so if you want to withdraw it, it's already too late, I've opened them all.

  • On page 92 of the current thread, I see that after activating the service, the system sends a new account to log on to solusvm.virmach.com.

    Will the 2FA of Billing.virmach.com affect my use of the service ?

    If it does not affect, I am willing to continue to wait :smiley: @VirMach

  • I am looking forward to my vps being activated

  • vhhjkglvhhjkgl Member
    edited April 2022

    @VirMach said:
    I'm proceeding with ticket cleanups as promised a few pages back. On top of that, any ticket I view I'll be viewing and making sure no other tickets are opened, otherwise they're being merged and being put at the back of the ticket queue. Anyone who created unnecessary spam tickets (up to me what I consider as that) is also being added to a list of beta testers for our AI ticket system. We're not going to really change the response time or anything like that but you get to speak to an AI until you realize you're speaking to an AI so it keeps you occupied and hopefully you don't spam our system with tickets while you're busy speaking with an AI.

    I can't believe you didn't go to sleep.Worked until now!

  • He works insane long hours. To try and make everyone happy. <3 Virmach

    Thanked by 2VirMach FrankZ
  • taizitaizi Member

    @Such said:

    @VirMach said:
    Important Ticket Update

    We're falling behind on tickets, and it's ballooning even further. Hundreds of requests for personal updates are still being created. The titles are not all that great. There's also many tickets regarding announcements made, such as when SolusVM was down and it was posted as a network issue, when TYOC040 had emergency emails sent out, and tons of misusage of the "report outage" button. Skimming through, the majority of the rest seem to be regarding things like "No CDRom" where people check on SolusVM and see no ISO but do not check service page, or "Missing OS" when they did not even initially install one. Lots of vague titles "Japan" which are mostly asking for updates as previously mentioned but some include various other questions and issues discussed inside so it's difficult to sort. We also have a lot of titles that sound like people were facing billing issues, such as "I paid, but were is my VPS?" which could usually be used to describe a payment issue but then it could just be about the fact that the pre-order is pending. Even more tickets about the Cloudflare timeouts, ratelimits, a lot of tickets about specific kernel panic-related errors where a compatible OS just needs to be installed, and tons of "connection issue" tickets to describe every varying level of high ping, packet loss, server just not configured properly, or even when it's just functioning fine, and with most missing any actual troubleshooting data requested before the ticket is created. Then there's all the custom requests, like specific templates, CPU passthrough, location change requests, package change requests, billing cycle changes, refund requests for store credit, tickets referencing other tickets, duplicates of the same tickets, requesting to buy the expired sale, the usual threats, re-install requests where they want us to do it for them, manual IP change tickets, recreating Tokyo on other nodes, and general complaints. The biggest problem of all seems to be that once the issue is no longer an issue, the majority of people do not close their tickets, so while we focused on mass resolution of issues, it did not bring down the ticket numbers even though it was resolved.

    We cannot realistically answer this volume of tickets, especially with the current state of the website with Cloudflare and lag, and it's more difficult finding the valid tickets inside the quantity of incorrectly created ones, which will only delay us getting to the valid tickets if we continue this way.

    Therefore, all tickets created by people who have special offers or tickets created by people with multiple accounts will be closed.

    I'm skimming through all these tickets before closing them, based on the title only, which is how we usually request people create their tickets (with a descriptive title.) If anyone [A] used a concise title to describe their issue and [B] the issue seems valid and not related to anything we are already fixing on a mass scale or something we specifically requested tickets not to be created for, etc, then I'll open the ticket and provide an answer to those, even after they are closed. It's possible I will miss some.

    For the next 7 days, if you are facing an urgent issue ONLY or want to make a VALID request at this time I recommend creating the ticket, with a very good title, in the priority department. You will not be billed as long as it's one of the valid or urgent issues listed below.

    Valid tickets & urgent issues include:

    • Requesting a refund for a service where you are eligible for a refund. Ensure the word "Refund" is in the ticket title and you clearly state your request.
    • An issue which we are not already fixing, so excluding issues such as "offline" services as a result of the disk issue on TYOC033 and TYOC035, which you absolutely cannot resolve on your end. If external VNC is not functioning/VNC is confirmed broken, or your service cannot power on with the appropriate OS installation (after power off)
    • Reporting a payment made, with transaction ID, for any invoice not marked as "paid" correctly, as in not registered on our system.
    • Any ticket that I specifically told you that you specifically should create, as in I replied to you and only you here and told you to make the ticket.
    • In the rare case that there is a real connection issue stopping you from accessing your service (this is nearly 0% chance) with included MTR only, and after confirmation that you checked VNC for service to be functional, correct firewall settings, and you are essentially 100% sure that the service is online and just not publicly accessible by anyone on the internet, and you cannot physically resolve it on your end.

    Does NOT include:

    • Asking for an update on pre-order service.
    • Asking for an activation of your special offer.
    • Asking for re-installation.
    • Asking for a template/ISO to be added.
    • Asking for rDNS to be added or removed (we cannot process them for Ryzen at this time.)
    • Asking for a refund for store credit deposit.
    • Refund quest when you are not eligible.
    • Asking to migrate locations.
    • Transferring services (we are not processing that at this time.)
    • Reporting any widespread issue without first posting it here and confirming if you should create a ticket for it.
    • Asking to uncancel/un-refund a cancelled and refunded order.
    • Reporting an outage on a Ryzen node. We are aware of all outages on our end and any issue with deployment should be discussed here, we simply can't get to all of them individually right now.
    • Custom ISO request (we are not processing that at this time, use Netboot.)
    • Requesting assistance with making a payment for a special order such as card declined (we cannot assist you in a timely manner, you will unfortunately just not be able to buy the special.)
    • Any pre-order/sales related pre-sales questions
    • Restoring invoice to unpaid (too many people didn't make payments on time, many are already queued for termination. You can assume service will end due to late payment.)
    • Requesting IPv6 (we will automatically assign there or have a button when available.)
    • Locating your service or account if you have multiple accounts (consider not having multiple accounts.)
    • Questions about upcoming migrations (we'll announce it and send emails.)
    • Making any account or service modifications such as changing your email, term changes, upgrades, downgrades, changing service, customizations.
    • Making a ticket asking why your old ticket was closed.
    • Connection issues. We will expect some level of packet loss, slow speeds, etc.
    • Web VNC not functioning (use external.)

    Of course nothing is stopping you from making a ticket, but we will strictly enforce the priority fee for all the above, as in, this is not an invitation to make a priority ticket for the same ticket that was closed. You should only create a priority ticket to ensure that your VALID request is answered at all.

    I'm going to begin closing tickets after answering any questions about the above here, and I'd like to hear your feedback, if you disagree with anything, so we can clarify it before I begin closing these tickets. Let me know if you think I'm forgetting anything extremely important.

    Short version: most tickets created by people with a special offer on their account will be closed, unless it has a good title. If it's urgent, recreate it in the priority ticket department and it will be answered much sooner, and we will not bill you as long as you use common sense (our version of common sense as described above.)

    @taizi > @taizi said:

    I am not the ticket owner, but can I know the real reason of refund ticket got rejected

    his name(in whmcs) is "fdg dhg"

    I can't see the reason why this MJJ got rejected, does he hide something, or staff member really just reject it

    original ticket owner's thread:https://hostloc-com.translate.goog/thread-999843-1-1.html?_x_tr_sl=zh-CN&_x_tr_tl=en&_x_tr_hl=zh-CN&_x_tr_pto=wapp

    but it is rejected, not closed

  • @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

  • Hello, my vps has been suspended for more than 15 hours (node 40), according to you the rebuild is not more than 1 hour, when will it be restored? Thank you.
    @VirMach

  • Fast :)

    root@TYOC039:~# speedtest -s 38241; speedtest -s 21569; speedtest -s 48463
    
       Speedtest by Ookla
    
         Server: BudgetVM - Tokyo (id = 38241)
            ISP: Owl Limited
        Latency:     0.92 ms   (0.11 ms jitter)
       Download:   705.23 Mbps (data used: 1.1 GB )
         Upload:   681.75 Mbps (data used: 681.3 MB )
    Packet Loss:     2.0%
     Result URL: https://www.speedtest.net/result/c/b5839d3d-b90c-4888-921f-7f3ef966d11e
    
       Speedtest by Ookla
    
         Server: i3D.net - Tokyo (id = 21569)
            ISP: Owl Limited
        Latency:     1.28 ms   (0.51 ms jitter)
       Download:   753.15 Mbps (data used: 830.3 MB )
         Upload:   620.12 Mbps (data used: 429.7 MB )
    Packet Loss:     0.6%
     Result URL: https://www.speedtest.net/result/c/b4da84ae-ea39-46d7-8172-190f3df08657
    
       Speedtest by Ookla
    
         Server: IPA CyberLab 400G - Tokyo (id = 48463)
            ISP: Owl Limited
        Latency:     1.92 ms   (1.07 ms jitter)
       Download:   786.12 Mbps (data used: 569.8 MB )
         Upload:   666.81 Mbps (data used: 308.1 MB )
    Packet Loss:     3.5%
     Result URL: https://www.speedtest.net/result/c/a8a475e8-a51f-4e1a-a599-6880b850ce48
    
    Thanked by 1FrankZ
  • VirMachVirMach Member, Patron Provider

    @AltriaPendragon said:
    Hello, my vps has been suspended for more than 15 hours (node 40), according to you the rebuild is not more than 1 hour, when will it be restored? Thank you.
    @VirMach

    I don't know, you provided no information outside of the time and node, it'd be difficult to locate it for certain. Did you create a priority ticket?

  • VirMachVirMach Member, Patron Provider

    @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.

    Thanked by 3nick_ tototo FrankZ
  • VirMachVirMach Member, Patron Provider

    Billing panel accidentally got "attacked" by me doing tickets too quickly. On the admin area it loads a lot of tables so if I open too much of it at once the system doesn't play well sometimes. I've brought it back online, sorry about that.

    I'll also double check and make sure it's not combined with another issue, it usually is if I manage to crash it like that.

  • @VirMach said:
    Billing panel accidentally got "attacked" by me doing tickets too quickly. On the admin area it loads a lot of tables so if I open too much of it at once the system doesn't play well sometimes. I've brought it back online, sorry about that.

    I'll also double check and make sure it's not combined with another issue, it usually is if I manage to crash it like that.

    Hehehe, I think this issue has existed for the last 15 years+ with whmcs.

  • @VirMach said: Billing panel accidentally got "attacked" by me doing tickets too quickly.

    Can't get the staff, these days! :p

  • VirMachVirMach Member, Patron Provider
    edited April 2022

    @zafouhar said: Hehehe, I think this issue has existed for the last 15 years+ with whmcs.

    They definitely made tons of "improvements" going from version 7 to 8, way more than ever. To the point where their solution to everything was telling us to get a larger server, and when I explained to them that they were proposing we essentially 20-50x the server size from version 7 to 8 and that it's not even how it works, you can't just infinitely scale up terrible code, they just shrugged.

    (Of course we didn't listen to them, we did our own optimizations.)

  • pddpdd Member

    @VirMach Hi,my vm on tokyo 039 is constantly downloading something even while idle.I just reinstalled my system several times with different os but the problem still exists!

  • Tokyo 37 seems to be uploading and downloading continuously, 500-600k per second. It seems to be intranet traffic?I don't know.

  • miaumiau Member

    @pdd said:
    @VirMach Hi,my vm on tokyo 039 is constantly downloading something even while idle.I just reinstalled my system several times with different os but the problem still exists!

    Install iftop and see whats going on.

  • VirMachVirMach Member, Patron Provider

    @fineln12 said:

    Tokyo 37 seems to be uploading and downloading continuously, 500-600k per second. It seems to be intranet traffic?I don't know.

    @pdd said:
    @VirMach Hi,my vm on tokyo 039 is constantly downloading something even while idle.I just reinstalled my system several times with different os but the problem still exists!

    Well for you to view it I assume it has to use networking in most cases, and then unless you set up rules to have it only be accessible by you, there are probably people attempting to access it at all times since it's a public IP address. All public IP addresses constantly get scanned by infected computers around the world, and so on. Even if you do lock it down they can still send a request and get rejected which will use up something.

    It shouldn't be a concern, you're not going to run out of bandwidth from that or even close to that.

    Thanked by 1tototo
  • pddpdd Member

    @VirMach said:
    It shouldn't be a concern, you're not going to run out of bandwidth from that or even close to that.

    This small period of time has used 300MB of my broadband, I try the iftop command as suggested and found that it is a Chinese IP(112.48.85.17) that has been communicating, how should I ban it?

  • @pdd said:

    @VirMach said:
    It shouldn't be a concern, you're not going to run out of bandwidth from that or even close to that.

    This small period of time has used 300MB of my broadband, I try the iftop command as suggested and found that it is a Chinese IP(112.48.85.17) that has been communicating, how should I ban it?

    Depends on what OS you are using and if you are using any firewall but this would block the IP on iptables/CentOS for example:

    iptables -A INPUT -s 112.48.85.17 -j DROP

    Thanked by 1FrankZ
  • @VirMach said:

    @AltriaPendragon said:
    Hello, my vps has been suspended for more than 15 hours (node 40), according to you the rebuild is not more than 1 hour, when will it be restored? Thank you.
    @VirMach

    I don't know, you provided no information outside of the time and node, it'd be difficult to locate it for certain. Did you create a priority ticket?

    I did not create tickets, but I can provide invoice #1397106.

  • pddpdd Member
    edited April 2022

    @zafouhar
    Depends on what OS you are using and if you are using any firewall but this would block the IP on iptables/CentOS for example:

    iptables -A INPUT -s 112.48.85.17 -j DROP

    Okay, I'll look into it. Thank you for your patient guidance and wish you a good day!

  • CalypsoCalypso Member
    edited April 2022

    @pdd said:

    @VirMach said:
    It shouldn't be a concern, you're not going to run out of bandwidth from that or even close to that.

    This small period of time has used 300MB of my broadband, I try the iftop command as suggested and found that it is a Chinese IP(112.48.85.17) that has been communicating, how should I ban it?

    Just to be sure... that IP is from China Mobile. How are you connected to your VPS? Isn't it simply your own traffic by being logged into it?

    Just asking, because your question "how do I block" is so elimentary for someone purchasing a Linux VPS with public interface - you might have overlooked the most obvious reason for traffic...

    And if not and you want to block, use a searchengine to look what the most convenient way for your Linux distribution is. If not sure, search for "iptables block ip" or something like that. But be sure it's not your own IP address you're blocking...

    Thanked by 1FrankZ
  • pddpdd Member

    @Calypso said:
    Just to be sure... that IP is from China Mobile. How are you connected to your VPS? Isn't it simply your own traffic by being logged into it?

    Just asking, because your question "how do I block" is so elimentary for someone purchasing a Linux VPS with public interface - you might have overlooked the most obvious reason for traffic...

    And if not and you want to block, use a searchengine to look what the most convenient way for your Linux distribution is. If not sure, search for "iptables block ip" or something like that. But be sure it's not your own IP address you're blocking...

    Of course not! I know my own ip, and that Chinese Fujian ip can't be mine In any possible way. Thanks anyway for your valuable advice

  • miaumiau Member
    edited April 2022

    @pdd said:

    @Calypso said:
    Just to be sure... that IP is from China Mobile. How are you connected to your VPS? Isn't it simply your own traffic by being logged into it?

    Just asking, because your question "how do I block" is so elimentary for someone purchasing a Linux VPS with public interface - you might have overlooked the most obvious reason for traffic...

    And if not and you want to block, use a searchengine to look what the most convenient way for your Linux distribution is. If not sure, search for "iptables block ip" or something like that. But be sure it's not your own IP address you're blocking...

    Of course not! I know my own ip, and that Chinese Fujian ip can't be mine In any possible way. Thanks anyway for your valuable advice

    use iftop -P to show port number.

    then lsof -i :[port number] (for example, lsof -i :443) to show its associated listening process. (Some distro does not have lsof installed by default)
    alternatively use netstat -aentpu and grep the related ip.

    this will give you better picture of what's actually happening.

    Thanked by 2pdd FrankZ
  • MiFen629MiFen629 Member
    edited April 2022

    Hi, you said that servers with two year bills get priority power on and are assigned better processors. But I found that the expiration time of the server has been modified, and the machine is still not powered on. I'm not urging you and I'm not a MJJ user as you say, I just want to know when will the machine be available? @VirMach
    Bill #1400410 Bill #1406090

  • @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...

  • @FrankZ said:

    @VirMach said: Laughs in arrhythmia

    So you literally sell a VPS for a year for less then a cup of coffee. :sunglasses:

    EDIT: It took more then 643 pre-sale 384MB VPSes to pay for your yearly coffee overhead.

    get a room guys ✌️🤪> @VirMach said:

    Update: We're around 67% activated for Tokyo.

    great. got target date to activate the rest (33%)? thanks

This discussion has been closed.