Graham Dumpleton
Graham Dumpleton
Did you make any progress on this? I still don't have any good ideas. Only thing can think of is that mod_wsgi is not setup correctly to use the same...
What do you get when you run: ``` which python3 ``` Does it come from a virtual environment or main system installation? If a virtual environment, was it created before...
Can you also try the `pip install` method for installing mod_wsgi. See: * https://pypi.org/project/mod-wsgi/
Since Apache can't even load the `python311.dll` file, ensure the following: * Both Apache and Python are 64 bit apps. Python appears to be 64 bit, but Apache must also...
What do you get when you run: ``` ls -las /etc/httpd/modules/mod_wsgi.so ``` and: ``` ldd /etc/httpd/modules/mod_wsgi.so ``` What flavour of Linux are you on? Debian/Ubuntu, or some form of Red...
BTW, at this point there has been no attempt to compile mod_wsgi with Apache 2.5 (dev stream) so it isn't known if it will even work for the future Apache...
What URL are using to access the WSGI application? At a guess I would say you might have a different `VirtualHost` for port 80 which is getting used in preference...
Sorry, there is possibly no simple fix for this. If they have made connection construction completely private that may prevent mod_wsgi even being able to do what it needs to...
Ensure you have latest `pip` installed. I believe there was an issue with one version on Windows that caused this.
Try using one of more `-v` options to `pip` then to try and coax it to give more detailed log output so can see where problem comes from.