Exactly. I moved to Jellyfin because Emby introduced the life time support thing
Exactly. I moved to Jellyfin because Emby introduced the life time support thing
I’m not sure what the right model is to get money flowing in. It seems like they took the easy route. 100 dollars for a server licence is not really that small amount considering that most server users are families? I would have preferred massive fund raising campaigns … I’m a bit lazy and need lots of nagging to get my credit card out … But its right these guys get some income for their work. As long as code remains AGPL … I bet soon there will be a fork like happened with Emby. I ended up purchasing the server licence a a few month later moved to the forked version …🙂
DEC740
Very nice but looks expensive. Do you think I could upload the pfSense configuration to it? I dread the pain of having to configure the whole thing from scratch.
I dont’ have IDS/IPS installed on my pfsense box.
Any more specific recomendation of the machine you have running?
sudo ethtool enp2s0 | egrep ‘Speed|Duplex’
Assuming you mean running these in the command prompt of pfSense? Tried but says “not found”. Same for “ip link”
I probably didn’t realise how CPU intensive the work of 1Gbit connection must be …
Yes, checked and are all on the 1000M (1G) link
Any thoughts on a good little fanless device that I can use as a pfSense machine that has a resonable CPU. I would just swap the SSD from my curent device to the new one and it should all work nicely.
Ok, starting to think I need a new little device for my pfSense. I was thinking of going OpenSense and buying one of their devices to support the project.
Regarding my switch, the ports where my Rukus APs are connected are showing 1000M on the interface. But I think a step by step testing is what is needed as suggested above.
This is an intersting thread because I read through the lines the concerns that many have about losing parts of their homelab. Something I too am concerned about. While I have learnt to put my data securely on NAS with docker compose (I.e. docker image runs on VM while data i s stored on NAS and nas dataset is mounted via NFS on VM), in still not clear ho I save the config on the docker container. Basicalky, if I want to move that docker image to a new VM, how do I go about it?
I’m also looking into this a bit as I’m ditching Nextcloud and need a more modulare approach to managing the three things i care about: calendards, files and bookmarks. Sorted calendars with Radicale (superb) and files with Syncthing but now looking at the bookmarks. This (https://github.com/awesome-selfhosted/awesome-selfhosted?tab=readme-ov-file#bookmarks-and-link-sharing) has several solutions proposed. lingding and linkwarden seem to be good and reasonable active on Github. Anyone compared these?
ss -tlnp
Yes, it returning the right address:port 192.168.0.2:5234
but as I said earlier, the problem was me mis-spelling the config folder so it was ignoring the config file.
Turned out I had created /etc/radical
rather than /etc/radicale
and of course the app was looking for a folder that didn’t exist. I can confirm the above procedure works for anyone trying to install it.
Ok, removed the conflicting bit but it made no difference. I wonder if this is to do with ‘radicale’ user not being able to open ports or something like that …?
Thanks. I’ll give this a try over the weekend since it appears to have worked for others. This is something I would have expected the developers to have implemented. Multiuser computers is not that rare …
Server is Truenas Scale. Syncthing is running as app. I and wife have it installed on Android phones. We both share a Debian 12 laptop with different logins. We both want to keep respective phone synced with laptop login. We want to have a folder shared on nas where we can exchange files.
I actually do have an always on server and I was planning on using it as a client-server type system. I think that the file sharing option is complicated to implement. I tried to launch syncthing in my wifes environment on the laptop and while I get a new ID, when I register it with the server, it complains saying that there are conflicts with the IDs for the device. I wonder if its getting confused by having two IDs against the same IP
Mmm, Seafile is is developed by an for-profit organisation. Looks interesting but might stick with nextcloud if I have to move to Seafile. Syncthing seems really robust and simple. I think its just the file sharing bit that I’m missing. Nextcloud is just a beast.
This thread has reminded me that I have Ruckus APs that mesh. But support had been dropped because they are “old”. Presumably there is no open source solution that I can flsh these with, still allowing me the meshing?