Working to get local-ai-packaged repo deployed to OCI cloud (Oracle) - caddy or dns issues

Hi all,
I have been working on a prototype install of the current adapted n8n local-ai-kit for public cloud deployments. My goal is to have a collection of mostly automated infrastructure installs of the full local ai ecosystem that @ColeMedin has been doing videos on for all the major cloud vendors as well as on-prem options. (so as to offer several options for customers) …
It’s been tricky to add some of the features I want, like security and such, but I now pretty much think I’m quite close on OCI (Oracle) …
However, I’m having issues with dns resolution. I think its a Caddy issue? Although the logs for Caddy are reporting TLS success like so:

{"level":"info","ts":1742299897.1896904,"logger":"tls.obtain","msg":"certificate obtained successfully","identifier":"openwebui.ai-and-automation-you-own.com","issuer":"acme-v02.api.letsencrypt.org-directory"}

I have setup dns through cloudflare and these settings appear to be ok I believe.?
One issue that I realized was a residual installation of Caddy on the Ubuntu VPS in question that I had done in the recent past as a test, which is one reason I believe the I didn’t thick thumb some DNS setting, because I successfully rendered the Caddy starting page via web browser.
This I realized was later causing my new Caddy docker container to loop restart with the ai-starter-kit … which I resolved enough to get Caddy container stable.
However, now I am getting DNS resolution issues on all of the subdomains I setup, eg n8n.,supabase., etc…

The error I’m seeing in the browser is:

n8n.ai-and-automation-you-own.com redirected you too many times.

Try deleting your cookies.
ERR_TOO_MANY_REDIRECTS

I’m fishing for ideas to try at this point, so would Love any ideas, feedback, debugging direction anyone would be willing to offer. :wink:

Thank you in advance for your efforts!

Craig

Wanted to update this in case others run into this type of issue. The TLDR is a running devops meme, ‘everything is a dns problem’ …
The issue involved my Cloudflare DNS settings being setup as defaulted for handling of SSL/TLS encryption mode configuration. I had it set for ‘Flexible’ Enable encryption only between your visitors and Cloudflare. This will avoid browser security warnings, but all connections between Cloudflare and your origin are made through HTTP.
It needed to be ‘Full Strict’ Enable encryption end-to-end and enforce validation on origin certificates. Use Cloudflare’s Origin CA to generate certificates for your origin.
If this is not set then Cloudflare send the request to Caddy on the OCI VPS as http, then Caddy responds with a redirect request https and Cloudflare again responds with http causing the loop.
Hope this helps someone else at some point.

1 Like

Glad you figured it out - thanks for circling back on this for the community :slight_smile:

1 Like