I have a lot of services running in docker containers on my TrueNAS server from Jellyfin, Mealie, Gitea, WordPress, DokuWiki, and more. I now want to create a simple to configure Google Search-like feature that crawls all these locally hosted sites to create a locally hosted search where I can search things like Star Wars and see all the media hosted in Jellyfin and game listing in Gitea. I found Typesense but it seems to be a bit more complex to set up than I have time for and I haven't been able to find a good tutorial video.

Any ideas?

I’m diving into the world of dedicated servers and trying to find the best provider for my needs. As a geek who loves tinkering with tech, I want to make an informed decision rather than just picking the first company that pops up on Google.

For those of you who’ve been down this road, what are the key things you look for in a dedicated server provider?

Also, if you’ve had horror stories or great experiences, I’d love to hear them. I’m especially curious about underrated companies that aren’t OVH, Hetzner, or Leaseweb but still deliver solid performance.

Appreciate any insights from the pros here!

After almost two years, Neko v3 has been released, along with a redesigned webpage and complete documentation. This update includes many new features and bug fixes focused on the backend. The next step will be upgrading the client.

Good news for those who have been using Neko v2— all configuration options remain backward compatible, making the upgrade seamless without any additional effort. Stay tuned for upcoming client features!

Docs: https://neko.m1k1o.net/
Repo: https://github.com/m1k1o/neko

I host a radio station and realized some of you might do the same. A few months ago, I made an automated weather forecast generator for my radio station and I recently learned that my local traffic service (UDOT for Utah) has an accessible API that allowed me to generate traffic reports using their data. Worked out pretty well! Feel free to give it a try. There's a sample in the repository if interested.

https://github.com/TannerNelson16/radio_traffic_report_udot/

Hi everyone,

According to GitHub traffic stats, a significant number of TinyFeed users come from r/SelfHosted, so I wanted to share a quick release update!

(If you’re not familiar with TinyFeed, it’s a simple tool that allows you to generate a static HTML page from a collection of feeds using a simple CLI tool. No database or complex setup is needed.)

Since the last post, TinyFeed has gained: - A guide for hosting TinyFeed using GitHub Actions and GitHub Pages - Support for comments in input files - Several bug fixes - Various quality-of-life and documentation improvements

Nothing grandiose, but TinyFeed was always meant to stay as simple as possible. My plan is to keep adding small, incremental improvements while keeping the core stable.

Check it out and let me know what you think! 🚀

Hey everyone, I embarked on my self hosting journey fully a few months ago and got a used Lenovo M720q to use as a home server. Now I realize that I do need more storage. I am not quite ready to invest in a full sized NAS atm, that’s on the roadmap for somewhere down the line. For now, I was thinking about adding a usb HDD to the server. What is your experience with that? Any advice on other options?

• sets up no-subscription repos of Proxmox;
• removes "No valid subscription" notice;
• can be configured (default is auto to both);
• survives upgrades.

The original post regarding free-pmx-no-subscription tool that explains how it is more streamlined and sound than script-only solutions got updated - see below.

Can be installed on PVE or PBS whether the repos have been already set or not - including with installs on top of Debian. Mode of failure of any setup step (including patching) is to end up doing nothing, i.e. worst case scenario nothing is changed - as will be clearly reported. Auto-configures both (repos+nag) on first install. (This can be avoided if you pre-create config file.) The actual upgrade (with the newly set repos) is up to the user.

