-
-
Notifications
You must be signed in to change notification settings - Fork 265
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
LogViewer::auth not working behind proxy #396
Comments
I faced the same issue, but even with Gate, I am able to access the viewer but not see the list of log files |
Here is actually the problem I am describing, it seems to have already been fixed. I will the proposed solution a try |
This might be due to configuration of the proxy. You must forward authorisation and host headers, otherwise Laravel might deny the request. Dump your request headers in any controller, and make sure you still receive the "Authorization" header, as well as the Host is set to the same as your "APP_URL" variable, or at least the host is added to the "LOG_VIEWER_API_STATEFUL_DOMAINS" variable https://log-viewer.opcodes.io/docs/3.x/configuration/route-and-domain#production-domains |
Not sure why it is the case, but when Laravel runs with Octane as reverse proxy (in production),
does not work and always leads to a 403 error, while
works fine.
PHP-FPM did not have this issue. I tested if it is a
remote_addr
related thing, by mapping it to the real IP instead of the Docker IP (real_ip_header X-Forwarded-For;
), but it didn't help.The text was updated successfully, but these errors were encountered: