We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
See issues #61 and #62
Not only web frontend and RADIUS server are toasted, but also the captive portal - requiring a third way of implementing the customized certs.
The text was updated successfully, but these errors were encountered:
So, during my research today I found out that any custom SSL certificate will break WiFiMan (official confirmation here).
So, no more need to fiddle around with full chain vs. server only certificates. I could say "nice" but would rather prefer an OEM solution.
Sorry, something went wrong.
ddd6948
alxwolf
Successfully merging a pull request may close this issue.
See issues #61 and #62
Not only web frontend and RADIUS server are toasted, but also the captive portal - requiring a third way of implementing the customized certs.
The text was updated successfully, but these errors were encountered: