#cloudflarepages — Public Fediverse posts

I'm moving the backend of our internal system from AWS Lambda/API Gateway to Cloudflare Pages Functions. Wow, it's so much faster even if it uses the same DynamoDB and Algolia for search.

#serverless #cloudflarePages #awslambda

I'm moving the backend of our internal system from AWS Lambda/API Gateway to Cloudflare Pages Functions. Wow, it's so much faster even if it uses the same DynamoDB and Algolia for search.

#serverless #cloudflarePages #awslambda

I'm moving the backend of our internal system from AWS Lambda/API Gateway to Cloudflare Pages Functions. Wow, it's so much faster even if it uses the same DynamoDB and Algolia for search.

#serverless #cloudflarePages #awslambda

500URL超のWordPressサイトを週末だけでヘッドレス化した — 実装はAIが約20時間、私はレビューなど3時間程度（Astro + Cloudflare Pages移行の全手順を公開）
https://qiita.com/nogataka/items/606660d788f2b055802f?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items

#qiita #WordPress #astro #JAMstack #ヘッドレスCMS #CloudflarePages

500URL超のWordPressサイトを週末だけでヘッドレス化した — 実装はAIが約20時間、私はレビューなど3時間程度（Astro + Cloudflare Pages移行の全手順を公開）
https://qiita.com/nogataka/items/606660d788f2b055802f?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items

#qiita #WordPress #astro #JAMstack #ヘッドレスCMS #CloudflarePages

500URL超のWordPressサイトを週末だけでヘッドレス化した — 実装はAIが約20時間、私はレビューなど3時間程度（Astro + Cloudflare Pages移行の全手順を公開）
https://qiita.com/nogataka/items/606660d788f2b055802f?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items

#qiita #WordPress #astro #JAMstack #ヘッドレスCMS #CloudflarePages

RE: https://mstdn.feddit.social/@admin/115978724644551216

今天主要在规划布局服务器，还写了很多.md策划社区的蓝图
然后付款NetCup，把新的NetCup服务器配置了一下
现在在删掉停掉ClawCloud上某些的Docker服务，然后整理了混乱不堪的主目录，用services、script、data替代，再划分Social、Network、Code、Monitor、Music

然后是迁移HostDzire上的Mastodon、Sharkey、GoToSocial，Loops、Pixelfed-Glitch，DNS配置、S3配置、SMTP等很多需要重新配置......

还有博客合并，取消掉Ghost、Hexo项目（迁移后修改博客链接），迁移到Astro/Hugo，并且部署在Cloudflare Pages上...

还有特别多策划，先掖着不说（）

#迁移 #NetCup #ClawCloud #docker #HostDzire #Social #Blog #CloudflarePages

I’m currently using #Github and #CloudflarePages for my #11ty site. If I move my code to selfhosted #Forgejo or #GitLab, what are my options for the build process and to serve the site?

#selfhosting

I’m currently using #Github and #CloudflarePages for my #11ty site. If I move my code to selfhosted #Forgejo or #GitLab, what are my options for the build process and to serve the site?

#selfhosting

I’m currently using #Github and #CloudflarePages for my #11ty site. If I move my code to selfhosted #Forgejo or #GitLab, what are my options for the build process and to serve the site?

#selfhosting

I’m currently using #Github and #CloudflarePages for my #11ty site. If I move my code to selfhosted #Forgejo or #GitLab, what are my options for the build process and to serve the site?

#selfhosting

I’m currently using #Github and #CloudflarePages for my #11ty site. If I move my code to selfhosted #Forgejo or #GitLab, what are my options for the build process and to serve the site?

#selfhosting

Tự động hóa blog Astro với GitHub Actions! ✨ Tạo CI/CD hoàn chỉnh để khởi tạo và triển khai blog chỉ với vài cú nhấp chuột. Hỗ trợ kiểm thử, linting, build và deploy tự động lên Cloudflare Pages. Dễ dàng tái sử dụng cho nhiều dự án. #Astro #GitHubActions #CI_CD #DevOps #Cloudflare #Tự_động_hóa #DevTool #WebDevelopment
#AstroBlog #GitHubActions #CloudflarePages #CICD #Automation #WebDev #Tech #Programing

https://dev.to/picoable/automate-your-astro-blog-with-github-actions-5aic

Tự động hóa blog Astro với GitHub Actions! ✨ Tạo CI/CD hoàn chỉnh để khởi tạo và triển khai blog chỉ với vài cú nhấp chuột. Hỗ trợ kiểm thử, linting, build và deploy tự động lên Cloudflare Pages. Dễ dàng tái sử dụng cho nhiều dự án. #Astro #GitHubActions #CI_CD #DevOps #Cloudflare #Tự_động_hóa #DevTool #WebDevelopment
#AstroBlog #GitHubActions #CloudflarePages #CICD #Automation #WebDev #Tech #Programing

https://dev.to/picoable/automate-your-astro-blog-with-github-actions-5aic

