-
-
Notifications
You must be signed in to change notification settings - Fork 21
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
http listener not started after upgrade #239
Comments
With 1.20 I introduce AppArmor profiles to increase the application security of openvpn-auth-oauth2. It cloud be possible that the profile is configured too strong. Without any logs, from
I can't assist here. |
Tried to run the demo, doesn't work for me either. Last working version for me is 1.19.1 Didn't dive deep into code but for tls = false shouldn't it just be ListenAndServe here? 🙂
|
You are right. Huch. And there was an additional bug that errors from http listener are never returned. |
I can confirm it works now. Thank you very much. |
Current Behavior
When I update openvpn-auth-oauth2 from openvpn-auth-oauth2_1.18.0_linux_amd64.deb to openvpn-auth-oauth2_1.20.0_linux_amd64.deb, the configured http listener on port 9000 does not start. It reports it has started in the logs but ss - tulpn reports nothing listening on that port. Reverting to version 1.18 fixes the issue.
Expected Behavior
Start the listener normally.
Steps To Reproduce
Environment
openvpn-auth-oauth2 logs
No response
openvpn server logs
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: