# Flint 2 - luci cors errors

**URL:** <https://forum.gl-inet.com/t/flint-2-luci-cors-errors/57072>\
**Category:** Router\
**Created:** [April 11, 2025, 10:01pm UTC](https://forum.gl-inet.com/t/flint-2-luci-cors-errors/57072 "2025-04-11T22:01:38Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![hendersj](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/h/4bbf92/32.png) [@hendersj](https://forum.gl-inet.com/u/hendersj)\
**Post date:** [April 13, 2025, 7:34pm UTC](https://forum.gl-inet.com/t/flint-2-luci-cors-errors/57072/2 "2025-04-13T19:34:25Z")

</div>

I think I found a solution to this issue, but I'm interested in feedback on it.

I modified `/etc/nginx/conf.d/gl.conf` and changed the ipv4 listen line from:

```auto
    listen :443 ssl;

```

to

```auto
    listen 192.168.8.1:443 ssl;

```

(Replacing the 192.x.x.x address with my router's own internal address)

It seems that now I don't get the CORS errors, and I can still access both the gl.inet and luci interfaces. Since I only want the web UI accessible from inside my network (and via VPN, which also works), this change makes sense to me.

But I'm not sure why it fixed the CORS errors. I made the change while trying to resolve the other issue I asked about on Friday ([Wireguard connection to web services in my LAN using external IP/DNS address](https://forum.gl-inet.com/t/wireguard-connection-to-web-services-in-my-lan-using-external-ip-dns-address/57074)) and found that this change affected this particular issue.

---

_[View the full topic](https://forum.gl-inet.com/t/flint-2-luci-cors-errors/57072)._