I use win only at work anymore, no choice. Update and shut down is the biggest fucking lie. I press it every time, it never did shut down.

Hi! If you share recipes, make them https://schema.org/ compliant, I think it’s a pre-requisite to be able to import them for example to Nextcloud Cookbook! :D

(I’m not sure, I just read about it earlier this week and did not dig further, yet)

Of course we can win against politicians who we pay but don’t listen to us. At some point, this is not democracy anymore, and if this is not democracy anymore, then the people is going to express itself through non-democratic measures. Just saying.

Until then, we have work to do: convince friends, family, politicians. Expose lobbyist, corporations. Support education, spread knowledge.

The hub is running as follow:

services:
  ...
  hub:
    ports:
      - "myportbehindreverseproxy:8080"
  ...

That way I had to change as less as possible and just setup a quick reverse proxy. I 100% followed the steps from the README.md in Github for the quick start guide, so this was all wizard and honeywire apply. 3306 was the already occupied port, occupied by a native program, not a container.

Yes I used the wizard, which is very neat. Yeah, during the setup, all occupied ports are listed, including the one which was already occupied but nevertheless got used by one of the tcp tarpit decoys.

Now I just moved that decoys port (just did +1, I hope that doesn’t matter) from the UI which correctly changed the honeywire-compose.yml file. Now it seems to be running properly, and firedrill triggers the notifications.

I think you are right on the compose up crash upon port occupied.

It doesn’t matter if Github is more convenient, I, for example, am straight banned from it with no possibility to sign-up. Issue with arkoselabs not working from my ip/device, which is required to complete captcha for signup, and the support is non existent, see this post.

Ok, issue is clear: tcp-tarpit is trying to use an already occupied port. I was not sure how to check the containers log, your command was correct.

Yes, I was trying to deploy everything on the same machine as starter.

I found that I could change the port from the hub, under fleet management, now it seems to work.

I still don’t get why the hub stopped working though. Cpntainer log is only showing from the last start.

Hi.

hw-sensor-tcp-tarpit crashes and that stops also the hub. I don’t know how to check the logs for that container.

I can’t open issues or anything on Github (this the reminder for every foss project participant: please use an alternative to github).

“Leave your tyre pressure sensors at home!”

Hahaha so true. At least the struggling part. I spent a lot of time before getting my things running smoothly, but hei I was a full beginner. It 's not that I don’t dare too ask, it’s just that usually I try hard to find a solution before asking and mostly get it working. But yeah, that’s many hours of setup.

Last paragraph: definitely.

Btw, I don’t remember where, but the compose file do exist somewhere on the system.

Even though I made a mistake. Happy to help!

If you can’t modify the compose file, you can try editing the container with Portainer. There you can change the network of gluetun qbittorrent to “container” and select gluetun.
That’s how I did it when I was running CasaOS.

I should do that because I always type

pwgen 1 32

first and then

pwgen 32 1

… or wait, was it the other way around?

yes I’m that open source guy.

Yet you host your code on Github. Just want to let you know that some of us are simply banned from Github.

• 92% of the 1,500+ projects I follow via selfh.st/apps host their source code on GitHub

Proceeds to share the Endurain github which is a mirror from codeberg. 😄

You made me click the link to see the pictures on the site. The page is so long now my thumb is bleeding from scrolling.

(OP is 100% slop though)

In a previous post, someone pointed out it does not help much saying what PCIe stands for without a short explanation.

I don’t use autocomplete or autocorrect so for me it’s keyboard as usual in the terminal. Actually I use unexpected keyboard, it runs very well with ctrl, tab etc. Not so nice for writing a lot and fast though. But that’s okay, that’s not my style anyway.

I feel that I have a better control over my stack since my new setup (debian). Anyway casaos is very limited in the end, I can’t control anything outside docker from it e.g. nginx, certbot, cronjobs, files, search… But it sure was a very good introduction to self-hosting! That’s actually how I got started with docker.

All the time. Actually that’s my main interacting with the server.

Portainer mobile UI is shit/non-existent: it’s as the desktop site, you need a lot of zoom in and out, but I actually rarely use it. It’s useful in the beginning to check containers’ status, IP and port distribution and such.

I moved from CasaOS to… debian. Once you have the tools in place (e.g. Portainer for docker control, Gethomepage for status, termux on your phone for ssh…) CasaOS has no added value. On the contrary I find it pollutes my docker-compose files.