-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
nginx proxy returns 403: Forbidden #3144
Comments
The problem persists after upgrading core to 2023.7.3. |
I'm trying to understand why the error_log (set to stdout) doesn't log anything for these requests.
That directive just creates an empty custom_error.log file. I also tried setting HA debug level and that doesn't log anything either. logger:
logs:
homeassistant.core: debug
http: debug
homeassistant.components.http: debug |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Describe the issue you are experiencing
When I try to connect to the nginx HTTPS proxy I get 403: Forbidden. This was working fine in the past, and I'm not sure what changed. My SSL certificate is valid. I'm getting the same issue in Chrome, Safari, and curl.
Nginx error log doesn't show anything, and neither does HA core log. If I bypass the proxy and use HTTP on port 8123 it works fine.
Addon configuration is like this:
What type of installation are you running?
Home Assistant OS
Which operating system are you running on?
Home Assistant Operating System
Which add-on are you reporting an issue with?
NGINX Home Assistant SSL proxy
What is the version of the add-on?
3.5.0
Steps to reproduce the issue
System Health information
System Information
Home Assistant Community Store
Home Assistant Cloud
Home Assistant Supervisor
Dashboards
Recorder
Anything in the Supervisor logs that might be useful for us?
No response
Anything in the add-on logs that might be useful for us?
Additional information
I tried reproducing the issue using a separate Docker container with
nginx:latest
and the same nginx.conf file, just modifying theproxy_pass
URL. That works fine, no problems.The text was updated successfully, but these errors were encountered: