-
Notifications
You must be signed in to change notification settings - Fork 308
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
Failure accessing from different networks - PyO3 modules may only be initialized once per interpreter process #3875
Comments
Thank you for filing an issue and sharing your observations or ideas. Please be sure to provide as much information as possible to help us to work on this issue. |
I discovered the issue, I think at https://github.com/privacyidea/privacyidea/blob/master/deploy/apache/sites-available/privacyidea.conf and comparing it to the https://privacyidea.readthedocs.io/en/latest/installation/system/wsgiscript.html#wsgi-configuration-for-the-apache-webserver minimal settings. The |
Ah Yes, we should remove that "deploy" directory or at least consolidate it with the documentation and the package build scripts. |
That deploy directory is good because it shows examples of the whole configuration and gives a global vision. If you integrate it into the documentation, it should expand the current section (in Apache HTTP Server as example) by a lot. |
Top-level intent
Accessing privacyIDEA webui from different networks to which Apache HTTP Server has access to.
Steps to reproduce
Expected outcome
Both requests should have been successful
Actual outcome
Second request failes with 500 server error on Apache HTTP Server side
Configuration
Log file
Additional notes
This error does not exist in a previous test using privacyIDEA 3.8.x. Initially I thought that was the Python version as it was tested with 3.11 which is not yet supported but this also failed with 3.9 which should be supported properly so I created another environment using Debian 11 which ships Python 3.9 by default and could reproduce the error.
The text was updated successfully, but these errors were encountered: