Skip to content
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 Addon -- is not usable.. 400 & 500 errors with no logging or help to try and resolve. #3055

Closed
MiddleSiggy opened this issue May 21, 2023 · 4 comments

Comments

@MiddleSiggy
Copy link

Describe the issue you are experiencing

I have more than 30 years and 26 IT certifications, and the HA implementation of this addon makes it practically un-usable..

You need to add in some logging or a hint as to why things are not working.. I have just spent the last 3 hours trying to debug my instance to try and understand why I can reach HA internally, but externally I receive nothing but errors..

So at this point I have uninstalled it, left my inside HA running on port 8123, and just feed my external connection through haproxy on psfense from outside port 443 to 8123..

I highly suggest you do something with this package...

Thank you

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?

current

Steps to reproduce the issue

  1. install Nginx, configure per documentations
  2. can connect internal no problem 10.254.0.254:8123
  3. can connect ha.domain.com internal with IP resolves to 10.254.0.254
  4. When trying to come from outside, my edge has a pfsense firewall running haproxy it does not work.
  5. The connection is Internet -> haproxy -> Nginx -> HA

Logging is needed

I have tried to use openssl to test port 443 on nginx and it does not seem to work correctly..

again.. no logging...
...

System Health information

no logging, logging needed

Anything in the Supervisor logs that might be useful for us?

no logging, logging needed

Anything in the add-on logs that might be useful for us?

no logging, logging needed

Additional information

No response

@MiddleSiggy MiddleSiggy changed the title This is not usable.. 400 & 500 errors with no logging or help to try and resolve. NGINX Addon -- is not usable.. 400 & 500 errors with no logging or help to try and resolve. May 21, 2023
@8ear
Copy link

8ear commented May 22, 2023

I have the same issue.

@wawyed
Copy link

wawyed commented Jun 4, 2023

I had to add this to configuration.yaml:

http:
  use_x_forwarded_for: true
  trusted_proxies:
    - 127.0.0.1
    - 172.30.33.0/24

@MiddleSiggy
Copy link
Author

I have added every version of the trusted_proxies and more...

The developers for this add-on needs to add an easier way to support people with useful logs.

@github-actions
Copy link

github-actions bot commented Jul 6, 2023

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.

@github-actions github-actions bot added the stale label Jul 6, 2023
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jul 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants