I installed a LakeFS container with Postgres container for KV store and in the config.yaml I specify local block store. Upon startup I get the error - "check_url: https://audit.lakefs.io/audit" error - no such host... I replaced check_audit_url in config.yaml with 127.0.0.1. When I do docker run with that config, I get the error - "Get \"127.0.0.1...unsupported protocol. When i change check_audit_url in config.yaml to http://127.0.0.1 it errors out with - connection refused.. Audit check failed. If I set audit_log_level to NONE, then the audit error disappears and the server appears to come up, but I when I try to connect to https://127.0.0.1:8000 I get a tiny lakefs logo but a blank page. Eventually I plan to change from local block store to s3 or DynamoDB, but how can I get past this audit error and blank page by testing locally first please?

Hey @Sam, welcome to the lake lakefs Can you share your lakefs.yaml configuration (server configuration)? AFAIR the value is

security.audit_check_url

Please note that my LakeFS docker setup is in an isolated environment, not connected to the internet, with Postgres container for KV store and a local block store. Initially security.audit_check_url was not specified in my config.yaml. So it went to default https://audit.lakefs.io/audit. So I got the eerror - no such host. I then changed security.audit_check_url to http://127.0.0.1:8000, it errors out with - connection refused.. Audit check failed. If I set audit_log_level to NONE, then the audit error disappears, and the server appears to come up the errors, but all got was a blank page with a tiny LakeFS logo on top. When do "docker logs lakefs" I only see the Welcome to LakeFS stuff.. How can you have audit logs working with localhost? Where can I detailed logs that might help me troubleshoot why I'm getting blank page?

<https://audit.lakefs.io/audit>

is an endpoint used for scanning vulnerabilities in your lakeFS installation and warn you when such exist. If that’s not available for your installation, I guess you would have to do it the old fashioned way. Either way, for anything else - your lakeFS installation remains fully functional. I guess the name of the url and config key is quite confusing, but it has nothing to do with lakeFS audit logs 😄

Thank you... but then why am I getting a blank page? Where do I check logs to see why the home page is not being displayed?

Can you open the network tab while reloading the page? Do you see any request failing there?

OK... Thanks! I will do that tomorrow... Meanwhile any idea where the server side logs are? Hoping they can provide a clue as to what went wrong. I'm sure the issue is server side with my configuration.

The logs are written to stdout. So it should be available as the container logs