BitFolk Users

users@mailman.bitfolk.com

1117 discussions

Erroneous alerts regarding backup3.bitfolk.com

by Andy Smith

Hi, A bunch of alerts were just sent out regarding backup3.bitfolk.com. I am doing some work on this host and forgot to disable alerts. There is no need for concern. Apologies for the confusion. Cheers, Andy -- https://bitfolk.com/ -- No-nonsense VPS hosting _______________________________________________ announce mailing list announce(a)lists.bitfolk.com https://lists.bitfolk.com/mailman/listinfo/announce

8 years

Re: [bitfolk] How to handle unresponsive customers with issues that cannot be ignored

by C. Scott Ananian

I think just turning the dropdowns into radio buttons (so all are visible immediately) would solve the immediate UX problem. --scott On Dec 19, 2016 9:32 AM, "Richard Dignall" <richard(a)dignall.co.uk> wrote: On Mon, Dec 19, 2016, at 02:30 PM, Roger Light wrote: > It makes sense to me now that you've said that. I think it's confusing > as it is. For those people with only a single person on the account I > imagine there is a tendency to ignore the "add another contact" option > because I'm already the contact and so there should be no need. This. At some point I probably clicked to add a new contact, saw that there were no obvious fields that linked to anything different that wasn't in the main contact, and clicked Cancel. _______________________________________________ users mailing list users(a)lists.bitfolk.com https://lists.bitfolk.com/mailman/listinfo/users

8 years

Vulnerability scanning and timescales for action

by Andy Smith

Hi, There was a consultation earlier regarding what to do about customers who do not react to the alerts we send about serious security issues we have found during regular scans of our IP space: http://lists.bitfolk.com/lurker/message/20161215.152008.2ee18732.en.html Dealing with that was becoming quite a time sink and I was also getting concerned about potentially inconsistent handling of these issues when not working to any kind of documented process. The consensus seemed to prefer the idea of network suspension after 21 days, so this has now been documented along with a bit more information about the things we (or partners) scan for: https://tools.bitfolk.com/wiki/Vulnerability_scanning This will now allow for some more automation. I've also updated the Terms and Conditions page: https://bitfolk.com/policy/terms.html with a new paragraph that points to that page: BitFolk and its partners regularly scan BitFolk's IP space for well-known vulnerabilities and misconfigurations, some of which are serious enough that BitFolk will insist that The Customer fixes them within a reasonable timescale. Although the paragraph above that one is the usual blanket "reserve the right to suspend service", so perhaps technically not necessary to list particular things, it does however seem like useful info to have there. Normally we try to have changes to T's&C's not take effect for 30 days but I don't see this as a change, since we have always used the "reserve the right to suspend service" clause if necessary with things like this. So if it is unfortunately necessary to suspend someone's network we won't be waiting until 30+21 days to do it. And happily there currently isn't anyone who's been receiving alerts for anything like that long. If you have any questions or feel the article (or process) could be improved please let us know. Cheers, Andy -- https://bitfolk.com/ -- No-nonsense VPS hosting "The electric guitar - like making love - is much improved by a little feedback, completely ruined by too much." — The League Against Tedium _______________________________________________ announce mailing list announce(a)lists.bitfolk.com https://lists.bitfolk.com/mailman/listinfo/announce

8 years

Backups will now be disabled when you go over quota

by Andy Smith

Hi, If you don't use BitFolk's backup service then you can ignore the rest of this email. For a very long time we have allowed customer backups to go past the quota and still continue working, arranging at a later time to fix that situation (by the customer asking for some backed up data to be deleted or else ordering more storage for backups). This is now changing so that backups will stop happening once the quota is exceeded. Nagios alerts have always been sent out as WARNING at 95% of quota and CRITICAL at 99% of quota. There is also a Nagios check for age of backups and that will start to fire when there has been no successful backup for a certain amount of time¹. Those whose backups get suspended for being over quota will start to receive that one. So, if you are currently receiving these alerts you do need to do something about it. Customers who are already over their backup quota at the moment have already been contacted via support ticket, but in future we may leave it down to you to get in touch. Cheers, Andy ¹ The time scales for those alerts depend on the backup schedule in use. For those having a backup run every 4 hours (the default) it's a WARNING after 10 hours and CRITICAL after 24 hours. -- https://bitfolk.com/ -- No-nonsense VPS hosting _______________________________________________ announce mailing list announce(a)lists.bitfolk.com https://lists.bitfolk.com/mailman/listinfo/announce

8 years

Upcoming reboots for security fixes prior to 13 December

by Andy Smith

Hi, Rather disappointingly there's been another round of security advisories for Xen, some of which affect the configuration in use at BitFolk: http://xenbits.xen.org/xsa/ So unfortunately that means another round of "patch and reboot everything" for us. We will send out direct emails informing you of a two hour window in which the work affecting your VPS is going to take place, but that won't be sent for a week or so as testing of the patches will be necessary first. I am going to try to get a checkbox added to the panel website so that those of you who are brave enough to try it can indicate that you'd prefer for your VPS to be suspended and restored rather than shutdown and booted. Cheers, Andy -- https://bitfolk.com/ -- No-nonsense VPS hosting _______________________________________________ announce mailing list announce(a)lists.bitfolk.com https://lists.bitfolk.com/mailman/listinfo/announce

