Skip to content

Commit 9fe778f

Browse files
author
ivan m.
committed
Remove outdated guides on connecting Excel to a local LakeFS server and replace with a comprehensive solution using NGINX reverse proxy to address CORS and Private Network Access issues.
1 parent 7211547 commit 9fe778f

4 files changed

+18
-345
lines changed

_posts/2025-06-23-a-complete-guide-connecting-excel-to-a-local-lakefs-server.md

Lines changed: 0 additions & 111 deletions
This file was deleted.

_posts/2025-06-23-connecting-excel-to-a-local-lakefs-server-a-clearer-guide.md

Lines changed: 0 additions & 55 deletions
This file was deleted.
Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,18 @@
1+
---
2+
3+
title: "Connecting Excel to a Local lakeFS Server"
4+
date: 2025-06-23 21:29:00 +0400
5+
categories: [Tech Stack, Troubleshooting]
6+
tags: [cors, docker, excel, lakefs, nginx, xlwings]
7+
render_with_liquid: false
8+
9+
---
10+
11+
This guide provides a definitive solution to a common but complex problem: connecting a modern Excel add-in (specifically, xlwings Lite) to a lakeFS server running on your local machine (`localhost`).
12+
13+
When you attempt this, you are likely to be blocked by browser security errors that can be difficult to diagnose. In your browser's developer console, you will typically see a failed `OPTIONS` preflight request in the network tab, followed by a CORS error message similar to this:
14+
15+
> Access to XMLHttpRequest at 'http://localhost:8000/api/v1/repositories' from origin 'https://addin.xlwings.org' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource.
16+
17+
Before we dive into the technical reasons, let's confirm you're facing this exact issue.
18+

0 commit comments

Comments
 (0)