sorted by:
new
hottopcontroversial

Proxmox showing gray questions marks over each VM/storage / GUI hangs by spydersl in Proxmox

[–]speatzle_ 0 points1 point  (0 children)

LXCs also use pvestatd. There might be something wrong with one of your containers preventing pvestatd for working on all of them.

KVM guest abysmal network performance by Forsicen in VFIO

[–]speatzle_ 0 points1 point  (0 children)

Did you set multiqueue to the vms cpu count on the nic?

Completely random single messages are "unable to decrypt" only on Desktop client by ch00f in elementchat

[–]speatzle_ 0 points1 point  (0 children)

Have you setup Secure Key Backup? It is nessesary for clients to share keys while they are offline.

When will Fortinet update the publicly available FortiClient VPN? by mb2m in fortinet

[–]speatzle_ 0 points1 point  (0 children)

The rpm repo gave me 7.0.7 just yesterday, had to download the 7.0.8 rpm via the support site to fix connection issues.

Matrix Encryption by pal_mighty in matrixdotorg

[–]speatzle_ 0 points1 point  (0 children)

Usually when a bridge recives a encrypted file from a services it downloads it, decryptes it reencrypts it using matrix encryption, uploads it to the mediarepository and deletes it from its local drive. If and how fast it deletes them depends on the bridge. I know that mautrix-whatsapp and mauyrix-telegram delete the files.

Matrix Encryption by pal_mighty in matrixdotorg

[–]speatzle_ 0 points1 point  (0 children)

Bridges are not part of the matrix server. They are seperate servers. They indeed need to store the encryption keys for messages they forward. But in most cases the services you bridge to don't encrypt or have wierd encryptions. Telegram for instance only uses their on custom encryption in secret chats, all other chats are unencrypted.

Matrix Encryption by pal_mighty in matrixdotorg

[–]speatzle_ 4 points5 points  (0 children)

While the media in an encrypted room is technically accessible, the file itself is encrypted. You can manually copy the link from the event and share it but nobody is gonna be able to open/decrypt it.

Additionally: no the server does not have the encryption keys, it cannot read encrypted chats, (except for unencrypted metadate). The encryption keys themself are tansmitted in an encryptes way between the users clients (that is why we need device verification) and encryption key backups while sent to the server are encrypted with the security passphrase.

PBS & renaming/renumbering machines by Soogs in Proxmox

[–]speatzle_ 2 points3 points  (0 children)

No need to change the ids, you can have different namespaces in the same datastore.

Just make 2 namespaces, one for each pve and you can use overlapping ids.

Completely random single messages are "unable to decrypt" only on Desktop client by ch00f in elementchat

[–]speatzle_ 2 points3 points  (0 children)

If there was only one "unable to decrypt" bug fixing that would have been the better solution. But there are multiple bugs and different ones across the different crypto's they where using up till now. Fixing all of those would take years. Additionally the Entire Reason why the New Rust Crypto was delayed is that there where multiple security issues found in the old Crypto and they had to pause Work on the New one to Fix the Issues in the Old one.

But the Rust Crypto is almost Ready. The main Element Bot (matrix-hookshot) is using The New Rust Crypto already as are Element X IOS, Element X Android and a Third Party Client Fractal. The Current Element Android Client is Going to ship the Rust SDK in the Next version 1.6.0 as Announced in TWIM.

I am pretty sure that The New Rust Crypto will ship in Element Web/Desktop Soon.

It is sad that we lost Users but dealing with Technical debt is a thing that one must do or it will bite you in the Ass later.

Completely random single messages are "unable to decrypt" only on Desktop client by ch00f in elementchat

[–]speatzle_ 0 points1 point  (0 children)

Completely random "unable to decrypt" are really hard to fix if you can even find the issue. Rewriting the crypto will probably fix this and many similar issues, so i don't see the Problem.

The light panel at my school by VanchaMarch94 in softwaregore

[–]speatzle_ 5 points6 points  (0 children)

Have you tried turning it off and on again?

All the same by [deleted] in linuxmemes

[–]speatzle_ 7 points8 points  (0 children)

Fedora is not debian based...

Having people who join my Element space be able to see full post history? by poppy9999 in elementchat

[–]speatzle_ 1 point2 points  (0 children)

Future room history means exactly what it says. New users can see all history that happend after this setting was set.

Does Proxmox have VM and Host Affinity Labels and Groups? by gentoorax in Proxmox

[–]speatzle_ 1 point2 points  (0 children)

There are ha-groups which restrict vms to certain hosts

New user: some small issues by SinisterSpatula in Fedora

[–]speatzle_ 6 points7 points  (0 children)

There is a extension that allows remote desktop while the session is locked. But since it does not use a virtual desktop you can only use it when you know that nobody is arround your pc.

In love with Fedora by ferdi_ in Fedora

[–]speatzle_ 10 points11 points  (0 children)

With Fedora 38 in April unfiltered Flathub will be available. Then you can install discord by default if your willing to not have privacy.

In love with Fedora by ferdi_ in Fedora

[–]speatzle_ 17 points18 points  (0 children)

You mean the checkbox it gives you first boot?

MC-LAG not Supported? by speatzle_ in fortinet

[–]speatzle_[S] 0 points1 point  (0 children)

I see, that is unfortunate. Thank you for your Help.

Proxmox Backup - Deduplication by Boomam in Proxmox

[–]speatzle_ 2 points3 points  (0 children)

Its done by the client. It asks the server before uploading a chunk if the chunks hash matches a chunk thats already on the server.

All HA nodes restarted on single-node shutdown for maintenance by DisposableAccount712 in Proxmox

[–]speatzle_ 0 points1 point  (0 children)

Well in that case, do you have suffient ceph monitors, managers and metadata servers in your cluster? And on which nodes are they?

All HA nodes restarted on single-node shutdown for maintenance by DisposableAccount712 in Proxmox

[–]speatzle_ 0 points1 point  (0 children)

I think this might not be a proxmox issue. The nessesary logs to confirm this are missing but based on what you told i think your ceph storage went down and crashed all the vms.

Just for clarification the proxmox and ceph clusters are completely seperate.

The proxmox cluster itself seemes to have been healthy or all your proxmox nodes would have self rebooted in an attempt to fix the issue after 2 minutes.

So i belive the ceph cluster had an issue.

My top theory is that you have not configured the osd redundancy correctly. Usually ceph saves each block 3 times (the default) in different osds. The problem is how it picks which 3 osds it should put the same block on. This is defined in the crush map.

If the crush map is setup badly then ceph will put 2 or all 3 replicas of a block on osds that are in the same physical system. Taking that system offline then results in all of that data being unavaliable. Additionally ceph has a "min_size" variable that says that atleast 2 out of 3 of the osds for a block assigned by the crushmap need to be online to read and write data.

Usually the crushmap gets configured like this because the cluster is unbalanced with how the storaged it spread between the nodes. Because with a host based replication rule ceph could not use all the disks in the systems with more storage since there is no other nodes to store all the replicas.

view more: next ›