【React×Cloudflare Pages】パチンコで狙い目の台を探すためのサービスをリリースしました
https://qiita.com/q-1-p/items/31ae688c53183597b3f1?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items

#qiita #拡張機能 #React #副業 #CloudflarePages #CloudflarePagesFunctions

【React×Cloudflare Pages】パチンコで狙い目の台を探すためのサービスをリリースしました
https://qiita.com/q-1-p/items/31ae688c53183597b3f1?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items

#qiita #拡張機能 #React #副業 #CloudflarePages #CloudflarePagesFunctions

How to Host a Website for Free in 2025 (Beginner Guide)

https://www.byteswifts.com/2025/08/how-to-host-website-for-free-in-2025.html

#FreeWebHosting #WebsiteHosting #BloggingTips #WebDevelopment #WordPress #Blogger #GitHubPages #Netlify #CloudflarePages #WixWebsite #GoogleCloud #AwardSpace #InfinityFree #000webhost #WebsiteBuilder #FreeTools #Tech2025 #DigitalTools #CloudHosting #BeginnerGuide #WebsiteDesign #WebTips #CodingLife #StudentsGuide #StartupTips #SmallBusiness #WebSecurity #FreeHosting2025 #WebTutorial #BuildAWebsite

🚧 Just rebuilt my personal site from scratch!
⚙️ Powered by #Hugo
🌐 Hosted on #CloudflarePages (for free!)
📁 Code on #GitHub
💬 Thanks to #ChatGPT for squashing syntax bugs 😅

Felt great to jump back into #HTML, #CSS, and #Markdown!

👉 https://AlwynSoh.com

#WebDev #IndieWeb #DevLife #BuiltWithHugo #SelfHost

🚧 Just rebuilt my personal site from scratch!
⚙️ Powered by #Hugo
🌐 Hosted on #CloudflarePages (for free!)
📁 Code on #GitHub
💬 Thanks to #ChatGPT for squashing syntax bugs 😅

Felt great to jump back into #HTML, #CSS, and #Markdown!

👉 https://AlwynSoh.com

#WebDev #IndieWeb #DevLife #BuiltWithHugo #SelfHost

🚧 Just rebuilt my personal site from scratch!
⚙️ Powered by #Hugo
🌐 Hosted on #CloudflarePages (for free!)
📁 Code on #GitHub
💬 Thanks to #ChatGPT for squashing syntax bugs 😅

Felt great to jump back into #HTML, #CSS, and #Markdown!

👉 https://AlwynSoh.com

#WebDev #IndieWeb #DevLife #BuiltWithHugo #SelfHost

🚧 Just rebuilt my personal site from scratch!
⚙️ Powered by #Hugo
🌐 Hosted on #CloudflarePages (for free!)
📁 Code on #GitHub
💬 Thanks to #ChatGPT for squashing syntax bugs 😅

Felt great to jump back into #HTML, #CSS, and #Markdown!

👉 https://AlwynSoh.com

#WebDev #IndieWeb #DevLife #BuiltWithHugo #SelfHost

🚧 Just rebuilt my personal site from scratch!
⚙️ Powered by #Hugo
🌐 Hosted on #CloudflarePages (for free!)
📁 Code on #GitHub
💬 Thanks to #ChatGPT for squashing syntax bugs 😅

Felt great to jump back into #HTML, #CSS, and #Markdown!

👉 https://AlwynSoh.com

#WebDev #IndieWeb #DevLife #BuiltWithHugo #SelfHost

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

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

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

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

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

Anyone with a solution for this when you host #11ty on #cloudflarepages? I have failed replicating what @robb do on his blog. https://pub.calebhearth.com/@caleb/113986254765194334

Anyone with a solution for this when you host #11ty on #cloudflarepages? I have failed replicating what @robb do on his blog. https://pub.calebhearth.com/@caleb/113986254765194334

Anyone with a solution for this when you host #11ty on #cloudflarepages? I have failed replicating what @robb do on his blog. https://pub.calebhearth.com/@caleb/113986254765194334

Anyone with a solution for this when you host #11ty on #cloudflarepages? I have failed replicating what @robb do on his blog. https://pub.calebhearth.com/@caleb/113986254765194334

Anyone with a solution for this when you host #11ty on #cloudflarepages? I have failed replicating what @robb do on his blog. https://pub.calebhearth.com/@caleb/113986254765194334

🚨 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

🚨 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

🚨 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

🚨 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

🚨 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

One thing I was missing on Cloudflare Pages is better errors' #observability. As I don't use Sentry, there was no easy way to use Rollbar. Until today. I published the #Rollbar plugin for #CloudflarePages to NPM. https://github.com/hckr-studio/cloudflare-pages-plugin-rollbar

One thing I was missing on Cloudflare Pages is better errors' #observability. As I don't use Sentry, there was no easy way to use Rollbar. Until today. I published the #Rollbar plugin for #CloudflarePages to NPM. https://github.com/hckr-studio/cloudflare-pages-plugin-rollbar