8 years

Re: [bitfolk] Upcoming reboots for security fixes prior to 13 December

by Steven Walker

I am strictly an amateur geek having a bit of fun so am not very worried about down time. For me it is much better to be as safe as possible as I am less likely to be pouring over logs looking for suspicious activities - and when I do I might not recognise them. Steve

8 years

Getting IPv6 working

by Gavin Westwood

So, I've had IPv6 configured how I believe it should be for some time, but every time I test it (which is limited by the lack of IPv6 connectivity by my backward ISP), it doesn't seem to be working, in or out. Can anyone help me getting it working? I've replaced my IP allocation with 'beef' below. I've flushed my ip6table rules for now /etc/network/interfaces: <snip> iface eth0 inet6 static address 2001:ba8:1f1:beef::2 netmask 64 gateway 2001:ba8:1f1:beef::1 post-up sysctl -w net.ipv6.conf.default.accept_ra=0 post-up sysctl -w net.ipv6.conf.all.accept_ra=0 post-up sysctl -w net.ipv6.conf.${IFACE}.accept_ra=0 post-up sysctl -w net.ipv6.conf.default.autoconf=0 post-up sysctl -w net.ipv6.conf.all.autoconf=0 post-up sysctl -w net.ipv6.conf.${IFACE}.autoconf=0 # ip -6 addr show dev eth0 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qlen 1000 inet6 2001:ba8:1f1:beef::2/64 scope global deprecated valid_lft forever preferred_lft 0sec inet6 2001:ba8:1f1:beef:216:5eff:fe00:2c0/64 scope global deprecated mngtmpaddr dynamic valid_lft 22130sec preferred_lft 0sec inet6 fe80::216:5eff:beef:2c0/64 scope link valid_lft forever preferred_lft forever eth0 Link encap:Ethernet HWaddr 00:16:5e:00:02:XX inet addr:85.119.X.Y Bcast:85.119.A.B Mask:255.255.248.0 inet6 addr: fe80::216:5eff:fe00:2c0/64 Scope:Link inet6 addr: 2001:ba8:1f1:beef:216:5eff:fe00:2c0/64 Scope:Global inet6 addr: 2001:ba8:1f1:beef::2/64 Scope:Global UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:622300 errors:0 dropped:0 overruns:0 frame:0 TX packets:598288 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:X (X.X MiB) TX bytes:X (X.X MiB) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:54214 errors:0 dropped:0 overruns:0 frame:0 TX packets:54214 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:X (X.X MiB) TX bytes:X (X.X MiB) # ip -6 route 2001:ba8:1f1:beef::/64 dev eth0 proto kernel metric 256 fe80::/64 dev eth0 proto kernel metric 256 # traceroute6 ipv6.google.com traceroute to ipv6.google.com (2a00:1450:4009:807::200e), 30 hops max, 80 byte packets connect: Network is unreachable

8 years

OpenBSD guest?

by craig＠craigm.net

Hi all. Have had bitfolk recommended and it has been said that custom ISOs can be uploaded, which I've also read on the website. OpenBSD 5.9 and 6.0, last and current releases, have native Xen PVHVM drivers. Is this enough for me to be able to install OpenBSD into a guest instance? Am I also right in my understanding that the guest OS must have an ext2 or 3 boot partition? OpenBSD uses ffs, so I'll have to find a work around there, I assume? TL;DR I'm looking for a VPS service, based in the UK, that I can run OpenBSD on. Can this be done with bitfolk?

8 years

IP Bill, BitFolk, and VPNs

by Chris Dennis

Hello BitFolk People This http://www.hailpixel.com/articles/how-to-protect-your-online-communications excellent article about the implications of the IP Bill suggests using a VPN to help to keep the snoopers at bay. Here's a question: is BitFolk an 'ISP' for the purposes of the bill? -- does it collect metadata about traffic in and out of my VPS? If not, would it make sense to use my BitFolk VPS as a VPN, so that it proxies my home internet connection? I've been toying with the idea of using software such as OpenVPN for this, and the bill (very nearly an Act now) gives me another reason for getting on with it. The alternative would be to use a paid-for VPN provider such as the ones recommended in that article. Cheers, Chris

8 years, 1 month

Upcoming reboots for security fixes prior to 22 November

by Andy Smith

Hi, Unfortunately a batch of security advisories for Xen were posted today, some of which affect the configuration in use at BitFolk: http://xenbits.xen.org/xsa/ The details are under embargo until 22 November, so a reboot of all hosts will need to take place before then. You should expect this work to be carried out over a few days prior to the 22nd. We will send out direct emails informing you of a two hour window in which the work affecting your VPS is going to take place, but that won't be sent for a week or so as testing of the patches will be necessary first. Cheers, Andy -- https://bitfolk.com/ -- No-nonsense VPS hosting _______________________________________________ announce mailing list announce(a)lists.bitfolk.com https://lists.bitfolk.com/mailman/listinfo/announce

8 years, 1 month

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

BitFolk Users