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

MFD unable to connect to /app when Security Profile is set to Weak or Secure #394

Open
mman opened this issue Aug 13, 2024 · 3 comments
Open
Labels
enhancement New feature or request wontfix This will not be worked on

Comments

@mman
Copy link
Collaborator

mman commented Aug 13, 2024

When Weak or Secure Security Profile is activated (version 3.50+), Venus nginx is protected with a password. No matter whether the /app is then requested via http:// or https:// the first load of the app on a MFD device requires password to be entered.

This is more of a reminder bug that we may want to address in the future depending on what the need is:

IMG_6025

@mman mman added the enhancement New feature or request label Aug 13, 2024
@mman mman added the wontfix This will not be worked on label Aug 29, 2024
@mman
Copy link
Collaborator Author

mman commented Aug 29, 2024

Marking as will not fix for now.

@mwielgoszewski
Copy link

FYI - I was able to get this working with my Garmin using the new "secured" profile by just allowlisting the IP address range of the Garmin ethernet network in the nginx config. I've got a short write up that you may consider implementing: https://gist.github.com/mwielgoszewski/aef6b729cf55fa18c96d35a2d828c49b

In my configuration, I omit using the auth_request module entirely. Another way to handle this would be by leveraging the satisfy any directive with auth_request and allow <ip>. This way, you can allowlist any devices that are directly connected to the ethernet network while requiring password auth from devices that connect to it over the wifi interface.

@mman
Copy link
Collaborator Author

mman commented Jan 8, 2025

Good suggestions @mwielgoszewski, will see which of these will work the best out of the box without much tweaking...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

2 participants