@VirMach said: @derekyang said: I am curious why ask customer to provide invoice number since the billing system have all information needed? i believe there is automated way to do this rather have exchange through the ticket as it's most hated by Virmach. i don't understand the logic here.
Workload. We're not going to go back and manually check whether or not it was a paid or unpaid request and then match it to specific invoices especially since on most of these accounts the migrate button was spammed over and over and over and over so there's lots of generated tickets and invoices.
Alternative would be for this batch to just send everyone a mass notice that there's no option for renewal and service is ending on next due date, or to not offer any refund since in almost all these cases the customer's support usage or AUP breach carries more fees than the migration. For other future batches, maybe that's different and we'll consider being more accommodating when it comes to locating and refunding migration fees without user input.
Anyway, I think I've said all I want to say here. I can't continue replying to everyone's concerns regarding this matter. The cancellation button is still there and it's definitely no hard feelings on our end if it's utilized. We're taking the minimal action in this case as necessary.
Thanks for the reply,
Totally not a concerns but just curious about the logic here as i see you are more prefer ticket-free business from my opinion. anyway in the end it's your business model as an company.
@VirMach said: It's first focused on people that might also do something like come on here tagging me making accusations and general increased support strain on a limited support service, or replying back to the ticket asking if a custom arrangement can be made in their case, and then also copy/pasting a similar message here after replying to the ticket.
I didn't do any accusation, or relied to any ticket, or intensionally increased your work load. how come I am asked to leave Tokyo?
VirMach said: It's first focused on people that might also do something like come on here tagging me making accusations and general increased support strain on a limited support service, or replying back to the ticket asking if a custom arrangement can be made in their case, and then also copy/pasting a similar message here after replying to the ticket.
I didn't do any accusation, or relied to any ticket, or intensionally increased your work load. how come I am asked to leave Tokyo?
VirMach said: It's first focused on people that might also do something like come on here tagging me making accusations and general increased support strain on a limited support service, or replying back to the ticket asking if a custom arrangement can be made in their case, and then also copy/pasting a similar message here after replying to the ticket.
I didn't do any accusation, or relied to any ticket, or intensionally increased your work load. how come I am asked to leave Tokyo?
Double down much ?
there is no way to go, I don't want to leave Tokyo, this is the only way to communicate with Virmach, do you have better suggestions?
I've tagged virmach here only to add an IPv6. Virmach provided the IPV6 button and I pressed the button, and it generated a ticket, I leave it open without replying for 6 months, then I started to tag him here. but he only replied me once saying no IPv6 currently, then I said how about pay to add one, that's all it's about.
besides that, I never filed any ticket or relied to any.
Now Virmach seems to blame me for adding his work load by tagging him here. It makes no sense.
VirMach said: It's first focused on people that might also do something like come on here tagging me making accusations and general increased support strain on a limited support service, or replying back to the ticket asking if a custom arrangement can be made in their case, and then also copy/pasting a similar message here after replying to the ticket.
I didn't do any accusation, or relied to any ticket, or intensionally increased your work load. how come I am asked to leave Tokyo?
Double down much ?
there is no way to go, I don't want to leave Tokyo, this is the only way to communicate with Virmach, do you have better suggestions?
I expect you are being moved from Tokyo to another location. I do not think that will change no matter how much you comment here, or via ticket. You should already know that from your attempt to get IPv6 on your Tokyo VM as I outlined below. My suggestion would be to find a different provider that offers service in Tokyo with Ipv6. Just my two cents.
Comment by ripeapple October 11 @VirMach Is it possible to pay a setup fee (like 5 dollars) to add an IPV6 for Tokyo?
Comment by ripeapple July 24
(Quote) sir, can you unofficially assign an ipv6 for me?
Comment by ripeapple July 22 @VirMach why my ticket regarding adding ipv6 being open for 6 months, you said to add it to the list..when?
Comment by ripeapple June 19 @VirMach , hello, how is the IPV6 of Tokyo location going on?
Comment by ripeapple February 18 @VirMach sir, I used the request IPV6 button and it generated a ticket, now your colleague closed the ticket without giving ipv6, Can I open a new ticket regarding this?
Comment by ripeapple January 29 @VirMach sir, how is the ipv6 for Tokyo?
i
VirMach said: It's first focused on people that might also do something like come on here tagging me making accusations and general increased support strain on a limited support service, or replying back to the ticket asking if a custom arrangement can be made in their case, and then also copy/pasting a similar message here after replying to the ticket.
I didn't do any accusation, or relied to any ticket, or intensionally increased your work load. how come I am asked to leave Tokyo?
Double down much ?
there is no way to go, I don't want to leave Tokyo, this is the only way to communicate with Virmach, do you have better suggestions?
I expect you are being moved from Tokyo to another location. I do not think that will change no matter how much you comment here, or via ticket. You should already know that from your attempt to get IPv6 on your Tokyo VM as I outlined below. My suggestion would be to find a different provider that offers service in Tokyo with Ipv6. Just my two cents.
Comment by ripeapple October 11 @VirMach Is it possible to pay a setup fee (like 5 dollars) to add an IPV6 for Tokyo?
Comment by ripeapple July 24
(Quote) sir, can you unofficially assign an ipv6 for me?
Comment by ripeapple July 22 @VirMach why my ticket regarding adding ipv6 being open for 6 months, you said to add it to the list..when?
Comment by ripeapple June 19 @VirMach , hello, how is the IPV6 of Tokyo location going on?
Comment by ripeapple February 18 @VirMach sir, I used the request IPV6 button and it generated a ticket, now your colleague closed the ticket without giving ipv6, Can I open a new ticket regarding this?
Comment by ripeapple January 29 @VirMach sir, how is the ipv6 for Tokyo?
i
yeah, it's a bit frustrating to accept it.
for Virmach, if you don't have plan to add ipv6, don't add the button. if you don't wanna be tagged, say it.
if you wanna move people, just do it, don't give unconvincible excuse.
@ripeapple For me it breaks down like this:
~50% of the time I get what I want, when I want it.
~25% of the time I get what I wanted, but not when I wanted it, or when I need it.
~25% of the time I don't get what I want, and I know I will never get it.
Learning to be OK with those numbers kept me from getting ulcers, or a heart attack, in my 50's and so far in my 60's. (Knock wood.) This is probably why you will seldomly see me get upset about anything regarding as small a thing in life as a VPS. Better that the small things fall into the bottom 50% than the big things.
Just saying.
VirMach said: It's first focused on people that might also do something like come on here tagging me making accusations and general increased support strain on a limited support service, or replying back to the ticket asking if a custom arrangement can be made in their case, and then also copy/pasting a similar message here after replying to the ticket.
I didn't do any accusation, or relied to any ticket, or intensionally increased your work load. how come I am asked to leave Tokyo?
Double down much ?
there is no way to go, I don't want to leave Tokyo, this is the only way to communicate with Virmach, do you have better suggestions?
I expect you are being moved from Tokyo to another location. I do not think that will change no matter how much you comment here, or via ticket. You should already know that from your attempt to get IPv6 on your Tokyo VM as I outlined below. My suggestion would be to find a different provider that offers service in Tokyo with Ipv6. Just my two cents.
Comment by ripeapple October 11 @VirMach Is it possible to pay a setup fee (like 5 dollars) to add an IPV6 for Tokyo?
Comment by ripeapple July 24
(Quote) sir, can you unofficially assign an ipv6 for me?
Comment by ripeapple July 22 @VirMach why my ticket regarding adding ipv6 being open for 6 months, you said to add it to the list..when?
Comment by ripeapple June 19 @VirMach , hello, how is the IPV6 of Tokyo location going on?
Comment by ripeapple February 18 @VirMach sir, I used the request IPV6 button and it generated a ticket, now your colleague closed the ticket without giving ipv6, Can I open a new ticket regarding this?
Comment by ripeapple January 29 @VirMach sir, how is the ipv6 for Tokyo?
i
yeah, it's a bit frustrating to accept it.
for Virmach, if you don't have plan to add ipv6, don't add the button. if you don't wanna be tagged, say it.
if you wanna move people, just do it, don't give unconvincible excuse.
you can choose not to buy. then no need to deal with such unhappiness.
@FrankZ said: @ripeapple For me it breaks down like this:
~50% of the time I get what I want, when I want it.
~25% of the time I get what I wanted, but not when I wanted it, or when I need it.
~25% of the time I don't get what I want, and I know I will never get it.
Learning to be OK with those numbers kept me from getting ulcers, or a heart attack, in my 50's and so far in my 60's. (Knock wood.) This is probably why you will seldomly see me get upset about anything regarding as small a thing in life as a VPS. Better that the small things fall into the bottom 50% than the big things.
Just saying.
thanks, you are right, there is way more lot to do in life than messing with suckers like virmach
have a good day.
Based on the quantity statistics from the email notification, it is expected that at least 60% or more of the non-Tokyo native VPS servers will be repatriated.
@ben said:
Based on the quantity statistics from the email notification, it is expected that at least 60% or more of the non-Tokyo native VPS servers will be repatriated.
Closer to 47% but yes, it turns out a good chunk of the accounts that were moved to Tokyo are also flagged in some way for creating too many non-essential tickets or continuing to have multiple accounts/resold, or whatever else I mentioned was in the criteria.
I know I originally also said under 5% of all Tokyo but this number ended up being higher after I finished the last few nodes which had a larger quantity of these on them, and I was going based off total spaces originally available in Tokyo but they're no longer filled in this way so it's closer to 11% of all of Tokyo once I put everything in more specifically on a spreadsheet and finished sending out all the tickets.
@soj1 said: hello.The ip segment 193.151.183.0/24 has 10% network packet loss. Chicago
Whatever it was I can't locate it more specifically since it happened for such a short period of time. If it keeps happening, let me know exact timestamps and timezone. This is what it looks like right now.
[1] - a lot means... idk - sometimes once a day, sometimes 3 times a day, sometimes it's quiet for a few days.
This looks like sessions reset or something like that and they are (most of the times) restablished before next HT check next minute and it's fucking hard to even catch it and do some debugging
Asking if this is "my issue" and just somehow I replicated it on 2-3 servers or this is something xTom/VirMach bad
Haven't bought a single service in VirMach Great Ryzen 2022 - 2023 Flash Sale.
Debian 12 template added. Debian 11 template re-added and resyncing, this one worked partially in the past but I've resynced the configuration and hopefully no more weird issues but if they persist let me know.
I've also gone through and tested some old templates and may re-introduce them as EOL templates because I think it'll be helpful versus people installing old ISOs improperly, especially on low memory older services.
Custom ISO feature is pretty much exclusively being misused right now, with the #1 request being blank, #2 request being an existing ISO, and #3 being dead links or non-ISO links. We're going to kind of phase this out into "request ISO to be added" instead and/or "report problem with ISO."
rDNS has been added in SolusVM for all new blocks, but I've seen reports of it not working. I haven't had time to go through these specifically so it'd be helpful if we can get anyone here to use the feature and let me know what you're seeing in terms of issues and on which node so we can see if it's just all broken or clusters of problems.
Added a paste button to VNC and improved visibility of text as well as some general instructions on failure.
rDNS has been added in SolusVM for all new blocks, but I've seen reports of it not working. I haven't had time to go through these specifically so it'd be helpful if we can get anyone here to use the feature and let me know what you're seeing in terms of issues and on which node so we can see if it's just all broken or clusters of problems.
Not sure if this counts as a "new block" or not, but I just tried setting rDNS on node RYZE.CHI-Z001.VMS with a 193.151.183.xx address. I received a "Could not connect to DNS server. Please try again later" error message.
Really excited to get those Dallas servers racked and online in ATL this week, too!
@VirMach said: Added ChatGPT button on VNC, work in progress.
Update:
It now actually keeps track of previous messages to some degree.
@JBB said: Not sure if this counts as a "new block" or not, but I just tried setting rDNS on node RYZE.CHI-Z001.VMS with a 193.151.183.xx address. I received a "Could not connect to DNS server. Please try again later" error message.
@VirMach said: Debian 12 template added. Debian 11 template re-added and resyncing, this one worked partially in the past but I've resynced the configuration and hopefully no more weird issues but if they persist let me know.
Just installed debian 12 on FFME007.VIRM.AC - waited 10 minutes as requested for install to complete then
apt-get update
apt-get install sshfs
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following additional packages will be installed:
fuse3 libfuse3-3
The following NEW packages will be installed:
fuse3 libfuse3-3 sshfs
0 upgraded, 3 newly installed, 0 to remove and 56 not upgraded.
Need to get 170 kB of archives.
After this operation, 540 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://deb.debian.org/debian bookworm/main amd64 libfuse3-3 amd64 3.14.0-4 [88.1 kB]
Get:2 http://deb.debian.org/debian bookworm/main amd64 fuse3 amd64 3.14.0-4 [35.9 kB]
Get:3 http://deb.debian.org/debian bookworm/main amd64 sshfs amd64 3.7.3-1.1 [45.6 kB]
Fetched 170 kB in 0s (2,075 kB/s) Segmentation fault
E: Sub-process /usr/bin/apt-listchanges --apt || test $? -lt 10 returned an error code (1)
E: Failure running script /usr/bin/apt-listchanges --apt || test $? -lt 10
Anyone have suggestions?
Reverted to deb 11 for now.
It now actually keeps track of previous messages to some degree.
Update:
User chat bubbles added as well. Added loading animation, close button.
@JBB said: Not sure if this counts as a "new block" or not, but I just tried setting rDNS on node RYZE.CHI-Z001.VMS with a 193.151.183.xx address. I received a "Could not connect to DNS server. Please try again later" error message.
@VirMach said: Debian 12 template added. Debian 11 template re-added and resyncing, this one worked partially in the past but I've resynced the configuration and hopefully no more weird issues but if they persist let me know.
Just installed debian 12 on FFME007.VIRM.AC - waited 10 minutes as requested for install to complete then
apt-get update
apt-get install sshfs
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following additional packages will be installed:
fuse3 libfuse3-3
The following NEW packages will be installed:
fuse3 libfuse3-3 sshfs
0 upgraded, 3 newly installed, 0 to remove and 56 not upgraded.
Need to get 170 kB of archives.
After this operation, 540 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://deb.debian.org/debian bookworm/main amd64 libfuse3-3 amd64 3.14.0-4 [88.1 kB]
Get:2 http://deb.debian.org/debian bookworm/main amd64 fuse3 amd64 3.14.0-4 [35.9 kB]
Get:3 http://deb.debian.org/debian bookworm/main amd64 sshfs amd64 3.7.3-1.1 [45.6 kB]
Fetched 170 kB in 0s (2,075 kB/s) Segmentation fault
E: Sub-process /usr/bin/apt-listchanges --apt || test $? -lt 10 returned an error code (1)
E: Failure running script /usr/bin/apt-listchanges --apt || test $? -lt 10
Anyone have suggestions?
Reverted to deb 11 for now.
Sounds like a familiar issue we had before. I'll have to see if it only occurs on certain nodes or all of them, I only did basic testing and didn't run any updates. How much memory do you have?
This is page I am welcomed (for last few days, however I didn't login earlier for like a week) after providing correct TOTP clicking "Back to homepage" logs me in successfully, but this was kinda scary for first time.
I can confirm the same thing happening on TPAZ003.VIRM.AC
root@osm-Replacement:~# apt-get update && apt-get install sshfs
Get:1 http://security.debian.org/debian-security bookworm-security InRelease [48.0 kB]
Get:2 http://deb.debian.org/debian bookworm InRelease [151 kB]
(....)
Get:16 http://deb.debian.org/debian bookworm-updates/main amd64 Packages [6,408 B]
Get:17 http://deb.debian.org/debian bookworm-updates/main Translation-en [5,008 B]
Fetched 24.8 MB in 2s (11.8 MB/s)
Reading package lists... Done
N: Repository 'http://deb.debian.org/debian bookworm InRelease' changed its 'Version' value from '12.0' to '12.2'
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following additional packages will be installed:
fuse3 libfuse3-3
The following NEW packages will be installed:
fuse3 libfuse3-3 sshfs
0 upgraded, 3 newly installed, 0 to remove and 56 not upgraded.
Need to get 170 kB of archives.
After this operation, 540 kB of additional disk space will be used.
Do you want to continue? [Y/n] Y
Get:1 http://deb.debian.org/debian bookworm/main amd64 libfuse3-3 amd64 3.14.0-4 [88.1 kB]
Get:2 http://deb.debian.org/debian bookworm/main amd64 fuse3 amd64 3.14.0-4 [35.9 kB]
Get:3 http://deb.debian.org/debian bookworm/main amd64 sshfs amd64 3.7.3-1.1 [45.6 kB]
Fetched 170 kB in 0s (1,072 kB/s)
Segmentation fault
E: Sub-process /usr/bin/apt-listchanges --apt || test $? -lt 10 returned an error code (1)
E: Failure running script /usr/bin/apt-listchanges --apt || test $? -lt 10
root@osm-Replacement:~# free -m
total used free shared buff/cache available
Mem: 961 192 606 1 299 768
Swap: 255 0 255
Haven't bought a single service in VirMach Great Ryzen 2022 - 2023 Flash Sale.
@VirMach thank you for keeping this thread updated. I had a VPS in SEA005 which after couple of months of downtime is finally up at LAX1Z012, but I am missing two ip4 from the network. Also, I thought based on what I read these are eventually moving to San Jose is that correct? Or do I request that via ticketing system? Do I wait for 2 missing ip4 to appear magically in sometime as you are working through or should raise ticket? Thanks again.
@xyz said: @VirMach thank you for keeping this thread updated. I had a VPS in SEA005 which after couple of months of downtime is finally up at LAX1Z012, but I am missing two ip4 from the network. Also, I thought based on what I read these are eventually moving to San Jose is that correct? Or do I request that via ticketing system? Do I wait for 2 missing ip4 to appear magically in sometime as you are working through or should raise ticket? Thanks again.
If you didn't get your additional it means at the time it was fixed there were none left so it had to be done that way. Maybe a dozen or so people affected if I recall correctly. Wait a little bit so we have extra IPs available and contact us, or if you need it immediately then feel free to contact us sooner but let us know we can move you anywhere with available IPs.
@xTom said: We have PNI with Cloudflare in Frankfurt, we didn't receive any other reports from other customers.
Thanks for answer, I guess then it's something VirMach related as the same Debian packages/version running on other hosts don't drop Cloudflared/Argo tunnel that many times.
Dear @VirMach should the network in Frankfurt look like that? I know jackshit how this should be, but getting 1-97 ms icmp ping from gateway is not good, right?
# ip -4 r s | grep "default"
default via 213.232.115.1 dev ens3 proto dhcp src 213.232.115.X metric 100
# ping 213.232.115.1
PING 213.232.115.1 (213.232.115.1) 56(84) bytes of data.
64 bytes from 213.232.115.1: icmp_seq=1 ttl=64 time=1.27 ms
64 bytes from 213.232.115.1: icmp_seq=2 ttl=64 time=22.4 ms
64 bytes from 213.232.115.1: icmp_seq=3 ttl=64 time=8.10 ms
64 bytes from 213.232.115.1: icmp_seq=4 ttl=64 time=8.46 ms
64 bytes from 213.232.115.1: icmp_seq=5 ttl=64 time=28.3 ms
64 bytes from 213.232.115.1: icmp_seq=6 ttl=64 time=21.5 ms
64 bytes from 213.232.115.1: icmp_seq=7 ttl=64 time=7.74 ms
64 bytes from 213.232.115.1: icmp_seq=8 ttl=64 time=8.19 ms
64 bytes from 213.232.115.1: icmp_seq=9 ttl=64 time=5.82 ms
64 bytes from 213.232.115.1: icmp_seq=10 ttl=64 time=30.2 ms
64 bytes from 213.232.115.1: icmp_seq=11 ttl=64 time=6.61 ms
64 bytes from 213.232.115.1: icmp_seq=12 ttl=64 time=2.38 ms
64 bytes from 213.232.115.1: icmp_seq=13 ttl=64 time=2.31 ms
64 bytes from 213.232.115.1: icmp_seq=14 ttl=64 time=1.02 ms
64 bytes from 213.232.115.1: icmp_seq=15 ttl=64 time=32.8 ms
64 bytes from 213.232.115.1: icmp_seq=16 ttl=64 time=60.1 ms
64 bytes from 213.232.115.1: icmp_seq=17 ttl=64 time=4.55 ms
64 bytes from 213.232.115.1: icmp_seq=18 ttl=64 time=6.74 ms
64 bytes from 213.232.115.1: icmp_seq=19 ttl=64 time=40.1 ms
64 bytes from 213.232.115.1: icmp_seq=20 ttl=64 time=2.35 ms
64 bytes from 213.232.115.1: icmp_seq=21 ttl=64 time=8.35 ms
64 bytes from 213.232.115.1: icmp_seq=22 ttl=64 time=2.29 ms
64 bytes from 213.232.115.1: icmp_seq=23 ttl=64 time=42.5 ms
64 bytes from 213.232.115.1: icmp_seq=24 ttl=64 time=2.44 ms
64 bytes from 213.232.115.1: icmp_seq=25 ttl=64 time=5.41 ms
64 bytes from 213.232.115.1: icmp_seq=26 ttl=64 time=1.08 ms
64 bytes from 213.232.115.1: icmp_seq=27 ttl=64 time=2.41 ms
64 bytes from 213.232.115.1: icmp_seq=28 ttl=64 time=77.2 ms
64 bytes from 213.232.115.1: icmp_seq=29 ttl=64 time=3.92 ms
64 bytes from 213.232.115.1: icmp_seq=30 ttl=64 time=1.31 ms
64 bytes from 213.232.115.1: icmp_seq=31 ttl=64 time=21.9 ms
64 bytes from 213.232.115.1: icmp_seq=32 ttl=64 time=51.1 ms
64 bytes from 213.232.115.1: icmp_seq=33 ttl=64 time=3.41 ms
64 bytes from 213.232.115.1: icmp_seq=34 ttl=64 time=8.07 ms
64 bytes from 213.232.115.1: icmp_seq=35 ttl=64 time=8.30 ms
64 bytes from 213.232.115.1: icmp_seq=36 ttl=64 time=97.9 ms
64 bytes from 213.232.115.1: icmp_seq=37 ttl=64 time=3.61 ms
64 bytes from 213.232.115.1: icmp_seq=38 ttl=64 time=5.39 ms
64 bytes from 213.232.115.1: icmp_seq=39 ttl=64 time=8.02 ms
64 bytes from 213.232.115.1: icmp_seq=40 ttl=64 time=1.94 ms
64 bytes from 213.232.115.1: icmp_seq=41 ttl=64 time=49.6 ms
64 bytes from 213.232.115.1: icmp_seq=42 ttl=64 time=2.17 ms
64 bytes from 213.232.115.1: icmp_seq=43 ttl=64 time=9.16 ms
64 bytes from 213.232.115.1: icmp_seq=44 ttl=64 time=1.07 ms
64 bytes from 213.232.115.1: icmp_seq=45 ttl=64 time=2.32 ms
64 bytes from 213.232.115.1: icmp_seq=46 ttl=64 time=22.4 ms
64 bytes from 213.232.115.1: icmp_seq=47 ttl=64 time=2.19 ms
^C
--- 213.232.115.1 ping statistics ---
47 packets transmitted, 47 received, 0% packet loss, time 46068ms
rtt min/avg/max/mdev = 1.020/15.883/97.910/21.362 ms
Okey, I am even more confused - seems like there are Google DNS route pushed within DHCP as the same route...
# ip -4 r s | grep "8.8"
8.8.4.4 via 213.232.115.1 dev ens3 proto dhcp src 213.232.115.X metric 10
8.8.8.8 via 213.232.115.1 dev ens3 proto dhcp src 213.232.115.X metric 100
# ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=61 time=0.533 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=61 time=0.732 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=61 time=0.979 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=61 time=0.879 ms
64 bytes from 8.8.8.8: icmp_seq=5 ttl=61 time=0.579 ms
64 bytes from 8.8.8.8: icmp_seq=6 ttl=61 time=0.558 ms
64 bytes from 8.8.8.8: icmp_seq=7 ttl=61 time=0.568 ms
64 bytes from 8.8.8.8: icmp_seq=8 ttl=61 time=0.662 ms
64 bytes from 8.8.8.8: icmp_seq=9 ttl=61 time=0.776 ms
64 bytes from 8.8.8.8: icmp_seq=10 ttl=61 time=0.890 ms
64 bytes from 8.8.8.8: icmp_seq=11 ttl=61 time=0.658 ms
64 bytes from 8.8.8.8: icmp_seq=12 ttl=61 time=0.746 ms
64 bytes from 8.8.8.8: icmp_seq=13 ttl=61 time=0.591 ms
64 bytes from 8.8.8.8: icmp_seq=14 ttl=61 time=0.569 ms
64 bytes from 8.8.8.8: icmp_seq=15 ttl=61 time=0.719 ms
64 bytes from 8.8.8.8: icmp_seq=16 ttl=61 time=0.493 ms
64 bytes from 8.8.8.8: icmp_seq=17 ttl=61 time=0.673 ms
64 bytes from 8.8.8.8: icmp_seq=18 ttl=61 time=0.836 ms
64 bytes from 8.8.8.8: icmp_seq=19 ttl=61 time=0.544 ms
64 bytes from 8.8.8.8: icmp_seq=20 ttl=61 time=0.814 ms
64 bytes from 8.8.8.8: icmp_seq=21 ttl=61 time=0.680 ms
64 bytes from 8.8.8.8: icmp_seq=22 ttl=61 time=0.781 ms
64 bytes from 8.8.8.8: icmp_seq=23 ttl=61 time=0.625 ms
64 bytes from 8.8.8.8: icmp_seq=24 ttl=61 time=0.730 ms
64 bytes from 8.8.8.8: icmp_seq=25 ttl=61 time=0.770 ms
64 bytes from 8.8.8.8: icmp_seq=26 ttl=61 time=0.825 ms
64 bytes from 8.8.8.8: icmp_seq=27 ttl=61 time=0.507 ms
64 bytes from 8.8.8.8: icmp_seq=28 ttl=61 time=0.704 ms
64 bytes from 8.8.8.8: icmp_seq=29 ttl=61 time=0.672 ms
64 bytes from 8.8.8.8: icmp_seq=30 ttl=61 time=0.866 ms
64 bytes from 8.8.8.8: icmp_seq=31 ttl=61 time=0.783 ms
64 bytes from 8.8.8.8: icmp_seq=32 ttl=61 time=0.686 ms
64 bytes from 8.8.8.8: icmp_seq=33 ttl=61 time=0.627 ms
64 bytes from 8.8.8.8: icmp_seq=34 ttl=61 time=0.659 ms
^C
--- 8.8.8.8 ping statistics ---
34 packets transmitted, 34 received, 0% packet loss, time 33747ms
rtt min/avg/max/mdev = 0.493/0.697/0.979/0.118 ms
and those has proper LAN timings - less than 1ms?
Haven't bought a single service in VirMach Great Ryzen 2022 - 2023 Flash Sale.
rDNS has been added in SolusVM for all new blocks, but I've seen reports of it not working. I haven't had time to go through these specifically so it'd be helpful if we can get anyone here to use the feature and let me know what you're seeing in terms of issues and on which node so we can see if it's just all broken or clusters of problems.
Receiving "Could not connect to DNS server. Please try again later" for NY server in ip range 141.11.22x.xxx
also, installed Debian 12 on RYZE.NYC-B013.VMS VM and I'm getting a segfault when I run apt upgrade. (not happening with other templates --- so I assume its a problem with the template.)
@JoeMerit said: also, installed Debian 12 on RYZE.NYC-B013.VMS VM and I'm getting a segfault when I run apt upgrade. (not happening with other templates --- so I assume its a problem with the template.)
This feels like dejavu. We added Debian 12 in the past and it had the same problem, didn't it? And then we removed it because we had to work on our own version not from SolusVM, that never happened, I forgot, and we went back to adding the SolusVM version that's still broken.
@FrankZ said: Could not connect to DNS server. Please try again later
Yeah I forgot an important step for all these, I have to go one by one mapping them to specific primary ID for each as they were added to PowerDNS. SolusVM feature, because it'd be impossible to do it any other way that's less labor intensive.
@imok said:
Why the $30 setup fee for Tokyo VPSes?
Is it a good location for a VPN to connect from China?
We still get a good number of purchases, it helps balance out stock levels, and balance out abuse. Will likely be changed again as we usually do based on other factors.
@imok said:
Given $30 are too expensive, any other recommended location to set up a private VPN?
From China or anywhere?
If anywhere, just select the nearest location to you.
From China, usually what I've seen people do is in the order:
Tokyo
Hong Kong
Vietnam (Greencloud)
Singapore
US West Los Angeles
US West Seattle
@imok said:
Given $30 are too expensive, any other recommended location to set up a private VPN?
Novosibirsk, Russia
Test IP: 91.188.223.6
I really wanted to do this location a while back as I was looking at all the global routes and thought it'd be an interesting location, but then it was definitely complicated after 2022.
@imok said:
Given $30 are too expensive, any other recommended location to set up a private VPN?
Novosibirsk, Russia
Test IP: 91.188.223.6
I really wanted to do this location a while back as I was looking at all the global routes and thought it'd be an interesting location, but then it was definitely complicated after 2022.
hey, there are no forever friends nor enemies. russia will be back in one way or another.
Comments
Thanks for the reply,
Totally not a concerns but just curious about the logic here as i see you are more prefer ticket-free business from my opinion. anyway in the end it's your business model as an company.
I didn't do any accusation, or relied to any ticket, or intensionally increased your work load. how come I am asked to leave Tokyo?
Double down much ?
there is no way to go, I don't want to leave Tokyo, this is the only way to communicate with Virmach, do you have better suggestions?
I've tagged virmach here only to add an IPv6. Virmach provided the IPV6 button and I pressed the button, and it generated a ticket, I leave it open without replying for 6 months, then I started to tag him here. but he only replied me once saying no IPv6 currently, then I said how about pay to add one, that's all it's about.
besides that, I never filed any ticket or relied to any.
Now Virmach seems to blame me for adding his work load by tagging him here. It makes no sense.
$30 setup fee for a server in Japan
I expect you are being moved from Tokyo to another location. I do not think that will change no matter how much you comment here, or via ticket. You should already know that from your attempt to get IPv6 on your Tokyo VM as I outlined below. My suggestion would be to find a different provider that offers service in Tokyo with Ipv6. Just my two cents.
Hi @imok, how's life down south ?
yeah, it's a bit frustrating to accept it.
for Virmach, if you don't have plan to add ipv6, don't add the button. if you don't wanna be tagged, say it.
if you wanna move people, just do it, don't give unconvincible excuse.
@ripeapple For me it breaks down like this:
~50% of the time I get what I want, when I want it.
~25% of the time I get what I wanted, but not when I wanted it, or when I need it.
~25% of the time I don't get what I want, and I know I will never get it.
Learning to be OK with those numbers kept me from getting ulcers, or a heart attack, in my 50's and so far in my 60's. (Knock wood.) This is probably why you will seldomly see me get upset about anything regarding as small a thing in life as a VPS. Better that the small things fall into the bottom 50% than the big things.
Just saying.
you can choose not to buy. then no need to deal with such unhappiness.
I bench YABS 24/7/365 unless it's a leap year.
thanks, you are right, there is way more lot to do in life than messing with suckers like virmach
have a good day.
I will
Well generally for "limited support" services, yes, it'd be preferable that it be limited.
True, it's fair
Based on the quantity statistics from the email notification, it is expected that at least 60% or more of the non-Tokyo native VPS servers will be repatriated.
hello.The ip segment 193.151.183.0/24 has 10% network packet loss. Chicago
Closer to 47% but yes, it turns out a good chunk of the accounts that were moved to Tokyo are also flagged in some way for creating too many non-essential tickets or continuing to have multiple accounts/resold, or whatever else I mentioned was in the criteria.
I know I originally also said under 5% of all Tokyo but this number ended up being higher after I finished the last few nodes which had a larger quantity of these on them, and I was going based off total spaces originally available in Tokyo but they're no longer filled in this way so it's closer to 11% of all of Tokyo once I put everything in more specifically on a spreadsheet and finished sending out all the tickets.
Whatever it was I can't locate it more specifically since it happened for such a short period of time. If it keeps happening, let me know exact timestamps and timezone. This is what it looks like right now.
Restock 47%
Is anyone web-hosting anything in Frankfurt via Cloudflare and see "a lot"[1] of 523?
or anyone have Argo/Tunnel?
[1] - a lot means... idk - sometimes once a day, sometimes 3 times a day, sometimes it's quiet for a few days.
This looks like sessions reset or something like that and they are (most of the times) restablished before next HT check next minute and it's fucking hard to even catch it and do some debugging
Asking if this is "my issue" and just somehow I replicated it on 2-3 servers or this is something xTom/VirMach bad
Haven't bought a single service in VirMach Great Ryzen 2022 - 2023 Flash Sale.
We have PNI with Cloudflare in Frankfurt, we didn't receive any other reports from other customers.
█ xTom - https://xtom.com/ - Global Dedicated Servers, Colocation and IP Transit. | Subscribe our newsletter
█ V.PS - https://v.ps/ - Global VPS Hosting. | Mastodon @[email protected] | @[email protected]
Thanks, Boss man.
My pleasure.
█ xTom - https://xtom.com/ - Global Dedicated Servers, Colocation and IP Transit. | Subscribe our newsletter
█ V.PS - https://v.ps/ - Global VPS Hosting. | Mastodon @[email protected] | @[email protected]
Debian 12 template added. Debian 11 template re-added and resyncing, this one worked partially in the past but I've resynced the configuration and hopefully no more weird issues but if they persist let me know.
I've also gone through and tested some old templates and may re-introduce them as EOL templates because I think it'll be helpful versus people installing old ISOs improperly, especially on low memory older services.
Custom ISO feature is pretty much exclusively being misused right now, with the #1 request being blank, #2 request being an existing ISO, and #3 being dead links or non-ISO links. We're going to kind of phase this out into "request ISO to be added" instead and/or "report problem with ISO."
rDNS has been added in SolusVM for all new blocks, but I've seen reports of it not working. I haven't had time to go through these specifically so it'd be helpful if we can get anyone here to use the feature and let me know what you're seeing in terms of issues and on which node so we can see if it's just all broken or clusters of problems.
Added a paste button to VNC and improved visibility of text as well as some general instructions on failure.
Added ChatGPT button on VNC, work in progress.
Not sure if this counts as a "new block" or not, but I just tried setting rDNS on node RYZE.CHI-Z001.VMS with a 193.151.183.xx address. I received a "Could not connect to DNS server. Please try again later" error message.
Really excited to get those Dallas servers racked and online in ATL this week, too!
Update:
It now actually keeps track of previous messages to some degree.
Okay, I'll look into it.
Just installed debian 12 on FFME007.VIRM.AC - waited 10 minutes as requested for install to complete then
apt-get update
apt-get install sshfs
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following additional packages will be installed:
fuse3 libfuse3-3
The following NEW packages will be installed:
fuse3 libfuse3-3 sshfs
0 upgraded, 3 newly installed, 0 to remove and 56 not upgraded.
Need to get 170 kB of archives.
After this operation, 540 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://deb.debian.org/debian bookworm/main amd64 libfuse3-3 amd64 3.14.0-4 [88.1 kB]
Get:2 http://deb.debian.org/debian bookworm/main amd64 fuse3 amd64 3.14.0-4 [35.9 kB]
Get:3 http://deb.debian.org/debian bookworm/main amd64 sshfs amd64 3.7.3-1.1 [45.6 kB]
Fetched 170 kB in 0s (2,075 kB/s)
Segmentation fault
E: Sub-process /usr/bin/apt-listchanges --apt || test $? -lt 10 returned an error code (1)
E: Failure running script /usr/bin/apt-listchanges --apt || test $? -lt 10
Anyone have suggestions?
Reverted to deb 11 for now.
Get your FREE VPS if you develop Open Source software
Update:
User chat bubbles added as well. Added loading animation, close button.
Figured this out, going to take some time to fix.
Sounds like a familiar issue we had before. I'll have to see if it only occurs on certain nodes or all of them, I only did basic testing and didn't run any updates. How much memory do you have?
@VirMach
Processor : AMD Ryzen 9 5900X 12-Core Processor
CPU cores : 4 @ 3693.060 MHz
AES-NI : ✔ Enabled
VM-x/AMD-V : ✔ Enabled
RAM : 3.3 GiB
Swap : 4.0 GiB
Disk : 27.8 GiB
Get your FREE VPS if you develop Open Source software
This is page I am welcomed (for last few days, however I didn't login earlier for like a week) after providing correct TOTP
clicking "Back to homepage" logs me in successfully, but this was kinda scary for first time.
I can confirm the same thing happening on TPAZ003.VIRM.AC
Haven't bought a single service in VirMach Great Ryzen 2022 - 2023 Flash Sale.
i am always scared of
fish
phishing
such pages because i think the jab's are out there fishing
Welp, this is even more scary.
Okey, it's gone after 2 minutes.
Haven't bought a single service in VirMach Great Ryzen 2022 - 2023 Flash Sale.
@VirMach thank you for keeping this thread updated. I had a VPS in SEA005 which after couple of months of downtime is finally up at LAX1Z012, but I am missing two ip4 from the network. Also, I thought based on what I read these are eventually moving to San Jose is that correct? Or do I request that via ticketing system? Do I wait for 2 missing ip4 to appear magically in sometime as you are working through or should raise ticket? Thanks again.
STOP BREAKING THE DATABASE!
If you didn't get your additional it means at the time it was fixed there were none left so it had to be done that way. Maybe a dozen or so people affected if I recall correctly. Wait a little bit so we have extra IPs available and contact us, or if you need it immediately then feel free to contact us sooner but let us know we can move you anywhere with available IPs.
Thanks for answer, I guess then it's something VirMach related as the same Debian packages/version running on other hosts don't drop Cloudflared/Argo tunnel that many times.
Dear @VirMach should the network in Frankfurt look like that? I know jackshit how this should be, but getting 1-97 ms icmp ping from gateway is not good, right?
Okey, I am even more confused - seems like there are Google DNS route pushed within DHCP as the same route...
and those has proper LAN timings - less than 1ms?
Haven't bought a single service in VirMach Great Ryzen 2022 - 2023 Flash Sale.
@VirMach said:
Receiving "Could not connect to DNS server. Please try again later" for NY server in ip range 141.11.22x.xxx
also, installed Debian 12 on RYZE.NYC-B013.VMS VM and I'm getting a segfault when I run apt upgrade. (not happening with other templates --- so I assume its a problem with the template.)
@VirMach rDNS works fine on:
Why the $30 setup fee for Tokyo VPSes?
Is it a good location for a VPN to connect from China?
This feels like dejavu. We added Debian 12 in the past and it had the same problem, didn't it? And then we removed it because we had to work on our own version not from SolusVM, that never happened, I forgot, and we went back to adding the SolusVM version that's still broken.
Yeah I forgot an important step for all these, I have to go one by one mapping them to specific primary ID for each as they were added to PowerDNS. SolusVM feature, because it'd be impossible to do it any other way that's less labor intensive.
We still get a good number of purchases, it helps balance out stock levels, and balance out abuse. Will likely be changed again as we usually do based on other factors.
Given $30 are too expensive, any other recommended location to set up a private VPN?
From China or anywhere?
If anywhere, just select the nearest location to you.
From China, usually what I've seen people do is in the order:
Tokyo
Hong Kong
Vietnam (Greencloud)
Singapore
US West Los Angeles
US West Seattle
The Ultimate Speedtest Script | Get Instant Alerts on new LES/LET deals | Cheap VPS Deals | VirMach Flash Sales Notifier
FREE KVM VPS - FreeVPS.org | FREE LXC VPS - MicroLXC
Novosibirsk, Russia
Test IP: 91.188.223.6
VirMach: Customer’s Service cannot use more than 10% of the monthly allocated bandwidth in under twenty-four (24) hours.
https://virmach.com/terms-conditions/#aup
I really wanted to do this location a while back as I was looking at all the global routes and thought it'd be an interesting location, but then it was definitely complicated after 2022.
When VirMach SG
食之无味 弃之可惜 - Too arduous to relish, too wasteful to discard.
I can be remote hands
食之无味 弃之可惜 - Too arduous to relish, too wasteful to discard.
I'll buy 10 of those sir
I bench YABS 24/7/365 unless it's a leap year.
hey, there are no forever friends nor enemies. russia will be back in one way or another.
I bench YABS 24/7/365 unless it's a leap year.
Sorry 10 of my hand or VPS?
食之无味 弃之可惜 - Too arduous to relish, too wasteful to discard.
is it too much to ask for both?
I bench YABS 24/7/365 unless it's a leap year.
I started working with my phoenix ryzen vps again. Installed Debian 11 and upgraded and it stopped working.
Reinstallling Debian 11... I suppose I should not upgrade the OS.