Only minor bugfix for v0.1.2 (#1 - false error message) and manual pages (HTML versions linked below) tidied up. No impact on functionality.

If you have the initial version installed, it can be simply installed "over it", Debian will take care of the rest, configuration preserved:

wget -P /tmp https://free-pmx.pages.dev/packages/free-pmx-no-subscription_0.1.2.deb apt install /tmp/free-pmx-no-subscription_0.1.2.deb

Since this is a standalone Debian package download and install, there is no foreign repositories added to the system to worry about, so updating is then manual only as well.

Instructions how to audit the package before installation are now separate and expanded.

Changes can be audited in GitHub Commit View.

Remove with:

apt remove free-pmx-no-subscription

or including configuration:

apt purge free-pmx-no-subscription

Thanks to those who provided feedback! Feel free to file enhancement ideas as well...

---

A neater Proxmox no subscription setup

TL;DR Download and install a Debian package for your no subscription deployment of Proxmox suite of products. Also remove "No valid subscription" popup in one go and safely. Initial version. PVE and PBS tested. Feedback welcome.

---

ORIGINAL POST A neater Proxmox no subscription setup

---

Lots of users run Proxmox suite of products with no support license and that is completely fine as long as they understand the caveats of freely available packages. There are two major chores: - setting up no-subscription repositories and disabling the "enterprise" one that came pre-set; and - the infamous "No valid subscription" notice popup also dubbed as a nag.

Dealing with both is somewhat manual and tiresome effort. The latter being actively discouraged by Proxmox themselves despite the fact the products are all distributed under FREE license which grants everyone freedom to modify it as they please.

Issues with standalone scripts

There are various popular and more or less trustworthy scripts dealing with both, but there is a major caveat: Patched files will not stay patched forever, they would get overwritten during upgrades from official repositories. A hack involved by most scripts is to place a specific code - essentially a recurrent script into /etc/apt/apt.conf.d/ where it is then launched whenever ANY and EVERY package is being dealt with. This is BAD design, not to mention users often do not understand let alone scrutinise these scripts and they stay behind unless their author provided yet another script to remove them.

A tiny package

Meanwhile, Debian already provides a neat mechanism for handling all these situations and that is by the packaging system itself. A package can bring in its executables, configuration and declare its interest to be notified when other packages are altering files on the system. It is the system that decides when it will trigger actions implemented by the interested package and under no other than declared rules.

No dubious APT repository

A package can be installed manually - from a single downloaded file - without having to trust an unknown repository. This one-off approach will NOT keep it updated, but this is the safer way to run code from strangers.

Transparency

It is also where the system provides its benefit of transparency - maintainers have to follow certain standards with Debian packages if they want it to pass a check. Meanwhile, some standalone scripts have become gargantuan and would be running own downloads of unknown payloads essentially having the user run unknown and remotely updated code at any time. It is also the system that will take care of removing package, including - if requested - its configuration. Nothing is left behind.

Download and install

TIP Current version of the no-subscription package for Proxmox PVE or PBS is: 0.1.2 - released Apr 1, 2025

If you had installed a previous version, simply install the new one manually 'over' it - it will be taken care of well, courtesy of Debian.

Please check for open issues before installation. Do not hesitate to file a new issue when found by yourself, of course.

You can download a package just like any other file, directly onto your host, without installing it:

wget -P /tmp https://free-pmx.pages.dev/packages/free-pmx-no-subscription_0.1.2.deb 

WARNING You are always encouraged to audit anything you are about to install on your system first-hand. Checking thoroughly any scripts is vital. Debian packages are no different. Since the package you have just downloaded does NOT contain any binaries, it is as simple as auditing a script. A separate post to assist you with your own audit of a Debian package with this very one as an example is available for your convenience.

Assuming you have already audited the package, trust the origin, or have had it vetted by a trustworthy 3rd party of your choice, you are welcome to install it right way.

Install on Proxmox system

To install the downloaded package:

apt install /tmp/free-pmx-no-subscription_0.1.2.deb 

And just watch the installation.

The repositories:

free-pmx: NO-SUBSCRIPTION REPOSITORIES SETUP Detecting default lists... Disabled original: /etc/apt/sources.list.d/pve-enterprise.list Created new: /etc/apt/sources.list.d/pve-no-subscription.list Disabled original: /etc/apt/sources.list.d/ceph.list Created new: /etc/apt/sources.list.d/ceph-no-subscription.list Completed total 2 of 2. Checking for Proxmox release key (bookworm) ... already present: pub rsa4096 2022-11-27 [SC] [expires: 2032-11-24] F4E136C67CDCE41AE6DE6FC81140AF8F639E0C39 uid Proxmox Bookworm Release Key <proxmox-release@proxmox.com> sha512 7da6fe34168adc6e479327ba517796d4702fa2f8b4f0a9833f5ea6e6b48f6507a6da403a274fe201595edc86a84463d50383d07f64bdd e2e3658108db7d6dc87 

The nag:

free-pmx: NO VALID SUBSCRIPTION NOTICE REMOVAL Patching: /usr/share/javascript/proxmox-widget-toolkit/proxmoxlib.js Patch successfully applied. 

And the manual pages:

Processing triggers for man-db (2.11.2-2) ... 

Done. You would also notice the same happening during later updates when the tool needs to intercept updated files from Proxmox.

On an existing Proxmox system, this will do everything you need upon the install already: - set up no-subscription repository; and - remove no-subscription popup.

It is still up to you to perform an update / upgrade - as it is your choice when and how, e.g. from GUI.

TIP If you are looking for the effects of GUI changes right after install, you may need to clean your browser cache. If unsure, access the GUI from alternative browser (which cannot have it cached) to rule out a caching problem.

Install on plain Debian

If you are performing an install of top of Debian, you can install this package first, but it will not know which Proxmox product you are about to install, so you have to manually ask it to auto-configure your system for the desired repository, then proceed with installation of the Proxmox product, e.g.:

free-pmx-no-subscription pbs apt update apt install proxmox-backup-server 

This means that you do NOT have to set up the repositories manually, you also do NOT have to download Proxmox release key - it is downloaded from Proxmox servers, but you can certainly manually check its SHA512 fingerprint as published on their website - it will be displayed by the tool.

Removal

To remove the package:

apt remove free-pmx-no-subscription 

TIP Standard apt behaviour on remove is to keep the configuration file - in this case in /etc/free-pmx. This is convenient when package is then reinstalled. Use purge instead to remove the configuration files as well.

That's all - no skeletons in the wardrobe left behind.

Configuration

If you want to configure the basic behaviour further, there is a rudimentary configuration file /etc/free-pmx/no-subscription.conf:

FREE_PMX_NO_SUBSCRIPTION=auto # auto | manual | prohibit FREE_PMX_NO_NAG=auto # auto | manual | prohibit FREE_PMX_CEPH=quincy # actual release name, e.g. quincy, reef, squid 

TIP If you intend to NOT have the package auto-configure itself during install with the default configuration, just create the configuration file with your own options set before install. Check the manual pages for more details on the options.

Usage

There are two simple user commands available:

free-pmx-no-subscription

Standalone tool which is also triggered if the repository lists were to be reinstalled, or more likely - installed, such on a plain Debian system. It simply creates correct 'no-subscription' repository lists and puts aside the original ones.

Configuration options can be explored in the manual page of free-pmx-no-subscription.

free-pmx-no-nag

Standalone tool which can (and will) be triggered whenever Proxmox update their UI toolkit - makes sure the file is patched for the pesky nag popup. It makes a backup of the original, calculates checksums before and after the patch and thus knows if it was effective.

Configuration options can be explored in the manual page of free-pmx-no-nag.

Feedback welcome

Feedback is very welcome in the GitHub repository of free-pmx-no-subscription.

Hello everyone,

I'm looking for a simple project planner to book my team at work on specific projects for each day.
My team work on several clients. I need to book my teammate on project and to be able to quickly glance at the planning to see what's everyone's week will be like.
Some people already told me to use a calendar app but that's just too much hassle for my need.
A simple table view with AM/PM per day and per user would suffice.
Do you have any recommendation on an app that would do that ?

I'm about 3 months into my homelab/self-hosting journey and I'm seeking some advice / perspectives from those with more experience.

My use case: A photo storage and viewing/sharing solution

Feature requirements:

• Auto-backup photos and videos from iPhone
• Stored in human-readable folder structures on my nas, ideally sorted by date/time
• View in user-friendly web interface or other that allows search, filtering
• Manage photos via web interface or other to handle duplicates, deletion of unneeded photos, etc.
• Eventually (not right away) expose to web for sharing photos / videos via link
• Backup to my Proxmox backup server and a cloud location

It's really not that wild, I know, and I think Immich does nearly all of it, but I'm hitting a snag. Originally, I planned to use immich bind mounted to my nas but got scared off during testing by the non-human-readable folder structure it was creating in my nas.

Then I thought maybe I can use NextCloud as my auto-backup solution but point Immich there as my viewer. But I'm still at a point in my homelab/self-hosting journey where one extra layer of complexity totally melts my brain and I have trouble thinking through the configuration that makes sense.

Someone with more experience here: Any recommendations? I'm feeling more and more confident I can get it set up, but choosing the route through all the options still intimidates me.

EDIT (more info): I know Immich can link to external libraries, and also do auto-backup, but can it do them at the same time? E.g., auto backup into a pre-determined file schema?

The official requirement is 5V 5A. what the fuck?

i need a power supply on a pinch and im looking at the power supplies in my electronics store

ofc not a single one that i’ve seen supports 5V 5A, i mean its out of spec isn’t it?

Can i use other ones? will i run into issues? i can’t find a power supply that can supply more than 5A on 5V

Hey, I'm a student and relatively new to Docker and virtualization, and I'm hoping someone here can offer some guidance on an issue I'm encountering. I'm running Proxmox as my hypervisor and have several Windows VMs set up for a personal project involving Docker. Here's the breakdown of the Windows versions and the problems I'm facing: * Windows 10 Pro: Works perfectly fine. Docker with WSL are installed and running without any issues. * Windows 10 Enterprise: I have installed Docker with WSL. However, when I try to run Docker, It says stopping docker engine and I get an "unexpected WSL error". * Windows 11 Pro: After installing Docker with WSL, this VM experiences automatic restarts whenever I shut it down. I've had to force-stop the VM from Proxmox. * Windows 11 Enterprise: Similar to Windows 11 Pro, this VM also automatically restarts after installing Docker. I'm not sure why these inconsistencies are happening across the different Windows versions. I understand that auto-restart can be a feature in some scenarios, but since this is a personal project and doesn't need to be running 24/7, I'd like to disable it if that's the cause. Here are some additional details: * In every OS, I have manually tried to update WSL through PowerShell. * I've checked event logs after the restart under the system category, and I found the error 'The l1vhlwf service failed to start due to the following error: A hypervisor feature is not available to the user'. (This error only appears in Win 11 Pro & Win 11 Enterprise.) * I have also turned on 'Hyper-V' and 'Hypervisor Platform' in the Windows Features on all OS. Has anyone else experienced similar issues with Docker on these specific Windows versions within a Proxmox environment? Any ideas on what might be causing the auto-restarts on the Windows 11 VMs or the WSL error on Windows 10 Enterprise? Any suggestions on how to diagnose or fix these problems would be greatly appreciated. Thanks in advance for your help!

I want to separate the RBAC process entirely from my REST API services, currently I have used spring security to validate JWT tokens with Keycloak in my spring boot services. But want to shift it to Nginx with Oauth2 proxy.
I want to know how efficient this approach can be?