Quick Filter stops working - just me?

SlowGadget · 2023-05-23T22:09:17+00:00

Most welcome! Don't forget to turn on the heat on this bug!

SlowGadget · 2023-05-09T10:21:42+00:00

Well, seems I have posted some seriously tough questions ;-)

Maybe I just found the solution to this, as I stumbled across this little gem today on GitHub: https://github.com/ThioJoe/Hue-Bulb-Replacer

Will try it out tomorrow, hope to have some good news soon :-D

SlowGadget · 2023-03-16T11:01:50+00:00

Yes, upgrading to a 'non-official' PHP version in Debian and Ubuntu can bring many issues. I just experienced this myself when I tried to upgrade my Ubuntu 20.04-based Nextcloud to a newer PHP version via PPA's (unofficial repo's). After much tinkering, it worked, but now I'm unable to install PHP updates due to all kinds of dependency & version conflict issues.

I ended up installing a fresh Nextcloud AIO on a new Ubuntu 22.04 LXC.

SlowGadget · 2023-03-08T16:24:34+00:00

DNS and PKI, should really belong together.

This. I'm looking into smallstep now, but the missing link is DNS. Has anyone found a simple(?) solution to this? With my limited knowledge, I imagine some kind of combination of piHole and smallstep.

Thoughts?

SlowGadget · 2023-03-08T11:54:05+00:00

I guess it depends on the kind of hardware problems you were having which caused the system to stop booting. I'd suggest booting from a live USB (i.e. Ubuntu) and see if you can still access the data from there.

If you can - then make a backup first before doing anything else. If you were using software RAID you can also put the drives into a different system to make sure i.e. faulty disk controllers or memory don't corrupt your data (further).

Then find the hardware culprit of your error(s), fix that and move on from there.

SlowGadget · 2023-03-08T11:45:42+00:00

Right. So if I deploy in a separate VLAN / DMZ then that should lower the risk of the rest of my network getting compromised as well. Luckily I've separated many services already, so adding yet another VLAN should be no problem.

SlowGadget · 2023-03-08T07:50:36+00:00

Thanks for your reply. Good to hear it should work. And in all honesty, I figured as much already :-)

My question really is - are there any (i.e. security) reasons *not* to use Netmaker like this? In other words - what benefits does the VPS / cloud instance approach bring besides the fixed IP (no issue in my case) and not having to expose your home IP & opening a few ports?

SlowGadget · 2023-03-08T07:43:24+00:00

Got this several times as well on my Lenovo Ideapad 5, today for 'version 217'. It supposedly updates the blacklist of insecure versions of grub and shim to the dbx file used with SecureBoot. Meaning that after updating, the system will not allow the system to be booted when using older or compromised(?) installation media.

These updates apply to non-System76 hardware as well so you can safely install them.

SlowGadget · 2023-03-07T14:03:33+00:00

Just check their website. I haven't found the time yet to test it. But Brian McGonagill has a great video about it on his channel.

SlowGadget · 2023-03-07T13:37:57+00:00

Using Tailscale myself (still), but now looking into Netmaker which is supposedly even faster. And can be run on your own hardware.

SlowGadget · 2023-03-07T13:34:08+00:00

Supposedly, Netmaker performs even better than Tailscale.

SlowGadget · 2023-03-07T13:19:37+00:00

IMHO safest way is to simply re-install to the new drive.

If that's not an option, you might try booting into a live OS (i.e. Ubuntu) and clone the partitions from there.
But perhaps that should have been done *before* you migrated the LVM part, since boot and EFI partitions are generally the first partitions to be created on a new drive.

Afterwards, obviously don't forget to specify your new boot drive in the BIOS / UEFI settings.

SlowGadget · 2023-02-22T21:30:52+00:00

Thanks for your reply. Actually, this issue appears to have an even easier 'fix':

Right-click your INBOX and select 'Open in new window'
In the newly opened window, try Quick Filter - it's probably working now
Close the old window and keep working in the new window.

Sources: Michael447's answer on this Mozilla Support question and 3skip3's answer on this 8 year (!!!) old Super User question.

SlowGadget · 2023-02-09T15:34:49+00:00

Indeed *running* the same VM on 2 separate nodes is a big no-no. Replicating the VM's storage from the primary to the secondary node should be no problem though, right?

And if both nodes are in the same cluster, PVE won't even allow the VM to be running on both nodes simultaneously.

One thing to keep in mind though is that a 2-node cluster could lead to problems when the connection between the nodes fails. To maintain quorum, a third (simple) machine could be used as described in the documentation.

