Closed kristian-lange closed 5 months ago
Hi Kristian,
At first glance I would say you actually setup the PROXY_PATH correctly. I believe your issue may instead be CORS related, because you are running it on example.com (I presume you are using /etc/hosts, and are not the ACTUAL owner of example.com haha).
Check out this table. You can either:
LRSQL_ALLOW_ALL_ORIGINS
, less secure but super flexible)
or LRSQL_ALLOWED_ORIGINS
, probably my recommendation for a production deployment) Thanks, Cliff
Thank you for the LRSQL_ALLOW_ALL_ORIGINS
. This solved it for me.
I want to set up LRSQL with an URL base path (
/lrsql
) since there are other applications running on the host, but somehow I cannot get it running.I found this in your documentation (https://yetanalytics.github.io/lrsql/env_vars.html):
Can you please help me with the setup or point me at an example.
This is my docker-compose.yml to run the LRSQL:
These are the relevant parts of my Apache reverse proxy configuration:
If I open the LRSQL page in the browser I get the login page but with some errors and I cannot login:
I'm running an Ubuntu 22.04, if it is relevant.