One thing I was missing on Cloudflare Pages is better errors' #observability. As I don't use Sentry, there was no easy way to use Rollbar. Until today. I published the #Rollbar plugin for #CloudflarePages to NPM. https://github.com/hckr-studio/cloudflare-pages-plugin-rollbar

I put the video, presentation and links into one place. You can find it on my blog https://www.rarous.net/weblog/2024/11/07/frontkon-serverless-renderovani-webovych-komponent #SSR #WebComponents #Serverless #CloudflarePages #LinkeDOM

I put the video, presentation and links into one place. You can find it on my blog https://www.rarous.net/weblog/2024/11/07/frontkon-serverless-renderovani-webovych-komponent #SSR #WebComponents #Serverless #CloudflarePages #LinkeDOM

I put the video, presentation and links into one place. You can find it on my blog https://www.rarous.net/weblog/2024/11/07/frontkon-serverless-renderovani-webovych-komponent #SSR #WebComponents #Serverless #CloudflarePages #LinkeDOM

Added more logging to #11ty. Turns out eleventy-img processes the images without any trouble.

Could it be that the build process takes too long to finish? Every attempt I make building on #CloudflarePages eventually ends with a segmentation fault after 6-7 minutes time.

Added more logging to #11ty. Turns out eleventy-img processes the images without any trouble.

Could it be that the build process takes too long to finish? Every attempt I make building on #CloudflarePages eventually ends with a segmentation fault after 6-7 minutes time.

Added more logging to #11ty. Turns out eleventy-img processes the images without any trouble.

Could it be that the build process takes too long to finish? Every attempt I make building on #CloudflarePages eventually ends with a segmentation fault after 6-7 minutes time.

Added more logging to #11ty. Turns out eleventy-img processes the images without any trouble.

Could it be that the build process takes too long to finish? Every attempt I make building on #CloudflarePages eventually ends with a segmentation fault after 6-7 minutes time.

Added more logging to #11ty. Turns out eleventy-img processes the images without any trouble.

Could it be that the build process takes too long to finish? Every attempt I make building on #CloudflarePages eventually ends with a segmentation fault after 6-7 minutes time.

Trying to deploy an #11ty site on #CloudflarePages without any success. This is what every try ends with:

21:26:11.279 Segmentation fault
21:26:11.288 Failed: Error while executing user command. Exited with error code: 139
21:26:11.298 Failed: build command exited with code: 1
21:26:12.755 Failed: error occurred while running build command

The same site builds just fine on Netlify.

My hunch is that it is eleventy-img's processing that takes to long.

Any ideas?

Trying to deploy an #11ty site on #CloudflarePages without any success. This is what every try ends with:

21:26:11.279 Segmentation fault
21:26:11.288 Failed: Error while executing user command. Exited with error code: 139
21:26:11.298 Failed: build command exited with code: 1
21:26:12.755 Failed: error occurred while running build command

The same site builds just fine on Netlify.

My hunch is that it is eleventy-img's processing that takes to long.

Any ideas?

Trying to deploy an #11ty site on #CloudflarePages without any success. This is what every try ends with:

21:26:11.279 Segmentation fault
21:26:11.288 Failed: Error while executing user command. Exited with error code: 139
21:26:11.298 Failed: build command exited with code: 1
21:26:12.755 Failed: error occurred while running build command

The same site builds just fine on Netlify.

My hunch is that it is eleventy-img's processing that takes to long.

Any ideas?

Trying to deploy an #11ty site on #CloudflarePages without any success. This is what every try ends with:

21:26:11.279 Segmentation fault
21:26:11.288 Failed: Error while executing user command. Exited with error code: 139
21:26:11.298 Failed: build command exited with code: 1
21:26:12.755 Failed: error occurred while running build command

The same site builds just fine on Netlify.

My hunch is that it is eleventy-img's processing that takes to long.

Any ideas?

Trying to deploy an #11ty site on #CloudflarePages without any success. This is what every try ends with:

21:26:11.279 Segmentation fault
21:26:11.288 Failed: Error while executing user command. Exited with error code: 139
21:26:11.298 Failed: build command exited with code: 1
21:26:12.755 Failed: error occurred while running build command

The same site builds just fine on Netlify.

My hunch is that it is eleventy-img's processing that takes to long.

Any ideas?

Senzilla, però efectiva. Ja tinc https://in4matics.cat a #CloudflarePages

#Cloudflare #Web #Pages

Senzilla, però efectiva. Ja tinc https://in4matics.cat a #CloudflarePages

#Cloudflare #Web #Pages

Senzilla, però efectiva. Ja tinc https://in4matics.cat a #CloudflarePages

#Cloudflare #Web #Pages

Senzilla, però efectiva. Ja tinc https://in4matics.cat a #CloudflarePages

#Cloudflare #Web #Pages