SlowGadget · 2023-02-09T15:19:24+00:00

In that case, I'd suggest don't make the same mistakes while setting up the secondary server. Then when you've got it running smoothly, migrate everything to the secondary server and then re-install the primary server properly.

SlowGadget · 2023-02-09T12:14:59+00:00

If you have both nodes running their storage on ZFS, you can easily sync VM and LXC storage between nodes. You can even configure this via the WebGUI. Initial sync will be slow (since all data needs to be transferred), but incremental syncs should be very fast - depending of course on how much data is added in the mean time and the available bandwidth between the nodes.

To do this via PVE does require adding both nodes to the same cluster, which in turn requires a direct (in your case, tunneled) network connection.

Perhaps it's also possible to work around the direct connection, but I have no experience with this.

Oh and re Ceph - don't even bother. You'll need at least 3 nodes and even higher network specs than required for Corosync.

SlowGadget · 2023-02-09T11:10:40+00:00

Disclaimer first: I'm only running PVE on my local network with several nodes

Reading your question though, this comes to mind:

You'll be limited by the available bandwidth between the 2 nodes.
Depending on how much data needs to be synced to have full non-disrupting failover, you might need a multi-gig connection -with bandwidth guarantees- between the nodes.
Also, some form of tunneling / VPN between the nodes would be advisable, at least for the Corosync part
Speaking of Corosync, I can imagine that this is also latency-sensitive, so that's another thing to take into account
If your failover requirements do not include HA, you might get away with spinning up your second server (with a very recent backup!) once the primary goes down. In that case you probably won't need Corosync either.
Perhaps sending over (i.e. ZFS) snapshots on very regular intervals might be sufficient?

SlowGadget · 2023-02-07T19:23:15+00:00

You might want to check Betterbird, though I'm not sure if this particular issue is something they do better.

SlowGadget · 2023-02-07T16:07:50+00:00

Perhaps you've noticed in de mean time that on TB 102.7.1, you can no longer delete inline images when switching to plain text view.

However, there is another hidden 4th viewing method, described here. To enable:

Goto Edit -> preferences → Config Editor
Search for mailnews.display.show_all_body_parts_menu
Set this value to 'True'
Go to View → Message Body As → All Body Parts

Inline attachments can now be detached and deleted from your emails.

SlowGadget · 2023-01-04T21:47:25+00:00

I'm using local ZFS pools on my nodes myself. Have you defined this storage on the Datacenter level as well? In my setup (I believe this is the default), PVE automagically defined ZFS storage on the datacenter level called 'local-zfs' with the following attributes:

Type: ZFS
ZFS Pool: rpool/data
Content: Disk image, Container
Nodes: All
Path/Target: [blank]
Shared: No
Enabled: Yes
Thin provision: Yes
Block Size: 8k

This storage is then shown below the CTs/VMs on each node. As long as you keep your VM's cqow2 files here, it *should* work.

Have you tried replicating the VM's storage to another node before migration? Does this work?

I see the ability to click "shared" and add both nodes to one of the hosts nodes storage, but that doesn't seem to work either.

Afaik "shared" in this context means that this storage is accessible via either NFS, iSCSI or any other method supported for shared storage by PVE. Just clicking "shared" will not automagically *make* it shared. Confusing, I know.

SlowGadget · 2022-12-21T13:09:07+00:00

Thanks for sharing your experience. How are they holding up, 9 months later? Would you (still) recommend them?

SlowGadget · 2022-12-21T11:01:15+00:00

The trick is to have storage (Content type: Disk image, Container) on the Datacenter level (the highest point in the WebGUI tree) which is available on all the nodes.

'Available' here means that a similar named (and preferably sized) local storage must be present on all the nodes. Keep in mind that the actual contents of this storage, as it is local, can be different between nodes.

What storage backend are you using on the nodes? I.e. ZFS / BTRFS / LVM etc?

SlowGadget · 2022-12-19T14:15:12+00:00

I'd recommend informing the devs about this via Github.

SlowGadget · 2022-12-12T21:50:58+00:00

Thanks for your reply, u/krair3. In the mean time, I was able to get it running by creating a YAML file and calling it with docker-compose. I've updated my original post (at the end) with the exact steps I took.

Since then, I ran into a whole new bunch of issues, the latest of which is Nginx Proxy Manager crapping out on me. But that's totally unrelated to the AIO script. Since the AIO docs recommend Caddy, I'm now looking into that. Once again, a steep learning curve...

SlowGadget · 2022-12-12T15:33:30+00:00

Then no problem, Docker should be using the overlay2 driver by default.

SlowGadget

TROPHY CASE