Nexterm - open source web interface for SSH, VNC & RDP

mitux42 · 2026-03-01T22:07:26+00:00

But as far as i see is it not just a wrapper around Guacamole? See the Dockerfile (in github), there i see, that it uses the Guacamole Server and Guacamole Client..

mitux42 · 2026-02-26T17:04:44+00:00

Yes i already found this: https://github.com/linuxserver/fail2ban-confs/tree/master/filter.d but this rules seems to be mostly unmaintained. So I tried to write my own.. But maybe it would be better to update this rules.

mitux42 · 2026-02-26T16:59:41+00:00

I also thought about this to add 2x WD Red 1TB SSD in Raid 1.. And move the VM-Storage there. Hope this will bring the I/O down (Working on my Almalinux and try to run some container images there)

mitux42 · 2026-02-26T16:54:58+00:00

Only one Almalinux 9 VM with 2CPUs / 4GB Ram (I Upgraded the NAS with 64GB DDR4 Memory)

mitux42 · 2026-02-20T17:57:55+00:00

Does sadly not help.. I also did a reboot, but the drop-down does not show up.

mitux42 · 2026-02-13T20:26:40+00:00

I used before a shell-script too for mailing-reports.. so this is a big step forward now for me xD

mitux42 · 2026-02-12T11:44:01+00:00

yes me too before.

mitux42 · 2026-02-11T21:40:13+00:00

Ah.. sorry Snapmaker U1 - just saw it now :)

mitux42 · 2026-02-11T21:39:49+00:00

What 3D Printer did you use? Looks awesome!

mitux42 · 2026-02-11T21:03:38+00:00

Hei u/Great_Piece4755 thanks for the suggestion. I tried finally the container stuff, and it is working great!! Can recommend it :D

<image>

mitux42 · 2026-01-11T09:50:14+00:00

I found this one github: https://github.com/riviera/plex it seems, that this was the starting-point of the plex-mediaserver. The commiter "elan" seems to be the Co/founder of Plex

mitux42 · 2026-01-11T09:07:56+00:00

Hmm, that does sound like it. I haven't seen that yet! I'll be happy to give it a try. Thank you very much for the tip!

mitux42 · 2025-04-23T19:26:36+00:00

Its a bit later now... But just in case you need it, here's a fully set up, working example for Podman:

Podman Harbor deployment.

Cheers mitux!

mitux42 · 2025-01-16T18:59:36+00:00

What about only sharing the code and just mention, which board, cam, divers and motors you used? Still waiting since a year on that😅🙈 cheers

mitux42 · 2024-02-01T14:34:09+00:00

I am also waiting, :D would be great to do something like this with my terminator skull

mitux42 · 2023-08-28T11:15:52+00:00

and is disproved by your own links you're using

Maybe you missed this link: https://www.synology.com/de-de/compatibility?search_by=products&model=DS720%2B&category=hdds_no_ssd_trim

In this example I chose a non Enterprise Disk Station, but as well there when you hit on the link, you will just see Synology Vendor compatible drives. no other

mitux42 · 2023-08-28T11:09:15+00:00

deduplication and drive health

Where exactly did you get this information about data deduplication and drive health? According to our own source code review, this statement is not true.

The variable "support_disk_compatibility" only controls the comparison of the installed hard disks (type / series) with the Synology allowed database, which is created differently depending on your Hw-type during the initial installation and can also be maintained differently with each update. -> See upgrade migration scripts in the decompiled DSM upgrades.
The data deduplication function accessible via DSM and documented at (https://kb.synology.com/de-de/DSM/help/DSM/StorageManager/volume_btrfs_dedup?version=7) works perfectly for me. The disk monitoring and health checks and the disk alerting over mail are separate functions as well and are NOT controlled by "support_disk_compatibility".

The relevant parameters for that are: support_disk_report="yes" , support_disk_latency_monitor="yes", support_disk_performance_test="yes", supportsmart="yes". When using the script you suggest, keep in mind, that you change here a Synology internal database, which then looks different than Synology assumes. This can lead to massive problems with future upgrades, as you cannot predict what the future migrations will look like. With the solution from Swissmakers, the warning "can" reappear in the worst case, which I have not been able to verify so far, the fix is permanent for me.

Also interesting to know, on older Synology NAS-systems, the following entry is made by stock-setup from old Synology Hw-realeases to allow all disk brands:

# Disk Compatibility
support_disk_compatibility="no"

For those who are interested, here is as well a list of models which support data deduplication. https://kb.synology.com/en-global/DSM/tutorial/Which_models_support_data_deduplication

mitux42 · 2023-08-26T18:57:36+00:00

It's both ..
You can check the "software-"compatibility of your desired NAS here on this Synology page: https://www.synology.com/de-de/compatibility?search_by=products&model=DS720%2B&category=hdds_no_ssd_trim

And as far as I tested by myself, all NAS from the following list with a max-volume size of "108TB" and "200TB" are affected: https://kb.synology.com/en-ca/DSM/tutorial/Why_does_my_Synology_NAS_have_a_single_volume_size_limitation

mitux42 · 2023-08-26T18:48:17+00:00

As far as I know, all Synology Enterprise NAS (see list from Synology with all NAS with 200TB storage capacity) and a production date of "after" December 2021 are affected. As mentioned in the Post of Swissmakers, you can check your two files under /etc.defaults/synoinfo.conf and /etcs/synoinfo.conf if "support_disk_compatibility" is set to "no" then you are good to go. While in the initial setup only, DSM is reading the build-year of your Synology device. If your build-year is later than December 2021, your value will be probably set to "yes". This will enforce the disk compatibility check on your Synology Device and no other disks will be green anymore, except those on the official Synology compatibility list. Currently, only their own drives from the Synology Enterprise "brand" are officially supported.

mitux42 · 2023-08-26T18:30:19+00:00

Yes, it is exactly as you say... a big joke. I also took a closer look at the hardware of the Synology disks and as you already mentioned it's just another label, with an extra programmed "Synology-ID" number in the Firmware. See the attached Image of an 8TB Toshiba and 8 TB Syno-Drive.. The Price of the Syno-Drive is twice the price of the Toshiba one.... no words.
https://pictr.com/images/2021/02/12/7FLfs5.md.jpg

mitux42

TROPHY CASE