home.social

#archlinuxarm — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #archlinuxarm, aggregated by home.social.

  1. Alanna 🏳️‍🌈🏳️‍⚧️ @[email protected] ·

    Well, that was an interesting adventure in electronics! This took about 3 days, but I finally got serial terminal output with one of the Dragonboard 410c I got given as junk! An interesting process, including making my own 1.8V USB->Serial on a breadboard with a level shifter! I finally got the bootloader up!

    #electronics #dragonboard410c #archlinuxarm #breadboard

    #electronics #dragonboard410c #archlinuxarm #breadboard
  2. LINux on MOBile @[email protected] ·

    Weekly GNU-like #MobileLinux Update (10/2026): Slow Spring

    https://linmob.net/weekly-update-10-2026/

    #Phosh #SailfishOS #Jolla #UbuntuTouch #postmarketOS #Mobian #ArchLinuxARM #Catacomb #LinuxMobile #PinePhone #Librem5 #FuriLabsFLX1

    #mobilelinux #phosh #sailfishos #jolla #ubuntutouch #postmarketos
  3. Peter Vágner @[email protected] ·

    Perhaps you remember I am occassionally running #emacs on android with speechd-el and espeak-ng providing speech output. Up to now I was using termux for doing that.
    Now I'm trying to get it to run on a pixel 9A with @GrapheneOS and the terminal app with #avf under the hood.

    The thing is I'd like to get more up to date packages in that virtualized environment running on my phone. I'd prefer #ArchLinuxARM based image or #Debian testing. Upgrading it by following debian's instructions I am getting broken image. I have found there's nixos-avf however I can't find more.

    Do you know if someone has succeeded building other images that might help me to get to my goal easier?

    #emacs #debian #archlinuxarm #avf
  4. Peter Vágner @[email protected] ·

    Perhaps you remember I am occassionally running #emacs on android with speechd-el and espeak-ng providing speech output. Up to now I was using termux for doing that.
    Now I'm trying to get it to run on a pixel 9A with @GrapheneOS and the terminal app with #avf under the hood.

    The thing is I'd like to get more up to date packages in that virtualized environment running on my phone. I'd prefer #ArchLinuxARM based image or #Debian testing. Upgrading it by following debian's instructions I am getting broken image. I have found there's nixos-avf however I can't find more.

    Do you know if someone has succeeded building other images that might help me to get to my goal easier?

    #emacs #debian #archlinuxarm #avf
  5. Peter Vágner @[email protected] ·

    Perhaps you remember I am occassionally running #emacs on android with speechd-el and espeak-ng providing speech output. Up to now I was using termux for doing that.
    Now I'm trying to get it to run on a pixel 9A with @GrapheneOS and the terminal app with #avf under the hood.

    The thing is I'd like to get more up to date packages in that virtualized environment running on my phone. I'd prefer #ArchLinuxARM based image or #Debian testing. Upgrading it by following debian's instructions I am getting broken image. I have found there's nixos-avf however I can't find more.

    Do you know if someone has succeeded building other images that might help me to get to my goal easier?

    #avf #archlinuxarm #debian #emacs
  6. Lanie @[email protected] ·

    Any Tintin++ users out there willing to share tips? This is the only #MUD client I can get working on #Stormux, and to be honest, the scripting just to add a simple trigger and the error messages are confusing to me. I'm trying to set up some simple triggers for Erion MUD and having a hard time figuring out what I'm doing.
    #MUDClients #MUDClient #tintin #orca #ScreenReader #Linux #archlinuxarm @mastoblind @main

    #mud #stormux #mudclients #mudclient #tintin #orca
  7. Lanie @[email protected] ·

    Any Tintin++ users out there willing to share tips? This is the only #MUD client I can get working on #Stormux, and to be honest, the scripting just to add a simple trigger and the error messages are confusing to me. I'm trying to set up some simple triggers for Erion MUD and having a hard time figuring out what I'm doing.
    #MUDClients #MUDClient #tintin #orca #ScreenReader #Linux #archlinuxarm @mastoblind @main

    #mud #stormux #mudclients #mudclient #tintin #orca
  8. Lanie @[email protected] ·

    Any Tintin++ users out there willing to share tips? This is the only #MUD client I can get working on #Stormux, and to be honest, the scripting just to add a simple trigger and the error messages are confusing to me. I'm trying to set up some simple triggers for Erion MUD and having a hard time figuring out what I'm doing.
    #MUDClients #MUDClient #tintin #orca #ScreenReader #Linux #archlinuxarm @mastoblind @main

    #mud #stormux #mudclients #mudclient #tintin #orca
  9. Lanie @[email protected] ·

    Any Tintin++ users out there willing to share tips? This is the only #MUD client I can get working on #Stormux, and to be honest, the scripting just to add a simple trigger and the error messages are confusing to me. I'm trying to set up some simple triggers for Erion MUD and having a hard time figuring out what I'm doing.
    #MUDClients #MUDClient #tintin #orca #ScreenReader #Linux #archlinuxarm @mastoblind @main

    #archlinuxarm #linux #screenreader #orca #tintin #mudclient
  10. Lanie @[email protected] ·

    Any Tintin++ users out there willing to share tips? This is the only #MUD client I can get working on #Stormux, and to be honest, the scripting just to add a simple trigger and the error messages are confusing to me. I'm trying to set up some simple triggers for Erion MUD and having a hard time figuring out what I'm doing.
    #MUDClients #MUDClient #tintin #orca #ScreenReader #Linux #archlinuxarm @mastoblind @main

    #mud #stormux #mudclients #mudclient #tintin #orca
  11. Lanie @[email protected] ·

    Question to #blind #linux users: I'm stuck using my #RaspberryPi500 as my computer for a bit because my PC quit working. Can anyone recommend a #Mastodon client? I'm on #Stormux, based on #ArchLinuxArm.
    #accessibility #orca #ScreenReader @mastoblind @main

    #blind #linux #raspberrypi500 #mastodon #stormux #archlinuxarm
  12. Lanie @[email protected] ·

    Question to #blind #linux users: I'm stuck using my #RaspberryPi500 as my computer for a bit because my PC quit working. Can anyone recommend a #Mastodon client? I'm on #Stormux, based on #ArchLinuxArm.
    #accessibility #orca #ScreenReader @mastoblind @main

    #blind #linux #raspberrypi500 #mastodon #stormux #archlinuxarm
  13. Lanie @[email protected] ·

    Question to #blind #linux users: I'm stuck using my #RaspberryPi500 as my computer for a bit because my PC quit working. Can anyone recommend a #Mastodon client? I'm on #Stormux, based on #ArchLinuxArm.
    #accessibility #orca #ScreenReader @mastoblind @main

    #blind #linux #raspberrypi500 #mastodon #stormux #archlinuxarm
  14. Lanie @[email protected] ·

    Question to #blind #linux users: I'm stuck using my #RaspberryPi500 as my computer for a bit because my PC quit working. Can anyone recommend a #Mastodon client? I'm on #Stormux, based on #ArchLinuxArm.
    #accessibility #orca #ScreenReader @mastoblind @main

    #screenreader #orca #accessibility #archlinuxarm #stormux #mastodon
  15. Lanie @[email protected] ·

    Question to #blind #linux users: I'm stuck using my #RaspberryPi500 as my computer for a bit because my PC quit working. Can anyone recommend a #Mastodon client? I'm on #Stormux, based on #ArchLinuxArm.
    #accessibility #orca #ScreenReader @mastoblind @main

    #blind #linux #raspberrypi500 #mastodon #stormux #archlinuxarm
  16. 0mega @[email protected] ·

    Falls ihr auch gerade mal wieder #ArchLinuxARM bzw. DanctNIX auf dem #Pinephone Pro ausprobieren wollt und euch wundert, warum die Kamera nicht funktioniert: #Pipewire & Co. sind eure neuen Freunde der Bildaufzeichnung und die entsprechenden Pakete scheinen nicht vorinstalliert zu sein. Megapixels läuft nicht OOTB und Snapshot benötigt mindestens noch gst-plugin-libcamera.

    Jetzt muss ich nur noch herausfinden, warum Snapshot crasht, wenn es das Bild abspeichert.

    #archlinuxarm #pinephone #pipewire
  17. LINux on MOBile @[email protected] ·

    Just something I just stumbled upon:

    https://github.com/ZXlieC/alarm-mobile

    (Can't try it, don't have the hardware.)
    #LinuxMobile #ArchLinuxARM

    #linuxmobile #archlinuxarm
  18. Kelson @[email protected] ·

    Is anyone here active on the #ArchLinux or #ArchLinuxArm forums? I've been trying off and on to register for both for a few weeks, and can't get an email confirmation from either of them. I'd contact the admins, but you have to be logged in to see the admin contact info.

    I emailed the site contacts I could find, but never got a response to those messages either. I have no way of knowing whether they just haven't replied yet, or the replies got lost, or whether my emails got deliberately ignored because I was emailing someone other than the forum admins.

    #archlinux #archlinuxarm
  19. The one with the headscarf 🧕🏽 @[email protected] ·

    Uuuuugh, my #IntelliJ port for #ArchLinux on #AArch64 #ArchLinuxArm finally landed 🤩 ! archlinuxarm.org/packages/aarc

    #intellij #archlinux #aarch64 #archlinuxarm
  20. [Nima@NimaOS ~]# @[email protected] ·

    @phosh
    Arch Linux ARM is still on Phosh 0.44!

    I've tried to contact them on their IRC, their forum etc, but they seem to not care.
    I also have talked with people at kupfer but they seem to not have much contact with them as well.

    #LinuxMobile #ArchLinux #ArchLinuxARM

    #linuxmobile #archlinux #archlinuxarm
  21. Lanie @[email protected] ·

    To people who use #HomeAssistant, do you need #NodeRed to get the most out of it? Found this guide to setting up HomeAssistant in #Docker that helped me get both installed, but Node-Red's interface is pretty much unusable with a #ScreenReader, and I'm thinking of uninstalling it.
    #SelfHosting #SelfHosted #RaspberryPi #RaspberryPi500 #RPi #RPi500 #Linux #Stormux #ArchLinuxARM
    @selfhosting @selfhost @selfhosted

    #homeassistant #nodered #docker #screenreader #selfhosting #selfhosted
  22. Lanie @[email protected] ·

    To people who use #HomeAssistant, do you need #NodeRed to get the most out of it? Found this guide to setting up HomeAssistant in #Docker that helped me get both installed, but Node-Red's interface is pretty much unusable with a #ScreenReader, and I'm thinking of uninstalling it.
    #SelfHosting #SelfHosted #RaspberryPi #RaspberryPi500 #RPi #RPi500 #Linux #Stormux #ArchLinuxARM
    @selfhosting @selfhost @selfhosted

    #homeassistant #nodered #docker #screenreader #selfhosting #selfhosted
  23. Lanie @[email protected] ·

    To people who use #HomeAssistant, do you need #NodeRed to get the most out of it? Found this guide to setting up HomeAssistant in #Docker that helped me get both installed, but Node-Red's interface is pretty much unusable with a #ScreenReader, and I'm thinking of uninstalling it.
    #SelfHosting #SelfHosted #RaspberryPi #RaspberryPi500 #RPi #RPi500 #Linux #Stormux #ArchLinuxARM
    @selfhosting @selfhost @selfhosted

    #homeassistant #nodered #docker #screenreader #selfhosting #selfhosted
  24. Lanie @[email protected] ·

    To people who use #HomeAssistant, do you need #NodeRed to get the most out of it? Found this guide to setting up HomeAssistant in #Docker that helped me get both installed, but Node-Red's interface is pretty much unusable with a #ScreenReader, and I'm thinking of uninstalling it.
    #SelfHosting #SelfHosted #RaspberryPi #RaspberryPi500 #RPi #RPi500 #Linux #Stormux #ArchLinuxARM
    @selfhosting @selfhost @selfhosted

    #archlinuxarm #stormux #linux #rpi500 #rpi #raspberrypi500
  25. Lanie @[email protected] ·

    To people who use #HomeAssistant, do you need #NodeRed to get the most out of it? Found this guide to setting up HomeAssistant in #Docker that helped me get both installed, but Node-Red's interface is pretty much unusable with a #ScreenReader, and I'm thinking of uninstalling it.
    #SelfHosting #SelfHosted #RaspberryPi #RaspberryPi500 #RPi #RPi500 #Linux #Stormux #ArchLinuxARM
    @selfhosting @selfhost @selfhosted

    #homeassistant #nodered #docker #screenreader #selfhosting #selfhosted
  26. Lanie @[email protected] ·

    Wondering if I should switch my #RaspberryPi OS from #Stormux, based on #ArchLinuxARM, to #HomeAssistantOS. I mostly work with it over SSH anyway and this might allow me to do more with it. What do others who #SelfHost think?
    #SelfHosting #SelfHosted #Linux
    @selfhost @selfhosting @selfhosted

    #raspberrypi #stormux #archlinuxarm #homeassistantos #selfhost #selfhosting
  27. Lanie @[email protected] ·

    Wondering if I should switch my #RaspberryPi OS from #Stormux, based on #ArchLinuxARM, to #HomeAssistantOS. I mostly work with it over SSH anyway and this might allow me to do more with it. What do others who #SelfHost think?
    #SelfHosting #SelfHosted #Linux
    @selfhost @selfhosting @selfhosted

    #raspberrypi #stormux #archlinuxarm #homeassistantos #selfhost #selfhosting
  28. Lanie @[email protected] ·

    Wondering if I should switch my #RaspberryPi OS from #Stormux, based on #ArchLinuxARM, to #HomeAssistantOS. I mostly work with it over SSH anyway and this might allow me to do more with it. What do others who #SelfHost think?
    #SelfHosting #SelfHosted #Linux
    @selfhost @selfhosting @selfhosted

    #raspberrypi #stormux #archlinuxarm #homeassistantos #selfhost #selfhosting
  29. Lanie @[email protected] ·

    Wondering if I should switch my #RaspberryPi OS from #Stormux, based on #ArchLinuxARM, to #HomeAssistantOS. I mostly work with it over SSH anyway and this might allow me to do more with it. What do others who #SelfHost think?
    #SelfHosting #SelfHosted #Linux
    @selfhost @selfhosting @selfhosted

    #linux #selfhosted #selfhosting #selfhost #homeassistantos #archlinuxarm
  30. Lanie @[email protected] ·

    Wondering if I should switch my #RaspberryPi OS from #Stormux, based on #ArchLinuxARM, to #HomeAssistantOS. I mostly work with it over SSH anyway and this might allow me to do more with it. What do others who #SelfHost think?
    #SelfHosting #SelfHosted #Linux
    @selfhost @selfhosting @selfhosted

    #raspberrypi #stormux #archlinuxarm #homeassistantos #selfhost #selfhosting
  31. Lanie @[email protected] ·

    I'm curious to hear what others are #SelfHosting! Here's my current setup:

    Hardware & OS

    Infrastructure & Networking

    Security & Monitoring

    Authentication & Identity Management

    • Authelia (Docker): Just set this up for two-factor authentication and single sign-on. Seems to be working well so far!
    • LLDAP (Docker): Lightweight LDAP server for managing authentication. Also seems to be working pretty well!
      #AuthenticationTools #IdentityManagement

    Productivity & Personal Tools

    Notifications & Development Workflow

    • Notifications via: #Ntfy (Docker) and Zoho's ZeptoMail (#Zoho)
    • Development Environment: Mostly using VSCode connected to my server via Remote-SSH extension. #VSCodeRemote

    Accessibility Focus ♿️🖥️

    Accessibility heavily influences my choices—I use a screen reader full-time (#ScreenReader), so I prioritize services usable without sight (#InclusiveDesign, #DigitalAccessibility). Always open to discussing accessibility experiences or recommendations!

    I've also experimented with:

    • Ollama (#Ollama): Not enough RAM on my Pi.
    • Habit trackers like Beaver Habit Tracker (#HabitTracking): Accessibility issues made it unusable for me.

    I don't really have a media collection, so no Plex or Jellyfin here (#MediaServer)—but I'm always open to suggestions! I've gotten a bit addicted to exploring new self-hosted services! 😄

    What's your setup like? Any cool services you'd recommend I try?

    #SelfHosted #LinuxSelfHost #OpenSource #TechCommunity #FOSS #TechDIY

    @selfhost @selfhosted @selfhosting

    #selfhosting #raspberrypi500 #rpi #rpi500 #singleboardcomputers #homelab
  32. Lanie @[email protected] ·

    I'm curious to hear what others are #SelfHosting! Here's my current setup:

    Hardware & OS

    Infrastructure & Networking

    Security & Monitoring

    Authentication & Identity Management

    • Authelia (Docker): Just set this up for two-factor authentication and single sign-on. Seems to be working well so far!
    • LLDAP (Docker): Lightweight LDAP server for managing authentication. Also seems to be working pretty well!
      #AuthenticationTools #IdentityManagement

    Productivity & Personal Tools

    Notifications & Development Workflow

    • Notifications via: #Ntfy (Docker) and Zoho's ZeptoMail (#Zoho)
    • Development Environment: Mostly using VSCode connected to my server via Remote-SSH extension. #VSCodeRemote

    Accessibility Focus ♿️🖥️

    Accessibility heavily influences my choices—I use a screen reader full-time (#ScreenReader), so I prioritize services usable without sight (#InclusiveDesign, #DigitalAccessibility). Always open to discussing accessibility experiences or recommendations!

    I've also experimented with:

    • Ollama (#Ollama): Not enough RAM on my Pi.
    • Habit trackers like Beaver Habit Tracker (#HabitTracking): Accessibility issues made it unusable for me.

    I don't really have a media collection, so no Plex or Jellyfin here (#MediaServer)—but I'm always open to suggestions! I've gotten a bit addicted to exploring new self-hosted services! 😄

    What's your setup like? Any cool services you'd recommend I try?

    #SelfHosted #LinuxSelfHost #OpenSource #TechCommunity #FOSS #TechDIY

    @selfhost @selfhosted @selfhosting

    #selfhosting #raspberrypi500 #rpi #rpi500 #singleboardcomputers #homelab
  33. Lanie @[email protected] ·

    I'm curious to hear what others are #SelfHosting! Here's my current setup:

    Hardware & OS

    Infrastructure & Networking

    Security & Monitoring

    Authentication & Identity Management

    • Authelia (Docker): Just set this up for two-factor authentication and single sign-on. Seems to be working well so far!
    • LLDAP (Docker): Lightweight LDAP server for managing authentication. Also seems to be working pretty well!
      #AuthenticationTools #IdentityManagement

    Productivity & Personal Tools

    Notifications & Development Workflow

    • Notifications via: #Ntfy (Docker) and Zoho's ZeptoMail (#Zoho)
    • Development Environment: Mostly using VSCode connected to my server via Remote-SSH extension. #VSCodeRemote

    Accessibility Focus ♿️🖥️

    Accessibility heavily influences my choices—I use a screen reader full-time (#ScreenReader), so I prioritize services usable without sight (#InclusiveDesign, #DigitalAccessibility). Always open to discussing accessibility experiences or recommendations!

    I've also experimented with:

    • Ollama (#Ollama): Not enough RAM on my Pi.
    • Habit trackers like Beaver Habit Tracker (#HabitTracking): Accessibility issues made it unusable for me.

    I don't really have a media collection, so no Plex or Jellyfin here (#MediaServer)—but I'm always open to suggestions! I've gotten a bit addicted to exploring new self-hosted services! 😄

    What's your setup like? Any cool services you'd recommend I try?

    #SelfHosted #LinuxSelfHost #OpenSource #TechCommunity #FOSS #TechDIY

    @selfhost @selfhosted @selfhosting

    #selfhosting #raspberrypi500 #rpi #rpi500 #singleboardcomputers #homelab
  34. Lanie @[email protected] ·

    I'm curious to hear what others are #SelfHosting! Here's my current setup:

    Hardware & OS

    Infrastructure & Networking

    Security & Monitoring

    Authentication & Identity Management

    • Authelia (Docker): Just set this up for two-factor authentication and single sign-on. Seems to be working well so far!
    • LLDAP (Docker): Lightweight LDAP server for managing authentication. Also seems to be working pretty well!
      #AuthenticationTools #IdentityManagement

    Productivity & Personal Tools

    Notifications & Development Workflow

    • Notifications via: #Ntfy (Docker) and Zoho's ZeptoMail (#Zoho)
    • Development Environment: Mostly using VSCode connected to my server via Remote-SSH extension. #VSCodeRemote

    Accessibility Focus ♿️🖥️

    Accessibility heavily influences my choices—I use a screen reader full-time (#ScreenReader), so I prioritize services usable without sight (#InclusiveDesign, #DigitalAccessibility). Always open to discussing accessibility experiences or recommendations!

    I've also experimented with:

    • Ollama (#Ollama): Not enough RAM on my Pi.
    • Habit trackers like Beaver Habit Tracker (#HabitTracking): Accessibility issues made it unusable for me.

    I don't really have a media collection, so no Plex or Jellyfin here (#MediaServer)—but I'm always open to suggestions! I've gotten a bit addicted to exploring new self-hosted services! 😄

    What's your setup like? Any cool services you'd recommend I try?

    #SelfHosted #LinuxSelfHost #OpenSource #TechCommunity #FOSS #TechDIY

    @selfhost @selfhosted @selfhosting

    #techdiy #foss #techcommunity #opensource #linuxselfhost #selfhosted
  35. Lanie @[email protected] ·

    I'm curious to hear what others are #SelfHosting! Here's my current setup:

    Hardware & OS

    Infrastructure & Networking

    Security & Monitoring

    Authentication & Identity Management

    • Authelia (Docker): Just set this up for two-factor authentication and single sign-on. Seems to be working well so far!
    • LLDAP (Docker): Lightweight LDAP server for managing authentication. Also seems to be working pretty well!
      #AuthenticationTools #IdentityManagement

    Productivity & Personal Tools

    Notifications & Development Workflow

    • Notifications via: #Ntfy (Docker) and Zoho's ZeptoMail (#Zoho)
    • Development Environment: Mostly using VSCode connected to my server via Remote-SSH extension. #VSCodeRemote

    Accessibility Focus ♿️🖥️

    Accessibility heavily influences my choices—I use a screen reader full-time (#ScreenReader), so I prioritize services usable without sight (#InclusiveDesign, #DigitalAccessibility). Always open to discussing accessibility experiences or recommendations!

    I've also experimented with:

    • Ollama (#Ollama): Not enough RAM on my Pi.
    • Habit trackers like Beaver Habit Tracker (#HabitTracking): Accessibility issues made it unusable for me.

    I don't really have a media collection, so no Plex or Jellyfin here (#MediaServer)—but I'm always open to suggestions! I've gotten a bit addicted to exploring new self-hosted services! 😄

    What's your setup like? Any cool services you'd recommend I try?

    #SelfHosted #LinuxSelfHost #OpenSource #TechCommunity #FOSS #TechDIY

    @selfhost @selfhosted @selfhosting

    #selfhosting #raspberrypi500 #rpi #rpi500 #singleboardcomputers #homelab
  36. Lanie @[email protected] ·

    #SelfHosted #LinkAce Bookmark Manager Running, but Unable to Check for Updates or Generate a Cron Token

    Hi all. Hoping someone in the #SelfHosting community can help here. I'm running LinkAce in #Docker behind non-Dockerized #Caddy and #Authelia, and most things are working, but I'm seeing "Could not check for updates" at the bottom of each page, and when I tried to generate a cron token, nothing happened except for the generate button graying out. I am seeing one or two 404 errors in my logs, but I don't know if that's causing the problem or not. I don't know much about #PHP applications.

    Logs

    2025-02-22 23:25:26,460 INFO supervisord started with pid 1
    2025-02-22 23:25:27,465 INFO spawned: 'php-fpm' with pid 8
    2025-02-22 23:25:27,467 INFO spawned: 'caddy' with pid 9
    [22-Feb-2025 23:25:27] NOTICE: [pool www] 'user' directive is ignored when FPM is not running as root
    [22-Feb-2025 23:25:27] NOTICE: [pool www] 'group' directive is ignored when FPM is not running as root
    [22-Feb-2025 23:25:27] NOTICE: fpm is running, pid 8
    [22-Feb-2025 23:25:27] NOTICE: ready to handle connections
    {"level":"info","ts":1740266727.5264525,"msg":"using config from file","file":"/etc/caddy/Caddyfile"}
    {"level":"info","ts":1740266727.5280282,"msg":"adapted config to JSON","adapter":"caddyfile"}
    {"level":"warn","ts":1740266727.5280406,"msg":"Caddyfile input is not formatted; run 'caddy fmt --overwrite' to fix inconsistencies","adapter":"caddyfile","file":"/etc/caddy/Caddyfile","line":2}
    {"level":"info","ts":1740266727.529092,"logger":"admin","msg":"admin endpoint started","address":"localhost:2019","enforce_origin":false,"origins":["//localhost:2019","//[::1]:2019","//127.0.0.1:2019"]}
    {"level":"warn","ts":1740266727.529331,"logger":"http.auto_https","msg":"server is listening only on the HTTP port, so no automatic HTTPS will be applied to this server","server_name":"srv0","http_port":80}
    {"level":"info","ts":1740266727.5294206,"logger":"tls.cache.maintenance","msg":"started background certificate maintenance","cache":"0x40000bab00"}
    {"level":"warn","ts":1740266727.530186,"logger":"http","msg":"HTTP/2 skipped because it requires TLS","network":"tcp","addr":":80"}
    {"level":"warn","ts":1740266727.530195,"logger":"http","msg":"HTTP/3 skipped because it requires TLS","network":"tcp","addr":":80"}
    {"level":"info","ts":1740266727.530198,"logger":"http.log","msg":"server running","name":"srv0","protocols":["h1","h2","h3"]}
    {"level":"info","ts":1740266727.5412574,"msg":"autosaved config (load with --resume flag)","file":"/home/www-data/.config/caddy/autosave.json"}
    {"level":"info","ts":1740266727.541271,"msg":"serving initial configuration"}
    {"level":"info","ts":1740266727.5477707,"logger":"tls","msg":"cleaning storage unit","storage":"FileStorage:/home/www-data/.local/share/caddy"}
    {"level":"info","ts":1740266727.5541356,"logger":"tls","msg":"finished cleaning storage units"}
    2025-02-22 23:25:28,555 INFO success: php-fpm entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
    2025-02-22 23:25:28,555 INFO success: caddy entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
    ::1 -  22/Feb/2025:23:25:34 +0000 "GET /index.php" 200
    ::1 -  22/Feb/2025:23:25:34 +0000 "GET /index.php" 404

    Docker Compose file

    services:
      # --- LinkAce
      linkace:
        image: docker.io/linkace/linkace:latest
        container_name: linkace
        restart: unless-stopped
        depends_on:
          - linkace_db
        ports:
          - "0.0.0.0:3009:80"
        volumes:
          - ./.env:/app/.env
          - ./backups:/app/storage/app/backups

      # --- Database
      linkace_db:
        image: docker.io/library/mariadb:11.5
        container_name: linkace_db
        restart: unless-stopped
        command: mariadbd --character-set-server=utf8mb4 --collation-server=utf8mb4_bin
        environment:
          - MYSQL_ROOT_PASSWORD=${DB_PASSWORD}
          - MYSQL_USER=${DB_USERNAME}
          - MYSQL_PASSWORD=${DB_PASSWORD}
          - MYSQL_DATABASE=${DB_DATABASE}
        volumes:
          - db:/var/lib/mysql

      # --- Cache
      linkace_redis:
        image: docker.io/bitnami/redis:7.4
        container_name: linkace_redis
        restart: unless-stopped
        environment:
          - REDIS_PASSWORD=${REDIS_PASSWORD}

    volumes:
      db:

    .env (secrets redacted)

    ## LINKACE CONFIGURATION

    # The app key is generated later, please leave it like that
    APP_KEY=redacted
    APP_ENV=development

    ## Configuration of the database connection
    ## Attention: Those settings are configured during the web setup, please do not modify them now.
    # Set the database driver (mysql, pgsql, sqlsrv, sqlite)
    DB_CONNECTION=mysql
    # Set the host of your database here
    DB_HOST=linkace_db
    # Set the port of your database here
    DB_PORT=3306
    # Set the database name here
    DB_DATABASE=linkace
    # Set both username and password of the user accessing the database
    DB_USERNAME=linkace
    # Wrap your password into quotes (") if it contains special characters
    DB_PASSWORD=redacted

    ## Redis cache configuration
    # Set the Redis connection here if you want to use it
    REDIS_HOST=linkace_redis
    REDIS_PASSWORD=redacted
    REDIS_PORT=6379
    APP_DEBUG=true

    # SSO configuration
    SSO_ENABLED=true
    SSO_OIDC_ENABLED=true
    SSO_REGISTRATION_ENABLED=true
    REGULAR_LOGIN_DISABLED=true
    SSO_OIDC_BASE_URL=https://auth.laniecarmelo.tech/  # Your Authelia base URL
    SSO_OIDC_CLIENT_ID=linkace
    SSO_OIDC_CLIENT_SECRET='redacted'
    SSO_OIDC_SCOPES=openid,profile,email

    Caddyfile snippet

    {
        email [email protected]
        debug
        acme_dns cloudflare redacted
        http_port 80
        https_port 443
        admin :2019 {
            origins 127.0.0.1:2019 0.0.0.0:2019 stormux:2019 caddy.laniecarmelo.tech
        }
    }

    (logconfig) {
        log {
            output stdout
            format json
        }
    }

    (auth_headers) {
        header Strict-Transport-Security "max-age=31536000; includeSubDomains; preload"
    }

    (proxy_config) {
        header_up Host {http.request.host}
        header_up X-Real-IP {http.request.remote}
        header_up X-Forwarded-User {http.auth.user.id} # Pass user ID
        header_up X-Forwarded-Email {http.auth.user.email} # Pass email
    }

    (authelia_middleware) {
        forward_auth localhost:9091 {
            uri /api/verify?rd=https://auth.laniecarmelo.tech
            copy_headers Remote-User Remote-Email Remote-Groups Authorization
        }
    }

    bookmarks.laniecarmelo.tech {
        route {
            import authelia_middleware
            reverse_proxy localhost:3009 {  # Directly proxy to LinkAce's web server
                import proxy_config
            }
        }
        import logconfig
        import auth_headers
    }

    Authelia config snippet

        - domain: "*.laniecarmelo.tech"
          policy: bypass
          networks:
            - 192.168.1.0/24    # Local network
            - 172.17.0.0/16     # Docker bridge network
            - 100.64.0.0/10     # Tailscale network

        - domain: "bookmarks.laniecarmelo.tech"
          resources: ["^/api.*"]
          policy: bypass

        - domain: "*.laniecarmelo.tech"
          policy: one_factor      

          - client_id: linkace
            client_name: LinkAce bookmarking app
            client_secret: redacted
             public: false
            authorization_policy: one_factor
            scopes: [openid, groups, profile, email, offline_access]
            redirect_uris:
              - https://bookmarks.laniecarmelo.tech/auth/oidc/callback
            grant_types: [authorization_code]
            response_types: [code]
            response_modes: [form_post, query]
            userinfo_signed_response_alg: none
            consent_mode: explicit
            pre_configured_consent_duration: "1y"

    Does anyone know what might be causing this and how I can fix it?
    #Linux #ArchLinuxARM #Stormux #RaspberryPi #RaspberryPi500 #RPi #RPi500 #tech #technology
    @selfhost @selfhosted @selfhosting

    #selfhosted #linkace #selfhosting #docker #caddy #authelia
  37. Lanie @[email protected] ·

    #SelfHosted #LinkAce Bookmark Manager Running, but Unable to Check for Updates or Generate a Cron Token

    Hi all. Hoping someone in the #SelfHosting community can help here. I'm running LinkAce in #Docker behind non-Dockerized #Caddy and #Authelia, and most things are working, but I'm seeing "Could not check for updates" at the bottom of each page, and when I tried to generate a cron token, nothing happened except for the generate button graying out. I am seeing one or two 404 errors in my logs, but I don't know if that's causing the problem or not. I don't know much about #PHP applications.

    Logs

    2025-02-22 23:25:26,460 INFO supervisord started with pid 1
    2025-02-22 23:25:27,465 INFO spawned: 'php-fpm' with pid 8
    2025-02-22 23:25:27,467 INFO spawned: 'caddy' with pid 9
    [22-Feb-2025 23:25:27] NOTICE: [pool www] 'user' directive is ignored when FPM is not running as root
    [22-Feb-2025 23:25:27] NOTICE: [pool www] 'group' directive is ignored when FPM is not running as root
    [22-Feb-2025 23:25:27] NOTICE: fpm is running, pid 8
    [22-Feb-2025 23:25:27] NOTICE: ready to handle connections
    {"level":"info","ts":1740266727.5264525,"msg":"using config from file","file":"/etc/caddy/Caddyfile"}
    {"level":"info","ts":1740266727.5280282,"msg":"adapted config to JSON","adapter":"caddyfile"}
    {"level":"warn","ts":1740266727.5280406,"msg":"Caddyfile input is not formatted; run 'caddy fmt --overwrite' to fix inconsistencies","adapter":"caddyfile","file":"/etc/caddy/Caddyfile","line":2}
    {"level":"info","ts":1740266727.529092,"logger":"admin","msg":"admin endpoint started","address":"localhost:2019","enforce_origin":false,"origins":["//localhost:2019","//[::1]:2019","//127.0.0.1:2019"]}
    {"level":"warn","ts":1740266727.529331,"logger":"http.auto_https","msg":"server is listening only on the HTTP port, so no automatic HTTPS will be applied to this server","server_name":"srv0","http_port":80}
    {"level":"info","ts":1740266727.5294206,"logger":"tls.cache.maintenance","msg":"started background certificate maintenance","cache":"0x40000bab00"}
    {"level":"warn","ts":1740266727.530186,"logger":"http","msg":"HTTP/2 skipped because it requires TLS","network":"tcp","addr":":80"}
    {"level":"warn","ts":1740266727.530195,"logger":"http","msg":"HTTP/3 skipped because it requires TLS","network":"tcp","addr":":80"}
    {"level":"info","ts":1740266727.530198,"logger":"http.log","msg":"server running","name":"srv0","protocols":["h1","h2","h3"]}
    {"level":"info","ts":1740266727.5412574,"msg":"autosaved config (load with --resume flag)","file":"/home/www-data/.config/caddy/autosave.json"}
    {"level":"info","ts":1740266727.541271,"msg":"serving initial configuration"}
    {"level":"info","ts":1740266727.5477707,"logger":"tls","msg":"cleaning storage unit","storage":"FileStorage:/home/www-data/.local/share/caddy"}
    {"level":"info","ts":1740266727.5541356,"logger":"tls","msg":"finished cleaning storage units"}
    2025-02-22 23:25:28,555 INFO success: php-fpm entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
    2025-02-22 23:25:28,555 INFO success: caddy entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
    ::1 -  22/Feb/2025:23:25:34 +0000 "GET /index.php" 200
    ::1 -  22/Feb/2025:23:25:34 +0000 "GET /index.php" 404

    Docker Compose file

    services:
      # --- LinkAce
      linkace:
        image: docker.io/linkace/linkace:latest
        container_name: linkace
        restart: unless-stopped
        depends_on:
          - linkace_db
        ports:
          - "0.0.0.0:3009:80"
        volumes:
          - ./.env:/app/.env
          - ./backups:/app/storage/app/backups

      # --- Database
      linkace_db:
        image: docker.io/library/mariadb:11.5
        container_name: linkace_db
        restart: unless-stopped
        command: mariadbd --character-set-server=utf8mb4 --collation-server=utf8mb4_bin
        environment:
          - MYSQL_ROOT_PASSWORD=${DB_PASSWORD}
          - MYSQL_USER=${DB_USERNAME}
          - MYSQL_PASSWORD=${DB_PASSWORD}
          - MYSQL_DATABASE=${DB_DATABASE}
        volumes:
          - db:/var/lib/mysql

      # --- Cache
      linkace_redis:
        image: docker.io/bitnami/redis:7.4
        container_name: linkace_redis
        restart: unless-stopped
        environment:
          - REDIS_PASSWORD=${REDIS_PASSWORD}

    volumes:
      db:

    .env (secrets redacted)

    ## LINKACE CONFIGURATION

    # The app key is generated later, please leave it like that
    APP_KEY=redacted
    APP_ENV=development

    ## Configuration of the database connection
    ## Attention: Those settings are configured during the web setup, please do not modify them now.
    # Set the database driver (mysql, pgsql, sqlsrv, sqlite)
    DB_CONNECTION=mysql
    # Set the host of your database here
    DB_HOST=linkace_db
    # Set the port of your database here
    DB_PORT=3306
    # Set the database name here
    DB_DATABASE=linkace
    # Set both username and password of the user accessing the database
    DB_USERNAME=linkace
    # Wrap your password into quotes (") if it contains special characters
    DB_PASSWORD=redacted

    ## Redis cache configuration
    # Set the Redis connection here if you want to use it
    REDIS_HOST=linkace_redis
    REDIS_PASSWORD=redacted
    REDIS_PORT=6379
    APP_DEBUG=true

    # SSO configuration
    SSO_ENABLED=true
    SSO_OIDC_ENABLED=true
    SSO_REGISTRATION_ENABLED=true
    REGULAR_LOGIN_DISABLED=true
    SSO_OIDC_BASE_URL=https://auth.laniecarmelo.tech/  # Your Authelia base URL
    SSO_OIDC_CLIENT_ID=linkace
    SSO_OIDC_CLIENT_SECRET='redacted'
    SSO_OIDC_SCOPES=openid,profile,email

    Caddyfile snippet

    {
        email [email protected]
        debug
        acme_dns cloudflare redacted
        http_port 80
        https_port 443
        admin :2019 {
            origins 127.0.0.1:2019 0.0.0.0:2019 stormux:2019 caddy.laniecarmelo.tech
        }
    }

    (logconfig) {
        log {
            output stdout
            format json
        }
    }

    (auth_headers) {
        header Strict-Transport-Security "max-age=31536000; includeSubDomains; preload"
    }

    (proxy_config) {
        header_up Host {http.request.host}
        header_up X-Real-IP {http.request.remote}
        header_up X-Forwarded-User {http.auth.user.id} # Pass user ID
        header_up X-Forwarded-Email {http.auth.user.email} # Pass email
    }

    (authelia_middleware) {
        forward_auth localhost:9091 {
            uri /api/verify?rd=https://auth.laniecarmelo.tech
            copy_headers Remote-User Remote-Email Remote-Groups Authorization
        }
    }

    bookmarks.laniecarmelo.tech {
        route {
            import authelia_middleware
            reverse_proxy localhost:3009 {  # Directly proxy to LinkAce's web server
                import proxy_config
            }
        }
        import logconfig
        import auth_headers
    }

    Authelia config snippet

        - domain: "*.laniecarmelo.tech"
          policy: bypass
          networks:
            - 192.168.1.0/24    # Local network
            - 172.17.0.0/16     # Docker bridge network
            - 100.64.0.0/10     # Tailscale network

        - domain: "bookmarks.laniecarmelo.tech"
          resources: ["^/api.*"]
          policy: bypass

        - domain: "*.laniecarmelo.tech"
          policy: one_factor      

          - client_id: linkace
            client_name: LinkAce bookmarking app
            client_secret: redacted
             public: false
            authorization_policy: one_factor
            scopes: [openid, groups, profile, email, offline_access]
            redirect_uris:
              - https://bookmarks.laniecarmelo.tech/auth/oidc/callback
            grant_types: [authorization_code]
            response_types: [code]
            response_modes: [form_post, query]
            userinfo_signed_response_alg: none
            consent_mode: explicit
            pre_configured_consent_duration: "1y"

    Does anyone know what might be causing this and how I can fix it?
    #Linux #ArchLinuxARM #Stormux #RaspberryPi #RaspberryPi500 #RPi #RPi500 #tech #technology
    @selfhost @selfhosted @selfhosting

    #selfhosted #linkace #selfhosting #docker #caddy #authelia
  38. Lanie @[email protected] ·

    #SelfHosted #LinkAce Bookmark Manager Running, but Unable to Check for Updates or Generate a Cron Token

    Hi all. Hoping someone in the #SelfHosting community can help here. I'm running LinkAce in #Docker behind non-Dockerized #Caddy and #Authelia, and most things are working, but I'm seeing "Could not check for updates" at the bottom of each page, and when I tried to generate a cron token, nothing happened except for the generate button graying out. I am seeing one or two 404 errors in my logs, but I don't know if that's causing the problem or not. I don't know much about #PHP applications.

    Logs

    2025-02-22 23:25:26,460 INFO supervisord started with pid 1
    2025-02-22 23:25:27,465 INFO spawned: 'php-fpm' with pid 8
    2025-02-22 23:25:27,467 INFO spawned: 'caddy' with pid 9
    [22-Feb-2025 23:25:27] NOTICE: [pool www] 'user' directive is ignored when FPM is not running as root
    [22-Feb-2025 23:25:27] NOTICE: [pool www] 'group' directive is ignored when FPM is not running as root
    [22-Feb-2025 23:25:27] NOTICE: fpm is running, pid 8
    [22-Feb-2025 23:25:27] NOTICE: ready to handle connections
    {"level":"info","ts":1740266727.5264525,"msg":"using config from file","file":"/etc/caddy/Caddyfile"}
    {"level":"info","ts":1740266727.5280282,"msg":"adapted config to JSON","adapter":"caddyfile"}
    {"level":"warn","ts":1740266727.5280406,"msg":"Caddyfile input is not formatted; run 'caddy fmt --overwrite' to fix inconsistencies","adapter":"caddyfile","file":"/etc/caddy/Caddyfile","line":2}
    {"level":"info","ts":1740266727.529092,"logger":"admin","msg":"admin endpoint started","address":"localhost:2019","enforce_origin":false,"origins":["//localhost:2019","//[::1]:2019","//127.0.0.1:2019"]}
    {"level":"warn","ts":1740266727.529331,"logger":"http.auto_https","msg":"server is listening only on the HTTP port, so no automatic HTTPS will be applied to this server","server_name":"srv0","http_port":80}
    {"level":"info","ts":1740266727.5294206,"logger":"tls.cache.maintenance","msg":"started background certificate maintenance","cache":"0x40000bab00"}
    {"level":"warn","ts":1740266727.530186,"logger":"http","msg":"HTTP/2 skipped because it requires TLS","network":"tcp","addr":":80"}
    {"level":"warn","ts":1740266727.530195,"logger":"http","msg":"HTTP/3 skipped because it requires TLS","network":"tcp","addr":":80"}
    {"level":"info","ts":1740266727.530198,"logger":"http.log","msg":"server running","name":"srv0","protocols":["h1","h2","h3"]}
    {"level":"info","ts":1740266727.5412574,"msg":"autosaved config (load with --resume flag)","file":"/home/www-data/.config/caddy/autosave.json"}
    {"level":"info","ts":1740266727.541271,"msg":"serving initial configuration"}
    {"level":"info","ts":1740266727.5477707,"logger":"tls","msg":"cleaning storage unit","storage":"FileStorage:/home/www-data/.local/share/caddy"}
    {"level":"info","ts":1740266727.5541356,"logger":"tls","msg":"finished cleaning storage units"}
    2025-02-22 23:25:28,555 INFO success: php-fpm entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
    2025-02-22 23:25:28,555 INFO success: caddy entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
    ::1 -  22/Feb/2025:23:25:34 +0000 "GET /index.php" 200
    ::1 -  22/Feb/2025:23:25:34 +0000 "GET /index.php" 404

    Docker Compose file

    services:
      # --- LinkAce
      linkace:
        image: docker.io/linkace/linkace:latest
        container_name: linkace
        restart: unless-stopped
        depends_on:
          - linkace_db
        ports:
          - "0.0.0.0:3009:80"
        volumes:
          - ./.env:/app/.env
          - ./backups:/app/storage/app/backups

      # --- Database
      linkace_db:
        image: docker.io/library/mariadb:11.5
        container_name: linkace_db
        restart: unless-stopped
        command: mariadbd --character-set-server=utf8mb4 --collation-server=utf8mb4_bin
        environment:
          - MYSQL_ROOT_PASSWORD=${DB_PASSWORD}
          - MYSQL_USER=${DB_USERNAME}
          - MYSQL_PASSWORD=${DB_PASSWORD}
          - MYSQL_DATABASE=${DB_DATABASE}
        volumes:
          - db:/var/lib/mysql

      # --- Cache
      linkace_redis:
        image: docker.io/bitnami/redis:7.4
        container_name: linkace_redis
        restart: unless-stopped
        environment:
          - REDIS_PASSWORD=${REDIS_PASSWORD}

    volumes:
      db:

    .env (secrets redacted)

    ## LINKACE CONFIGURATION

    # The app key is generated later, please leave it like that
    APP_KEY=redacted
    APP_ENV=development

    ## Configuration of the database connection
    ## Attention: Those settings are configured during the web setup, please do not modify them now.
    # Set the database driver (mysql, pgsql, sqlsrv, sqlite)
    DB_CONNECTION=mysql
    # Set the host of your database here
    DB_HOST=linkace_db
    # Set the port of your database here
    DB_PORT=3306
    # Set the database name here
    DB_DATABASE=linkace
    # Set both username and password of the user accessing the database
    DB_USERNAME=linkace
    # Wrap your password into quotes (") if it contains special characters
    DB_PASSWORD=redacted

    ## Redis cache configuration
    # Set the Redis connection here if you want to use it
    REDIS_HOST=linkace_redis
    REDIS_PASSWORD=redacted
    REDIS_PORT=6379
    APP_DEBUG=true

    # SSO configuration
    SSO_ENABLED=true
    SSO_OIDC_ENABLED=true
    SSO_REGISTRATION_ENABLED=true
    REGULAR_LOGIN_DISABLED=true
    SSO_OIDC_BASE_URL=https://auth.laniecarmelo.tech/  # Your Authelia base URL
    SSO_OIDC_CLIENT_ID=linkace
    SSO_OIDC_CLIENT_SECRET='redacted'
    SSO_OIDC_SCOPES=openid,profile,email

    Caddyfile snippet

    {
        email [email protected]
        debug
        acme_dns cloudflare redacted
        http_port 80
        https_port 443
        admin :2019 {
            origins 127.0.0.1:2019 0.0.0.0:2019 stormux:2019 caddy.laniecarmelo.tech
        }
    }

    (logconfig) {
        log {
            output stdout
            format json
        }
    }

    (auth_headers) {
        header Strict-Transport-Security "max-age=31536000; includeSubDomains; preload"
    }

    (proxy_config) {
        header_up Host {http.request.host}
        header_up X-Real-IP {http.request.remote}
        header_up X-Forwarded-User {http.auth.user.id} # Pass user ID
        header_up X-Forwarded-Email {http.auth.user.email} # Pass email
    }

    (authelia_middleware) {
        forward_auth localhost:9091 {
            uri /api/verify?rd=https://auth.laniecarmelo.tech
            copy_headers Remote-User Remote-Email Remote-Groups Authorization
        }
    }

    bookmarks.laniecarmelo.tech {
        route {
            import authelia_middleware
            reverse_proxy localhost:3009 {  # Directly proxy to LinkAce's web server
                import proxy_config
            }
        }
        import logconfig
        import auth_headers
    }

    Authelia config snippet

        - domain: "*.laniecarmelo.tech"
          policy: bypass
          networks:
            - 192.168.1.0/24    # Local network
            - 172.17.0.0/16     # Docker bridge network
            - 100.64.0.0/10     # Tailscale network

        - domain: "bookmarks.laniecarmelo.tech"
          resources: ["^/api.*"]
          policy: bypass

        - domain: "*.laniecarmelo.tech"
          policy: one_factor      

          - client_id: linkace
            client_name: LinkAce bookmarking app
            client_secret: redacted
             public: false
            authorization_policy: one_factor
            scopes: [openid, groups, profile, email, offline_access]
            redirect_uris:
              - https://bookmarks.laniecarmelo.tech/auth/oidc/callback
            grant_types: [authorization_code]
            response_types: [code]
            response_modes: [form_post, query]
            userinfo_signed_response_alg: none
            consent_mode: explicit
            pre_configured_consent_duration: "1y"

    Does anyone know what might be causing this and how I can fix it?
    #Linux #ArchLinuxARM #Stormux #RaspberryPi #RaspberryPi500 #RPi #RPi500 #tech #technology
    @selfhost @selfhosted @selfhosting

    #selfhosted #linkace #selfhosting #docker #caddy #authelia
  39. Lanie @[email protected] ·

    #SelfHosted #LinkAce Bookmark Manager Running, but Unable to Check for Updates or Generate a Cron Token

    Hi all. Hoping someone in the #SelfHosting community can help here. I'm running LinkAce in #Docker behind non-Dockerized #Caddy and #Authelia, and most things are working, but I'm seeing "Could not check for updates" at the bottom of each page, and when I tried to generate a cron token, nothing happened except for the generate button graying out. I am seeing one or two 404 errors in my logs, but I don't know if that's causing the problem or not. I don't know much about #PHP applications.

    Logs

    2025-02-22 23:25:26,460 INFO supervisord started with pid 1
    2025-02-22 23:25:27,465 INFO spawned: 'php-fpm' with pid 8
    2025-02-22 23:25:27,467 INFO spawned: 'caddy' with pid 9
    [22-Feb-2025 23:25:27] NOTICE: [pool www] 'user' directive is ignored when FPM is not running as root
    [22-Feb-2025 23:25:27] NOTICE: [pool www] 'group' directive is ignored when FPM is not running as root
    [22-Feb-2025 23:25:27] NOTICE: fpm is running, pid 8
    [22-Feb-2025 23:25:27] NOTICE: ready to handle connections
    {"level":"info","ts":1740266727.5264525,"msg":"using config from file","file":"/etc/caddy/Caddyfile"}
    {"level":"info","ts":1740266727.5280282,"msg":"adapted config to JSON","adapter":"caddyfile"}
    {"level":"warn","ts":1740266727.5280406,"msg":"Caddyfile input is not formatted; run 'caddy fmt --overwrite' to fix inconsistencies","adapter":"caddyfile","file":"/etc/caddy/Caddyfile","line":2}
    {"level":"info","ts":1740266727.529092,"logger":"admin","msg":"admin endpoint started","address":"localhost:2019","enforce_origin":false,"origins":["//localhost:2019","//[::1]:2019","//127.0.0.1:2019"]}
    {"level":"warn","ts":1740266727.529331,"logger":"http.auto_https","msg":"server is listening only on the HTTP port, so no automatic HTTPS will be applied to this server","server_name":"srv0","http_port":80}
    {"level":"info","ts":1740266727.5294206,"logger":"tls.cache.maintenance","msg":"started background certificate maintenance","cache":"0x40000bab00"}
    {"level":"warn","ts":1740266727.530186,"logger":"http","msg":"HTTP/2 skipped because it requires TLS","network":"tcp","addr":":80"}
    {"level":"warn","ts":1740266727.530195,"logger":"http","msg":"HTTP/3 skipped because it requires TLS","network":"tcp","addr":":80"}
    {"level":"info","ts":1740266727.530198,"logger":"http.log","msg":"server running","name":"srv0","protocols":["h1","h2","h3"]}
    {"level":"info","ts":1740266727.5412574,"msg":"autosaved config (load with --resume flag)","file":"/home/www-data/.config/caddy/autosave.json"}
    {"level":"info","ts":1740266727.541271,"msg":"serving initial configuration"}
    {"level":"info","ts":1740266727.5477707,"logger":"tls","msg":"cleaning storage unit","storage":"FileStorage:/home/www-data/.local/share/caddy"}
    {"level":"info","ts":1740266727.5541356,"logger":"tls","msg":"finished cleaning storage units"}
    2025-02-22 23:25:28,555 INFO success: php-fpm entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
    2025-02-22 23:25:28,555 INFO success: caddy entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
    ::1 -  22/Feb/2025:23:25:34 +0000 "GET /index.php" 200
    ::1 -  22/Feb/2025:23:25:34 +0000 "GET /index.php" 404

    Docker Compose file

    services:
      # --- LinkAce
      linkace:
        image: docker.io/linkace/linkace:latest
        container_name: linkace
        restart: unless-stopped
        depends_on:
          - linkace_db
        ports:
          - "0.0.0.0:3009:80"
        volumes:
          - ./.env:/app/.env
          - ./backups:/app/storage/app/backups

      # --- Database
      linkace_db:
        image: docker.io/library/mariadb:11.5
        container_name: linkace_db
        restart: unless-stopped
        command: mariadbd --character-set-server=utf8mb4 --collation-server=utf8mb4_bin
        environment:
          - MYSQL_ROOT_PASSWORD=${DB_PASSWORD}
          - MYSQL_USER=${DB_USERNAME}
          - MYSQL_PASSWORD=${DB_PASSWORD}
          - MYSQL_DATABASE=${DB_DATABASE}
        volumes:
          - db:/var/lib/mysql

      # --- Cache
      linkace_redis:
        image: docker.io/bitnami/redis:7.4
        container_name: linkace_redis
        restart: unless-stopped
        environment:
          - REDIS_PASSWORD=${REDIS_PASSWORD}

    volumes:
      db:

    .env (secrets redacted)

    ## LINKACE CONFIGURATION

    # The app key is generated later, please leave it like that
    APP_KEY=redacted
    APP_ENV=development

    ## Configuration of the database connection
    ## Attention: Those settings are configured during the web setup, please do not modify them now.
    # Set the database driver (mysql, pgsql, sqlsrv, sqlite)
    DB_CONNECTION=mysql
    # Set the host of your database here
    DB_HOST=linkace_db
    # Set the port of your database here
    DB_PORT=3306
    # Set the database name here
    DB_DATABASE=linkace
    # Set both username and password of the user accessing the database
    DB_USERNAME=linkace
    # Wrap your password into quotes (") if it contains special characters
    DB_PASSWORD=redacted

    ## Redis cache configuration
    # Set the Redis connection here if you want to use it
    REDIS_HOST=linkace_redis
    REDIS_PASSWORD=redacted
    REDIS_PORT=6379
    APP_DEBUG=true

    # SSO configuration
    SSO_ENABLED=true
    SSO_OIDC_ENABLED=true
    SSO_REGISTRATION_ENABLED=true
    REGULAR_LOGIN_DISABLED=true
    SSO_OIDC_BASE_URL=https://auth.laniecarmelo.tech/  # Your Authelia base URL
    SSO_OIDC_CLIENT_ID=linkace
    SSO_OIDC_CLIENT_SECRET='redacted'
    SSO_OIDC_SCOPES=openid,profile,email

    Caddyfile snippet

    {
        email [email protected]
        debug
        acme_dns cloudflare redacted
        http_port 80
        https_port 443
        admin :2019 {
            origins 127.0.0.1:2019 0.0.0.0:2019 stormux:2019 caddy.laniecarmelo.tech
        }
    }

    (logconfig) {
        log {
            output stdout
            format json
        }
    }

    (auth_headers) {
        header Strict-Transport-Security "max-age=31536000; includeSubDomains; preload"
    }

    (proxy_config) {
        header_up Host {http.request.host}
        header_up X-Real-IP {http.request.remote}
        header_up X-Forwarded-User {http.auth.user.id} # Pass user ID
        header_up X-Forwarded-Email {http.auth.user.email} # Pass email
    }

    (authelia_middleware) {
        forward_auth localhost:9091 {
            uri /api/verify?rd=https://auth.laniecarmelo.tech
            copy_headers Remote-User Remote-Email Remote-Groups Authorization
        }
    }

    bookmarks.laniecarmelo.tech {
        route {
            import authelia_middleware
            reverse_proxy localhost:3009 {  # Directly proxy to LinkAce's web server
                import proxy_config
            }
        }
        import logconfig
        import auth_headers
    }

    Authelia config snippet

        - domain: "*.laniecarmelo.tech"
          policy: bypass
          networks:
            - 192.168.1.0/24    # Local network
            - 172.17.0.0/16     # Docker bridge network
            - 100.64.0.0/10     # Tailscale network

        - domain: "bookmarks.laniecarmelo.tech"
          resources: ["^/api.*"]
          policy: bypass

        - domain: "*.laniecarmelo.tech"
          policy: one_factor      

          - client_id: linkace
            client_name: LinkAce bookmarking app
            client_secret: redacted
             public: false
            authorization_policy: one_factor
            scopes: [openid, groups, profile, email, offline_access]
            redirect_uris:
              - https://bookmarks.laniecarmelo.tech/auth/oidc/callback
            grant_types: [authorization_code]
            response_types: [code]
            response_modes: [form_post, query]
            userinfo_signed_response_alg: none
            consent_mode: explicit
            pre_configured_consent_duration: "1y"

    Does anyone know what might be causing this and how I can fix it?
    #Linux #ArchLinuxARM #Stormux #RaspberryPi #RaspberryPi500 #RPi #RPi500 #tech #technology
    @selfhost @selfhosted @selfhosting

    #technology #tech #rpi500 #rpi #raspberrypi500 #raspberrypi
  40. Lanie @[email protected] ·

    #SelfHosted #LinkAce Bookmark Manager Running, but Unable to Check for Updates or Generate a Cron Token

    Hi all. Hoping someone in the #SelfHosting community can help here. I'm running LinkAce in #Docker behind non-Dockerized #Caddy and #Authelia, and most things are working, but I'm seeing "Could not check for updates" at the bottom of each page, and when I tried to generate a cron token, nothing happened except for the generate button graying out. I am seeing one or two 404 errors in my logs, but I don't know if that's causing the problem or not. I don't know much about #PHP applications.

    Logs

    2025-02-22 23:25:26,460 INFO supervisord started with pid 1
    2025-02-22 23:25:27,465 INFO spawned: 'php-fpm' with pid 8
    2025-02-22 23:25:27,467 INFO spawned: 'caddy' with pid 9
    [22-Feb-2025 23:25:27] NOTICE: [pool www] 'user' directive is ignored when FPM is not running as root
    [22-Feb-2025 23:25:27] NOTICE: [pool www] 'group' directive is ignored when FPM is not running as root
    [22-Feb-2025 23:25:27] NOTICE: fpm is running, pid 8
    [22-Feb-2025 23:25:27] NOTICE: ready to handle connections
    {"level":"info","ts":1740266727.5264525,"msg":"using config from file","file":"/etc/caddy/Caddyfile"}
    {"level":"info","ts":1740266727.5280282,"msg":"adapted config to JSON","adapter":"caddyfile"}
    {"level":"warn","ts":1740266727.5280406,"msg":"Caddyfile input is not formatted; run 'caddy fmt --overwrite' to fix inconsistencies","adapter":"caddyfile","file":"/etc/caddy/Caddyfile","line":2}
    {"level":"info","ts":1740266727.529092,"logger":"admin","msg":"admin endpoint started","address":"localhost:2019","enforce_origin":false,"origins":["//localhost:2019","//[::1]:2019","//127.0.0.1:2019"]}
    {"level":"warn","ts":1740266727.529331,"logger":"http.auto_https","msg":"server is listening only on the HTTP port, so no automatic HTTPS will be applied to this server","server_name":"srv0","http_port":80}
    {"level":"info","ts":1740266727.5294206,"logger":"tls.cache.maintenance","msg":"started background certificate maintenance","cache":"0x40000bab00"}
    {"level":"warn","ts":1740266727.530186,"logger":"http","msg":"HTTP/2 skipped because it requires TLS","network":"tcp","addr":":80"}
    {"level":"warn","ts":1740266727.530195,"logger":"http","msg":"HTTP/3 skipped because it requires TLS","network":"tcp","addr":":80"}
    {"level":"info","ts":1740266727.530198,"logger":"http.log","msg":"server running","name":"srv0","protocols":["h1","h2","h3"]}
    {"level":"info","ts":1740266727.5412574,"msg":"autosaved config (load with --resume flag)","file":"/home/www-data/.config/caddy/autosave.json"}
    {"level":"info","ts":1740266727.541271,"msg":"serving initial configuration"}
    {"level":"info","ts":1740266727.5477707,"logger":"tls","msg":"cleaning storage unit","storage":"FileStorage:/home/www-data/.local/share/caddy"}
    {"level":"info","ts":1740266727.5541356,"logger":"tls","msg":"finished cleaning storage units"}
    2025-02-22 23:25:28,555 INFO success: php-fpm entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
    2025-02-22 23:25:28,555 INFO success: caddy entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
    ::1 -  22/Feb/2025:23:25:34 +0000 "GET /index.php" 200
    ::1 -  22/Feb/2025:23:25:34 +0000 "GET /index.php" 404

    Docker Compose file

    services:
      # --- LinkAce
      linkace:
        image: docker.io/linkace/linkace:latest
        container_name: linkace
        restart: unless-stopped
        depends_on:
          - linkace_db
        ports:
          - "0.0.0.0:3009:80"
        volumes:
          - ./.env:/app/.env
          - ./backups:/app/storage/app/backups

      # --- Database
      linkace_db:
        image: docker.io/library/mariadb:11.5
        container_name: linkace_db
        restart: unless-stopped
        command: mariadbd --character-set-server=utf8mb4 --collation-server=utf8mb4_bin
        environment:
          - MYSQL_ROOT_PASSWORD=${DB_PASSWORD}
          - MYSQL_USER=${DB_USERNAME}
          - MYSQL_PASSWORD=${DB_PASSWORD}
          - MYSQL_DATABASE=${DB_DATABASE}
        volumes:
          - db:/var/lib/mysql

      # --- Cache
      linkace_redis:
        image: docker.io/bitnami/redis:7.4
        container_name: linkace_redis
        restart: unless-stopped
        environment:
          - REDIS_PASSWORD=${REDIS_PASSWORD}

    volumes:
      db:

    .env (secrets redacted)

    ## LINKACE CONFIGURATION

    # The app key is generated later, please leave it like that
    APP_KEY=redacted
    APP_ENV=development

    ## Configuration of the database connection
    ## Attention: Those settings are configured during the web setup, please do not modify them now.
    # Set the database driver (mysql, pgsql, sqlsrv, sqlite)
    DB_CONNECTION=mysql
    # Set the host of your database here
    DB_HOST=linkace_db
    # Set the port of your database here
    DB_PORT=3306
    # Set the database name here
    DB_DATABASE=linkace
    # Set both username and password of the user accessing the database
    DB_USERNAME=linkace
    # Wrap your password into quotes (") if it contains special characters
    DB_PASSWORD=redacted

    ## Redis cache configuration
    # Set the Redis connection here if you want to use it
    REDIS_HOST=linkace_redis
    REDIS_PASSWORD=redacted
    REDIS_PORT=6379
    APP_DEBUG=true

    # SSO configuration
    SSO_ENABLED=true
    SSO_OIDC_ENABLED=true
    SSO_REGISTRATION_ENABLED=true
    REGULAR_LOGIN_DISABLED=true
    SSO_OIDC_BASE_URL=https://auth.laniecarmelo.tech/  # Your Authelia base URL
    SSO_OIDC_CLIENT_ID=linkace
    SSO_OIDC_CLIENT_SECRET='redacted'
    SSO_OIDC_SCOPES=openid,profile,email

    Caddyfile snippet

    {
        email [email protected]
        debug
        acme_dns cloudflare redacted
        http_port 80
        https_port 443
        admin :2019 {
            origins 127.0.0.1:2019 0.0.0.0:2019 stormux:2019 caddy.laniecarmelo.tech
        }
    }

    (logconfig) {
        log {
            output stdout
            format json
        }
    }

    (auth_headers) {
        header Strict-Transport-Security "max-age=31536000; includeSubDomains; preload"
    }

    (proxy_config) {
        header_up Host {http.request.host}
        header_up X-Real-IP {http.request.remote}
        header_up X-Forwarded-User {http.auth.user.id} # Pass user ID
        header_up X-Forwarded-Email {http.auth.user.email} # Pass email
    }

    (authelia_middleware) {
        forward_auth localhost:9091 {
            uri /api/verify?rd=https://auth.laniecarmelo.tech
            copy_headers Remote-User Remote-Email Remote-Groups Authorization
        }
    }

    bookmarks.laniecarmelo.tech {
        route {
            import authelia_middleware
            reverse_proxy localhost:3009 {  # Directly proxy to LinkAce's web server
                import proxy_config
            }
        }
        import logconfig
        import auth_headers
    }

    Authelia config snippet

        - domain: "*.laniecarmelo.tech"
          policy: bypass
          networks:
            - 192.168.1.0/24    # Local network
            - 172.17.0.0/16     # Docker bridge network
            - 100.64.0.0/10     # Tailscale network

        - domain: "bookmarks.laniecarmelo.tech"
          resources: ["^/api.*"]
          policy: bypass

        - domain: "*.laniecarmelo.tech"
          policy: one_factor      

          - client_id: linkace
            client_name: LinkAce bookmarking app
            client_secret: redacted
             public: false
            authorization_policy: one_factor
            scopes: [openid, groups, profile, email, offline_access]
            redirect_uris:
              - https://bookmarks.laniecarmelo.tech/auth/oidc/callback
            grant_types: [authorization_code]
            response_types: [code]
            response_modes: [form_post, query]
            userinfo_signed_response_alg: none
            consent_mode: explicit
            pre_configured_consent_duration: "1y"

    Does anyone know what might be causing this and how I can fix it?
    #Linux #ArchLinuxARM #Stormux #RaspberryPi #RaspberryPi500 #RPi #RPi500 #tech #technology
    @selfhost @selfhosted @selfhosting

    #selfhosted #linkace #selfhosting #docker #caddy #authelia
  41. Lanie @[email protected] ·

    Help Needed with Cloudflare Zero Trust, Pages, and Workers for ReactFlux + MiniFlux Setup

    Hi everyone,

    I'm new to #Cloudflare and have been trying to set up a #SelfHosted project on my #RaspberryPi 500. I'm mostly self-taught, so I apologize if I misunderstand anything or miss important details. Here's my situation:

    Current Setup

    • I'm running the self-hosted #RSS feed reader #MiniFlux on my Raspberry Pi 500 (#ArchLinuxARM, installed via Pacman).
    • The setup uses #Caddy as a reverse proxy, a #CloudflareZeroTrust tunnel, and Cloudflare Access for SSO.
    • My #CloudflareAccess application is configured to allow all origins, methods, and headers. It has a policy that allows specific emails or login methods (e.g., GitHub).

    What I'm Trying to Do

    • I want to deploy ReactFlux, an alternative frontend for MiniFlux, on #CloudflarePages.
    • Before setting it up fully, I tested the ReactFlux demo with my MiniFlux instance at https://rss.laniecarmelo.tech. However, ReactFlux couldn't log in.

    Suspected Issue

    I believe the issue is caused by Cloudflare Access protection blocking ReactFlux from accessing the MiniFlux API (https://rss.laniecarmelo.tech/v1/*).

    What I've Tried So Far

    1. I added another hostname (rss.laniecarmelo.tech/v1/*) to my tunnel configuration and created a new Cloudflare Access application with a policy set to "Bypass" for everyone. However, this didn't work—when testing the API endpoint in a private browser window, I'm still asked to sign into Cloudflare.
    2. I also tried setting up the hostname with "Protect with Access" turned off but got the same results.
    3. Next, I attempted to use a #CloudflareWorker written in JavaScript to bypass authentication for /v1/*, but it doesn't seem to be doing anything (or isn't being triggered).

    What I Need Help With

    • How can I properly configure Cloudflare so ReactFlux can access the MiniFlux API (/v1/*) while keeping the rest of my MiniFlux instance protected by Cloudflare Access?
    • I've been stuck on this for a couple of days and would really appreciate any guidance or suggestions!

    Thanks in advance for your help!

    #SelfHosting #ArchLinux #Linux #RSSReader #tech #technology #RaspberryPi #RPi #RPi500 #RaspberryPi500
    @selfhosting @selfhost @selfhosted

    #cloudflare #selfhosted #raspberrypi #rss #miniflux #archlinuxarm
  42. Lanie @[email protected] ·

    Help Needed with Cloudflare Zero Trust, Pages, and Workers for ReactFlux + MiniFlux Setup

    Hi everyone,

    I'm new to #Cloudflare and have been trying to set up a #SelfHosted project on my #RaspberryPi 500. I'm mostly self-taught, so I apologize if I misunderstand anything or miss important details. Here's my situation:

    Current Setup

    • I'm running the self-hosted #RSS feed reader #MiniFlux on my Raspberry Pi 500 (#ArchLinuxARM, installed via Pacman).
    • The setup uses #Caddy as a reverse proxy, a #CloudflareZeroTrust tunnel, and Cloudflare Access for SSO.
    • My #CloudflareAccess application is configured to allow all origins, methods, and headers. It has a policy that allows specific emails or login methods (e.g., GitHub).

    What I'm Trying to Do

    • I want to deploy ReactFlux, an alternative frontend for MiniFlux, on #CloudflarePages.
    • Before setting it up fully, I tested the ReactFlux demo with my MiniFlux instance at https://rss.laniecarmelo.tech. However, ReactFlux couldn't log in.

    Suspected Issue

    I believe the issue is caused by Cloudflare Access protection blocking ReactFlux from accessing the MiniFlux API (https://rss.laniecarmelo.tech/v1/*).

    What I've Tried So Far

    1. I added another hostname (rss.laniecarmelo.tech/v1/*) to my tunnel configuration and created a new Cloudflare Access application with a policy set to "Bypass" for everyone. However, this didn't work—when testing the API endpoint in a private browser window, I'm still asked to sign into Cloudflare.
    2. I also tried setting up the hostname with "Protect with Access" turned off but got the same results.
    3. Next, I attempted to use a #CloudflareWorker written in JavaScript to bypass authentication for /v1/*, but it doesn't seem to be doing anything (or isn't being triggered).

    What I Need Help With

    • How can I properly configure Cloudflare so ReactFlux can access the MiniFlux API (/v1/*) while keeping the rest of my MiniFlux instance protected by Cloudflare Access?
    • I've been stuck on this for a couple of days and would really appreciate any guidance or suggestions!

    Thanks in advance for your help!

    #SelfHosting #ArchLinux #Linux #RSSReader #tech #technology #RaspberryPi #RPi #RPi500 #RaspberryPi500
    @selfhosting @selfhost @selfhosted

    #cloudflare #selfhosted #raspberrypi #rss #miniflux #archlinuxarm
  43. Lanie @[email protected] ·

    Help Needed with Cloudflare Zero Trust, Pages, and Workers for ReactFlux + MiniFlux Setup

    Hi everyone,

    I'm new to #Cloudflare and have been trying to set up a #SelfHosted project on my #RaspberryPi 500. I'm mostly self-taught, so I apologize if I misunderstand anything or miss important details. Here's my situation:

    Current Setup

    • I'm running the self-hosted #RSS feed reader #MiniFlux on my Raspberry Pi 500 (#ArchLinuxARM, installed via Pacman).
    • The setup uses #Caddy as a reverse proxy, a #CloudflareZeroTrust tunnel, and Cloudflare Access for SSO.
    • My #CloudflareAccess application is configured to allow all origins, methods, and headers. It has a policy that allows specific emails or login methods (e.g., GitHub).

    What I'm Trying to Do

    • I want to deploy ReactFlux, an alternative frontend for MiniFlux, on #CloudflarePages.
    • Before setting it up fully, I tested the ReactFlux demo with my MiniFlux instance at https://rss.laniecarmelo.tech. However, ReactFlux couldn't log in.

    Suspected Issue

    I believe the issue is caused by Cloudflare Access protection blocking ReactFlux from accessing the MiniFlux API (https://rss.laniecarmelo.tech/v1/*).

    What I've Tried So Far

    1. I added another hostname (rss.laniecarmelo.tech/v1/*) to my tunnel configuration and created a new Cloudflare Access application with a policy set to "Bypass" for everyone. However, this didn't work—when testing the API endpoint in a private browser window, I'm still asked to sign into Cloudflare.
    2. I also tried setting up the hostname with "Protect with Access" turned off but got the same results.
    3. Next, I attempted to use a #CloudflareWorker written in JavaScript to bypass authentication for /v1/*, but it doesn't seem to be doing anything (or isn't being triggered).

    What I Need Help With

    • How can I properly configure Cloudflare so ReactFlux can access the MiniFlux API (/v1/*) while keeping the rest of my MiniFlux instance protected by Cloudflare Access?
    • I've been stuck on this for a couple of days and would really appreciate any guidance or suggestions!

    Thanks in advance for your help!

    #SelfHosting #ArchLinux #Linux #RSSReader #tech #technology #RaspberryPi #RPi #RPi500 #RaspberryPi500
    @selfhosting @selfhost @selfhosted

    #cloudflare #selfhosted #raspberrypi #rss #miniflux #archlinuxarm
  44. Lanie @[email protected] ·

    Help Needed with Cloudflare Zero Trust, Pages, and Workers for ReactFlux + MiniFlux Setup

    Hi everyone,

    I'm new to #Cloudflare and have been trying to set up a #SelfHosted project on my #RaspberryPi 500. I'm mostly self-taught, so I apologize if I misunderstand anything or miss important details. Here's my situation:

    Current Setup

    • I'm running the self-hosted #RSS feed reader #MiniFlux on my Raspberry Pi 500 (#ArchLinuxARM, installed via Pacman).
    • The setup uses #Caddy as a reverse proxy, a #CloudflareZeroTrust tunnel, and Cloudflare Access for SSO.
    • My #CloudflareAccess application is configured to allow all origins, methods, and headers. It has a policy that allows specific emails or login methods (e.g., GitHub).

    What I'm Trying to Do

    • I want to deploy ReactFlux, an alternative frontend for MiniFlux, on #CloudflarePages.
    • Before setting it up fully, I tested the ReactFlux demo with my MiniFlux instance at https://rss.laniecarmelo.tech. However, ReactFlux couldn't log in.

    Suspected Issue

    I believe the issue is caused by Cloudflare Access protection blocking ReactFlux from accessing the MiniFlux API (https://rss.laniecarmelo.tech/v1/*).

    What I've Tried So Far

    1. I added another hostname (rss.laniecarmelo.tech/v1/*) to my tunnel configuration and created a new Cloudflare Access application with a policy set to "Bypass" for everyone. However, this didn't work—when testing the API endpoint in a private browser window, I'm still asked to sign into Cloudflare.
    2. I also tried setting up the hostname with "Protect with Access" turned off but got the same results.
    3. Next, I attempted to use a #CloudflareWorker written in JavaScript to bypass authentication for /v1/*, but it doesn't seem to be doing anything (or isn't being triggered).

    What I Need Help With

    • How can I properly configure Cloudflare so ReactFlux can access the MiniFlux API (/v1/*) while keeping the rest of my MiniFlux instance protected by Cloudflare Access?
    • I've been stuck on this for a couple of days and would really appreciate any guidance or suggestions!

    Thanks in advance for your help!

    #SelfHosting #ArchLinux #Linux #RSSReader #tech #technology #RaspberryPi #RPi #RPi500 #RaspberryPi500
    @selfhosting @selfhost @selfhosted

    #raspberrypi500 #rpi500 #rpi #technology #tech #rssreader
  45. Lanie @[email protected] ·

    Help Needed with Cloudflare Zero Trust, Pages, and Workers for ReactFlux + MiniFlux Setup

    Hi everyone,

    I'm new to #Cloudflare and have been trying to set up a #SelfHosted project on my #RaspberryPi 500. I'm mostly self-taught, so I apologize if I misunderstand anything or miss important details. Here's my situation:

    Current Setup

    • I'm running the self-hosted #RSS feed reader #MiniFlux on my Raspberry Pi 500 (#ArchLinuxARM, installed via Pacman).
    • The setup uses #Caddy as a reverse proxy, a #CloudflareZeroTrust tunnel, and Cloudflare Access for SSO.
    • My #CloudflareAccess application is configured to allow all origins, methods, and headers. It has a policy that allows specific emails or login methods (e.g., GitHub).

    What I'm Trying to Do

    • I want to deploy ReactFlux, an alternative frontend for MiniFlux, on #CloudflarePages.
    • Before setting it up fully, I tested the ReactFlux demo with my MiniFlux instance at https://rss.laniecarmelo.tech. However, ReactFlux couldn't log in.

    Suspected Issue

    I believe the issue is caused by Cloudflare Access protection blocking ReactFlux from accessing the MiniFlux API (https://rss.laniecarmelo.tech/v1/*).

    What I've Tried So Far

    1. I added another hostname (rss.laniecarmelo.tech/v1/*) to my tunnel configuration and created a new Cloudflare Access application with a policy set to "Bypass" for everyone. However, this didn't work—when testing the API endpoint in a private browser window, I'm still asked to sign into Cloudflare.
    2. I also tried setting up the hostname with "Protect with Access" turned off but got the same results.
    3. Next, I attempted to use a #CloudflareWorker written in JavaScript to bypass authentication for /v1/*, but it doesn't seem to be doing anything (or isn't being triggered).

    What I Need Help With

    • How can I properly configure Cloudflare so ReactFlux can access the MiniFlux API (/v1/*) while keeping the rest of my MiniFlux instance protected by Cloudflare Access?
    • I've been stuck on this for a couple of days and would really appreciate any guidance or suggestions!

    Thanks in advance for your help!

    #SelfHosting #ArchLinux #Linux #RSSReader #tech #technology #RaspberryPi #RPi #RPi500 #RaspberryPi500
    @selfhosting @selfhost @selfhosted

    #cloudflare #selfhosted #raspberrypi #rss #miniflux #archlinuxarm
  46. Lanie @[email protected] ·

    #MiniFlux users, can anyone help?

    Hi all. I'm having some issues with MiniFlux, a #SelfHosted #RSSReader, and hoping someone can help. MiniFlux was working fine until I tried to deploy ReactFlux on the same domain as it, rss.laniecarmelo.tech, on a subpath, /reactflux. This didn't work so I removed ReactFlux. I also migrated MiniFlux from #Docker to #Pacman package, thinking it would be easier on my system. This problem, or a similar one, was occurring before I did that though.

    Now, rss.laniecarmelo.tech loads the MiniFlux login page, but when I login, it redirects to a blank page at rss.laniecarmelo.tech/login. I've added trusted proxies and cookie configuration to my miniflux.conf and headers to my Caddyfile, but I still have the issue.

    I'm using #Caddy for #ReverseProxy and #Cloudflare for #SSO. Has anyone seen anything like this before? This is on a #RaspberryPi500 running #ArchLinuxARM.

    I've checked MiniFlux logs, and it's getting the login requests and creating sessions. I'm not sure what's happening after that. Cloudflared and Caddy seem to be working normally.

    #SelFhosting #Linux #RSS #RaspberryPi #RPi #tech #technology
    @selfhost @selfhosted @selfhosting

    #miniflux #selfhosted #rssreader #docker #pacman #caddy
  47. Lanie @[email protected] ·

    🚨 Help Needed: #CORS and #Cloudflare Access Issues with #Nextflux + #MiniFlux Setup 🚨

    Hi everyone! I’m struggling with a #SelfHosted setup and could really use some advice from the self-hosting community. Lol I've been trying to figure this out for hours with no luck. Here’s my situation:

    Setup

    • MiniFlux: Running in #Docker on a #RaspberryPi500 (#Stormux, based on #ArchLinuxARM).
    • Nextflux: Hosted on Cloudflare Pages.
    • Reverse Proxy: #Caddy (installed via AUR).
    • Cloudflare Access: Enabled for security and SSO.
    • Cloudflared: Also installed via AUR.
    • CORS Settings in Cloudflare Access: Configured to allow all origins, methods, and headers.

    What’s Working

    • MiniFlux is accessible from my home network after removing restrictive CORS settings in both Caddy and MiniFlux.
    • Nextflux is properly deployed on Cloudflare Pages.

    The Problem

    Nextflux cannot connect to MiniFlux due to persistent CORS errors and authentication issues with Cloudflare Access. Here are the errors I’m seeing in the browser console:

    1. CORS Error:Access to fetch at 'https://rss.laniecarmelo.tech/v1/me' from origin 'https://nextflux.laniecarmelo.tech' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.

    2. Cloudflare Access Redirection:

      Request redirected to 'https://lifeofararebird.cloudflareaccess.com/cdn-cgi/access/login/rss.laniecarmelo.tech'.

    3. Failed to Fetch:

      Failed to fetch: TypeError: Failed to fetch.

    What I’ve Tried

    1. Service Token Authentication:

      • Generated a service token in Cloudflare Access for Nextflux.
      • Added CF-Access-Client-Id and CF-Access-Client-Secret headers in Caddy for rss.laniecarmelo.tech.
      • Updated Cloudflare Access policies to include a bypass rule for this service token.

    2. CORS Configuration:

      • Tried permissive settings (Access-Control-Allow-Origin: *) in both Caddy and MiniFlux.
      • Configured Cloudflare Access CORS settings to allow all origins, methods, and headers.

    3. Policy Adjustments:

      • Created a bypass policy for my home IP range and public IP.
      • Added an "Allow" policy for authenticated users via email/login methods.

    4. Debugging Logs:

      • Checked Cloudflared logs, which show requests being blocked due to missing access tokens (AccessJWTValidator errors).

    Current State

    Despite these efforts:

    • Requests from Nextflux are still being blocked by Cloudflare Access or failing due to CORS issues.
    • The browser console consistently shows "No 'Access-Control-Allow-Origin' header" errors.

    Goals

    1. Allow Nextflux (hosted on Cloudflare Pages) to connect seamlessly to MiniFlux (behind Cloudflare Access).
    2. Maintain secure access to MiniFlux for other devices (e.g., my home network or mobile devices).

    My Environment

    • Raspberry Pi 500 running Arch Linux ARM.
    • Both Caddy and Cloudflared are installed via AUR packages.
    • MiniFlux is running in Docker with the following environment variables:CLOUDFLARE_SERVICE_AUTH_ENABLED=trueCLOUDFLARE_CLIENT_ID=<client-id>CLOUDFLARE_CLIENT_SECRET=<client-secret>

    Relevant Logs

    From cloudflared:

    ERR error="request filtered by middleware handler (AccessJWTValidator) due to: no access token in request"

    From the browser console:

    Access to fetch at 'https://rss.laniecarmelo.tech/v1/me' has been blocked by CORS policy.

    Questions

    1. Is there a better way to configure CORS for this setup?
    2. Should I be handling authentication differently between Nextflux and MiniFlux?
    3. How can I ensure that requests from Nextflux include valid access tokens?

    Any help or advice would be greatly appreciated! 🙏

    #SelfHosting #Cloudflare #CaddyServer #Docker #RSS #CORS #Linux #ArchLinuxARM #CloudflarePages #tech #technology

    #cors #cloudflare #nextflux #miniflux #selfhosted #docker
  48. 𝖑𝖔𝖗𝖊𝖓 𝖉𝖎𝖆𝖘 @[email protected] ·

    Has anyone used #beagleboard #beaglevahead to run #archlinux #archlinuxarm ? I am really curious what the #riscv space looks like with #linux in 2025.

    #beagleboard #beaglevahead #archlinux #archlinuxarm #riscv #linux
  49. 𝖑𝖔𝖗𝖊𝖓 𝖉𝖎𝖆𝖘 @[email protected] ·

    Has anyone used #beagleboard #beaglevahead to run #archlinux #archlinuxarm ? I am really curious what the #riscv space looks like with #linux in 2025.

    #beagleboard #beaglevahead #archlinux #archlinuxarm #riscv #linux
  50. j4n3z @[email protected] ·

    Dnes by snad pro #RaspberryPi5 měla dorazit malá USB zvukovka, SSD a RTC baterie.
    To znamená, že budu muset migrovat instalačku z SD karty a upravit design krabičky, aby se do ní SSD vešlo (hlavně redukce PCIe na M.2) 🫣 Aktuální design nebude fungovat kvůli sražení vpředu, které sice je pěkné, ale pro můj účel teď nepraktické 😄

    #FreeCAD na #ArchLinuxArm nějak zlobí, takže se možná na chvilku vrátím k #openSCAD 🤔

    Víkend asi bude patřit Box86/Box64 a pokusům o nějaký indie hry 😊

    #raspberrypi5 #freecad #archlinuxarm #openscad