Hello,
Unfortunately some serious security bugs have been discovered in the
Xen hypervisor and fixes for these have now been pre-disclosed, with
an embargo that ends at 1200Z on 9 June 2022.
As a result we will need to apply these fixes and reboot everything
before that time. We are likely to do this in the early hours of the
morning UK time, on 7, 8 and 9 June.
In the next few days individual emails will be sent out confirming
to you which hour long maintenance window your services are in. The
times will be in UTC; please note that UK is currently observing
daylight savings and as such is currently at UTC+1. We expect the
work to take between 15 and 30 minutes per bare metal host.
If you have opted in to suspend and restore¹ then your VM will be
suspended to storage and restored again after the host it is on is
rebooted. Otherwise your VM will be cleanly shut down and booted
again later.
If you cannot tolerate the downtime then please contact
support(a)bitfolk.com. We may be able to migrate² you to
already-patched hardware before the maintenance is scheduled for
your host. You can expect a few tens of seconds of pausing in that
case. This process uses suspend&restore so has the same caveats.
Cheers,
Andy
¹ https://tools.bitfolk.com/wiki/Suspend_and_restore
² https://tools.bitfolk.com/wiki/Suspend_and_restore#Migration
--
https://bitfolk.com/ -- No-nonsense VPS hosting
_______________________________________________
announce mailing list
announce(a)lists.bitfolk.com
https://lists.bitfolk.com/mailman/listinfo/announce
Hi,
As requested this check is now enabled for all customer DNS zones in
the secondary DNS service. The alert will look like this:
https://tools.bitfolk.com/wiki/Secondary_DNS_service#Zone_serials_match
If you receive it then the first thing to do is to check your
nameserver's logs as it will normally be due to an issue that (only)
you can fix yourself.
Cheers,
Andy
----- Forwarded message from Mike Zanker via users <users(a)lists.bitfolk.com> -----
[…]
>> Maybe we should add some serial number monitoring, so if your zone
>> serial number changes but ours doesn't (because AXFR failed) then
>> that difference would be an alert.
I do like the sound of that, Andy (Smith).
----- End forwarded message -----
--
https://bitfolk.com/ -- No-nonsense VPS hosting
_______________________________________________
announce mailing list
announce(a)lists.bitfolk.com
https://lists.bitfolk.com/mailman/listinfo/announce
Howdy!
I have two VPS on bitfolk. The first one I didn't know I needed a
dedicated IP address, so had to order it and patched it in by editing
/etc/netplan/*.yaml as shown on
https://tools.bitfolk.com/wiki/Ubuntu#The_switch_to_netplan_for_configuring…
I added the - "x.x.x.x/32" (dedicated ip) underneath the - "x.x.x.x./21"
(VPS default IP) and did not use the "tab" ley because yaml didn't like
that.
I did a xen console shutdown and boot. The IP address shows up when
logging in the MOTD and in "ip a" successfully.
However, the dedicated IP address will not ping from outside, but the
default will. I have disabled ufw and still no network access.
On the second VPS, it was setup with dedicated IP address initially. So
both IPs are usable, ping from internet traffic and can be used. The
/etc/netplan/*.yaml on both installs is setup absolutely similar, showing
that my "patching" was correct usage.
Any help would be appreciated! I have never added an interface to a live
setup.
Timmy
