I think that @Falzo is suggesting disabling it altogether and to let people decide for themselves whether to run it through a translation program. After all, only the English version is the legally binding version.
Perhaps this is worth an FAQ item?
Perhaps disabling auto-translation for ToS and instead linking to a “TL;DR no guarantee/non legal binding” ToS summary with auto-translation would be the way to go. Iirc @Francisco has a Tl;dr ToS version and it’s great 
2 Likes
I advise clients when asked to use stripe rather than pp if making international payments.
so with stripe I would have been aked for the 5.80 ? I haven’t used srtipe for quite a while, so genuine question 
The problem with paypal is they always revert back to our accounts default currency no matter the currency the token from WHMCS was sent in.
alright, will see if and when I renew about it… if the stripe thing does not work as intended, I hope you can at least change the currency back to GBP in your system then for future invoices? As said it’s not neccessarily about the difference but about tax declaration
however, let’s see what that box can do. came with centos 
instead of the requested debian, but hey, I guess that’s due to the manual install
good chance to see if and how the reinstall works though…
Yes. That too is what my response implied.
Gone ahead and made English default across all sites. The option to change the language is now the users choice.
Added
1 Like
Will definately look into this as an option moving forward.
1 Like
With Stripe, you would have had a better conversion rate therefore the final bill would have been slightly less.
Sure, your default currency can be changed back to GBP at time by opening a ticket.
CentOS is simply my choice of preference 
apologies for not taking into account your specification for debian.
Our Debian 10 template has a bug. So, unless you are comfortable managing your VPS via VNC (SSH will not work), you might want to steer clear of that template (for now).
Geekbench for Kansas: Red Hat KVM - Geekbench Browser
Nench:
-------------------------------------------------
nench.sh v2019.07.20 -- https://git.io/nench.sh
benchmark timestamp: 2019-11-03 20:55:17 UTC
-------------------------------------------------
Processor: Intel(R) Xeon(R) CPU E7- 4870 @ 2.40GHz
CPU cores: 4
Frequency: 2397.400 MHz
RAM: 7.8G
Swap: 1.0G
Kernel: Linux 4.15.0-22-generic x86_64
Disks:
vda 50G HDD
vdb 50G HDD
CPU: SHA256-hashing 500 MB
5.743 seconds
CPU: bzip2-compressing 500 MB
9.613 seconds
CPU: AES-encrypting 500 MB
2.471 seconds
ioping: seek rate
min/avg/max/mdev = 119.2 us / 459.5 us / 31.7 ms / 436.5 us
ioping: sequential read speed
generated 5.95 k requests in 5.00 s, 1.45 GiB, 1.19 k iops, 297.5 MiB/s
dd: sequential write speed
1st run: 228.88 MiB/s
2nd run: 354.77 MiB/s
3rd run: 460.62 MiB/s
average: 348.09 MiB/s
IPv4 speedtests
Cachefly CDN: 69.06 MiB/s
Leaseweb (NL): 7.16 MiB/s
Softlayer DAL (US): 74.20 MiB/s
Online.net (FR): 19.40 MiB/s
OVH BHS (CA): 18.43 MiB/s
IPv6 speedtests
your IPv6: 2a0a:1f42:1001:xxxx
Leaseweb (NL): 8.00 MiB/s
Softlayer DAL (US): 69.12 MiB/s
Online.net (FR): 12.96 MiB/s
OVH BHS (CA): 24.48 MiB/s
-------------------------------------------------
more DL speedtest EU/US:
Vultr, Frankfurt, DE 108.61.210.117 19.9MB/s
Linode, Frankfurt, DE 2a01:7e01::4b 10.6MB/s
Softlayer, Frankfurt, DE 2a03:8180:1201:45::4 1.53MB/s
Leaseweb, Frankfurt, DE 2a00:c98:2030:a034::21 10.8MB/s
DO, Frankfurt, DE 2a03:b0c0:3:d0::36:3001 7.14MB/s
Vultr, Paris, FR 108.61.209.127 18.4MB/s
OVH, Gravelines, FR 2001:41d0:a:79c8::1 3.15MB/s
OVH, Strasbourg, FR 2001:41d0:8:a051::1 2.95MB/s
OVH, Roubaix, FR 2001:41d0:2:876a::1 7.22MB/s
Online.Net, Paris, FR 62.210.18.40 13.1MB/s
Tele2, Amsterdam, NL 2a00:800:1010:8::2 18.7MB/s
Vultr, Amsterdam, NL 108.61.198.102 22.4MB/s
DO 2, Amsterdam, NL 2a03:b0c0:0:1010::91:d001 19.8MB/s
DO 3, Amsterdam, NL 2a03:b0c0:2:d0::85:e001 8.27MB/s
Leaseweb, Amsterdam, NL 2001:1af8:4700:b210::33 9.88MB/s
i3d, Amsterdam, NL 2a00:1630:1:13d::133d 11.1MB/s
Vultr, London, UK 108.61.196.101 25.1MB/s
DO, London, UK 2a03:b0c0:1:d0::2c:2001 10.4MB/s
Linode, London, UK 2a01:7e00::4b 13.2MB/s
Softlayer, London, UK 2a03:8180:1101:5::4 12.8MB/s
Softlayer, Mexico, MX 2607:f0d0:1c01::4 49.8MB/s
Softlayer, Brazil, BR 2607:f0d0:1d01:12::4 9.19MB/s
DO 1, NYC, USA 2604:a880:400:d0::62:f001 34.7MB/s
DO 2, NYC, USA 2604:a880:0:1010::2b:a001 30.9MB/s
DO 3, NYC, USA 2604:a880:800:a1::19:9001 22.4MB/s
Vultr, New Jersey, USA 108.61.149.182 53.1MB/s
Linode, Newark, USA 2600:3c03::4b 49.9MB/s
Vultr, Illinois, USA 107.191.51.12 76.9MB/s
Vultr, Atlanta, USA 108.61.193.166 53.2MB/s
Linode, Atlanta, USA 2600:3c02::4b 29.9MB/s
Vultr, Miami, USA 104.156.244.232 51.1MB/s
Vultr, Washington, USA 108.61.194.105 49.7MB/s
Softlayer, Seattle, USA 2607:f0d0:2001:3::2 37.5MB/s
Leaseweb, Washington, USA 2604:9a00:2010:a0b8::5 24.8MB/s
Vultr, Dallas, USA 108.61.224.175 42.1MB/s
Linode, Dallas, USA 2600:3c00::4b 70.0MB/s
Softlayer, Dallas, USA 2607:f0d0:1101:4::2 72.9MB/s
Leaseweb, Dallas, USA 2606:9880:2100:b010::1531 56.4MB/s
Vultr, Los Angeles, USA 108.61.219.200 42.8MB/s
DO, San Francisco, USA 2604:a880:2:d0::ba:d001 18.8MB/s
DO, San Francisco, USA 2604:a880:1:20::9:9001 59.7MB/s
Linode, Fremont, USA 2600:3c01::4b 34.4MB/s
Leaseweb, San Francisco, USA 2605:fe80:2100:b001::5187 28.3MB/s
DO, Toronto, CA 2604:a880:cad:d0::11:f001 53.3MB/s
OVH, Beauharnois, CA 2607:5300:60:44a5::1 10.2MB/s
EastLink, Canada, CA 24.222.0.194 20.7MB/s
Softlayer, Montreal, CA 2607:f0d0:3701:16::4 30.9MB/s
not so bad for a cheapish VM like that, with shared ressources
will check again after BF and decide if it’s going to be a long time idler. I guess I can switch to the discounted yearly pirce at any time later, right?
3 Likes
Sorry, I missed the question at the end. Yes, that would be possible.
1 Like
TIL withdrawn posts trigger me.
It’s OK baby, I won’t pull out.
1 Like
Promise?
As long as you keep that zipper closed, we’re ok.
Haha I wanted to ask for bench results for the KC box until I saw one posted by Falzo 
1 Like
Satisfied ? Not bad huh ?
Indeed.
1 Like
This topic was automatically closed after 14 days. New replies are no longer allowed.