soc.octade.net is a Fediverse instance that uses the ActivityPub protocol. In other words, users at this host can communicate with people that use software like Mastodon, Pleroma, Friendica, etc. all around the world.

This server runs the snac software and there is no automatic sign-up process.

Admin email
social@octade.net

Search results for tag #cloudflare

Pyrzout »
@jos1264@social.skynetcloud.site

JimmyChezPants 🇨🇦 »
@jpaskaruk@growers.social

Hey

edit: I have not yet sorted out getting Docker running on NixOS yet, so for the moment I'm gonna get that installed and use the available container, which has latest build. I would like to stick to pure Nix on everything, but there is a need to be, umm, clean on opsec.

I was trying to install cloudflared from unstable repo. It installed and works from 24.11, but when I ran the command to create the credentialsFile it complained about the older version and suggested upgrading to 2025.4.0 rather than the 2024.10.0 that is in nixos.

Unstable has 2025.2.1, which is better, but is not 2025.4.0. Two branching questions from here.

1 - the unstable package returned that error: Package ‘cloudflared-2025.2.1’ in /nix/store/vxwsnfg5mys9v1qrxvim13ddmnhd4z1g-unstable/unstable/pkgs/applications/networking/cloudflared/default.nix:97 is marked as broken, refusing to evaluate.

Conveniently, it included instructions for allowing packages marked broken through. Is that considered normal in dealing with Cloudflare on NixOS? Cause it reads to me like an outtake from "How To Get Your Website Pwned By L33t H4krz".

2 - considering that even if I allow the "broken" package in, I'm still not getting the version recommended by cloudflared's error message, perhaps there's a flake or something I should try, that would get the daily build or whatever?

I'm off to do more searches and maybe poke my head into one of the actual support forums, but this seems like a pretty common task for NixOS admins to be doing, so it's probably an easy answer that I just haven't found yet.

Probably been looking at nixos.wiki again or something.

    Krutonium:// »
    @krutonium@social.treehouse.systems

    If you know someone who works on/at Tell them their SSL Certificate just expired!

      Pyrzout »
      @jos1264@social.skynetcloud.site

      Jerry on Mastodon »
      @Jerry@hear-me.social

      Over the past 24-hours, has been the most determined crawler to scrape data from this server, by far. They never succeed. always blocks them for being one of the unwanted AI bots.

      What is interesting though is its determination to read one particular user invite. I wonder how it picks the other posts it wants to read.

      Fairewall image of the Facebook BOT activity over the past 24-hours showing 846 blocked attempts to scrape data.

      Alt...Fairewall image of the Facebook BOT activity over the past 24-hours showing 846 blocked attempts to scrape data.

        Pyrzout »
        @jos1264@social.skynetcloud.site

        Jerry on Mastodon »
        @Jerry@hear-me.social

        Over the past 24-hours, the firewall blocked over 34K requests on hear-me.social, about 7% of the traffic. This is a typical day. Some days, though, can be a lot more. I'm dodging some bullets.

        I don't have the knowledge or time to build a firewall that recognizes bot behaviors, dynamically learns new abuse behaviors, does managed challenges when needed, and recognizes and blocks the hundreds of attack patterns hackers use. I would need a bigger server. I just couldn't do this myself.

        And Cloudflare provides this service for free to hobbyists and small businesses.

        Graph showing traffic blocked by time

        Alt...Graph showing traffic blocked by time

          Jerry on Mastodon »
          @Jerry@hear-me.social

          now punishes companies that purposely ignore their do-not-scan rules.

          "... The content served to bots is deliberately irrelevant to the website being crawled, but it is carefully sourced or generated using real scientific facts—such as neutral information about biology, physics, or mathematics ... ". Cloudflare creates this content using its Workers AI service.

          "No real human would go four links deep into a maze of AI-generated nonsense," Cloudflare explains. "Any visitor that does is very likely to be a bot, so this gives us a brand-new tool to identify and fingerprint bad bots."

          arstechnica.com/ai/2025/03/clo

            Pyrzout »
            @jos1264@social.skynetcloud.site

            Lanie Molinar Carmelo »
            @RareBird15@allovertheplace.ca

            I'm curious to hear what others are ! 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!

            Productivity & Personal Tools

            Notifications & Development Workflow

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

            Accessibility Focus ♿️🖥️

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

            I've also experimented with:

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

            I don't really have a media collection, so no Plex or Jellyfin here ()—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?

                 

            @selfhost @selfhosted @selfhosting

              Pyrzout »
              @jos1264@social.skynetcloud.site

              Pyrzout »
              @jos1264@social.skynetcloud.site

              Pyrzout »
              @jos1264@social.skynetcloud.site

              Lanie Molinar Carmelo »
              @RareBird15@allovertheplace.ca

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

              Hi everyone,

              I'm new to and have been trying to set up a project on my 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 feed reader on my Raspberry Pi 500 (, installed via Pacman).
              • The setup uses as a reverse proxy, a tunnel, and Cloudflare Access for SSO.
              • My 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 .
              • 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 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 @selfhost @selfhosted

                Lanie Molinar Carmelo »
                @RareBird15@allovertheplace.ca

                users, can anyone help?

                Hi all. I'm having some issues with MiniFlux, a , 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 to 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 for and for . Has anyone seen anything like this before? This is on a running .

                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.


                @selfhost @selfhosted @selfhosting

                  Lanie Molinar Carmelo »
                  @RareBird15@allovertheplace.ca

                  🚨 Help Needed: and Access Issues with + Setup 🚨

                  Hi everyone! I’m struggling with a 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 on a (, based on ).
                  • Nextflux: Hosted on Cloudflare Pages.
                  • Reverse Proxy: (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! 🙏

                    Hans van Zijst »
                    @hans@social.woefdram.nl

                    Hahaha, #Thuisbezorgd meldt via #CloudFlare dat mijn browser te oud is.

                    Gisterenavond heb #Firefox geüpdated naar de laatste versie, dus ik vermoed dat het "probleem" ergens anders ligt.

                    Waarschijnlijk bij het blokkeren en negeren van alle tracking-shite die ze in hun pagina's stoppen. Ik vermoed dat dat ook de reden is dat #Dominos een blanco pagina geeft zodra ik op iets klik.

                    Nou ja, your loss, ik kom toch wel aan een pizza hoor. My way or the highway.

                    #enshittification

                      Pyrzout »
                      @jos1264@social.skynetcloud.site