When I install qbittorrent via docker, I see this in the docker logs:

qbittorrent-1         | 2024-11-04T15:25:25.201955254Z The WebUI administrator username is: admin
qbittorrent-1         | 2024-11-04T15:25:25.201974066Z The WebUI administrator password was not set. A temporary password is provided for this session: H7ct3xPes

That’s the default admin credentials for the instance. I can then change the login or pw in the UI.

I found the solution. configuration.yaml needed to have the following syntax, with the defined values being true or false (instead of “Detected” or “Not Detected”):

template:
  - binary_sensor:
      - name: "Lounge Presence"
        state: >-
          {% if states('sensor.apollo_mtr_1_cca750_presence_target_count') | int > 0 %}
            true
          {% elif is_state('binary_sensor.apollo_msr_2_c7bfe8_radar_zone_1_occupancy', 'on') %}
            true
          {% elif is_state('binary_sensor.apollo_msr_2_c7bfe8_radar_zone_2_occupancy', 'on') %}
            true
          {% elif is_state('binary_sensor.apollo_msr_2_c7bfe8_radar_zone_3_occupancy', 'on') %}
            true
          {% else %}
            false
          {% endif %}
        device_class: presence

Thanks for sharing about Backrest. I use Restic and Backrest looks like a great addition to it.

I think Studio Code Server is a linter. It’s telling me what the syntax problems are - I just don’t know how to fix them. Now that I removed the hypehn, it’s not telling me there are any spacing/formatting issues. But it currently says I’m missing the “entities” and “platform” properties, but I don’t know what the values should be. And It also says “state” is not an allowed property, but that’s the property that holds all the important stuff about this sensor - so how can I remove it?

What I did was de-indent the binary_sensor section so it was at the same heirarchy as the template section, like this:

But I realize now that I have to remove the hypen before “binary_sensor”. When I do, I Studio Code Server still shows a couple errors:

It says I’m missing the “entities” and “platform” properties, and that “state” is not an allowed property.

Thanks for the suggsetion @Matt The Horwood.

It looks like a “Combine the state of several sensors” or a “Group” helper only allow you to combine sensors of the same type.

I created a binary sensor from a template using the helper, but it also returns “‘binary_sensor’ is undefined” when I try to access its value in the template editor with {{ states(binary_sensor.lounge_presence) }}

If any of these 4 things happen, set the sensor to “Detected”, otherwise set it to “Not Detected”:

1. MTR presence target count is greater than 0 (zero)
2. MSR zone 1 occupancy is “on”
3. MSR zone 2 occupancy is “on”
4. MSR zone 3 occupancy is “on”

As I said, this is working correctly in the template editor. The problem is that I can’t make a sensor out of it.

Thanks for the suggestion, @NeoNachtwaechter.

But doing that makes configuration.yaml invalid:

I should add the d.rymcg.tech includes step-ca if you want to host your own CA server, but I agree with @[email protected] : it’s not necessary for securely hosting services, and ir can be dangerous I’d not done carefully.

I have a similar setup. I use d.rymcg.tech (a configuration manager for Docker, as well as a collection of open source web services and config templates) and have Traefik (reverse proxy) on a Digital Ocean dropet connected to a VM in my home lab through wireguard. This framework allows me to put authentication and authoriation in front of any apps/services I’m hosting (HTTP basic auth, oauth2, mTLS). This setup allows me to control what is allowed access from outside of my home, without opening any ports.

Glances?

I self-host xBrowserSync. It’s a bookmark sync tool, not a link manager, but it does that very well (set-and-forget - it’s almost invisible). There are browser extensions and mobile apps

I’ve also used Shaarli, which is more of a link sharing tool. Don’t remember much about it, though - sorry.

I think most of the other suggestions seem like a better solution than WordPress, but there is a plugin for WordPress that exports static websites.

I don’t think you’re correct.

• Richard Nixon (1969–1974)
• Gerald Ford (1974–1977)
• Jimmy Carter (1977–1981)
• Ronald Reagan (1981–1989)
• George H. W. Bush (1989–1993)
• Bill Clinton (1993–2001)
• George W. Bush (2001–2009)
• Barack Obama (2009–2017)
• Donald Trump (2017–2021)
• Joe Biden (2021–present)

I run MiniO in Docker. Love it. I’ve never used Garage or Seaweed.

[SOLVED!] That Stack Exchange post was the solution! I had to ask ChatGPT for assistance (e.g., “how do I view the contents of a .crt and a .p12?”, “how do I add a CA to a client cert?”), but it worked. Thanks for your help, @[email protected].

I don’t think I would have ever thought that my client cert didn’t contain the CA, especially because when I clicked on the client cert that was installed in GrapheneOS, it showed me a summary that said it did contain a CA! grrrr

(tagging @[email protected] as he wanted to know the solution)

Wow! That sounds exactly like my issue. I’ll try the workaround tomorrow. Thanks, @[email protected].

Thanks for your research and the suggestion, @[email protected].

I wasn’t able to make that work, but I don’t think it was trying to solve the problem I’m having, anyway. That procedure was to add self signed SSL certificate to Android, but my certificate is neither self-signed nor an SSL cert. At least I think not - I find certs very confusing. The cert I’m trying to work with is an mTLS cert, a client cert. It’s not used to establish a secure SSL connections, it’s used to verify that I (the person with the cert) and authorized to use the app.

Additionally, I’m able to successfully install the cert into Android, but the problem is that it seems to be ignored. The mTLS cert is installed in GrapheneOS’s “VPN & App User Certificate” section, and my CA cert is installed in the “CA Certificate” section. Vanadium, Fennec, and Mull browsers just aren’t using them. :(

Thanks for the reply, @[email protected].

I tried to install my client cert in “CA Certificate” but the certificate manager app in GrapheneOS said that it was the wrong kind of cert to be used in “CA Certificate”. It is, after all, a client cert, not a CA cert.

:(

All of these replies made me feel a little bit better, but yours especially resonated with me. Thanks.