So I was trying to setup a new server for a django app after a few hours I couln't make it work. For some reason with python manager 2.5 and aapanel 7 it doesn't work. The created at version 2.0 and 6 was flawless now there is no way to make it work even when I tried to do a django "blank" project. here is the video. https://drive.google.com/open?id=1-1qru2KNgcDPVI0Ocdx5QmrwrhJefQyb&usp=drive_fs

Hello, please check if your server can connect to the PyPI official source? Need to switch to a third-party source in your region? oscars

aaPanel_Kern The server can ping to pypi.org. so there is something wrong with that version. It was fixed after downgrading to aapanel 6.9. Let me know if you want me to test something else however I did try 3 fresh clean servers and was the same.

@aaPanel_Kern i have also same issue with python manager 2.5

Hello, do you have any error messages or screenshots? chandu

aaPanel_Kern no error just failed and modules are not installing if i try to install module by venv it was installling but project automatically shuting down . same like above drive video

aapanel python manager 2.5 doesn't with django?

aaPanel_Kern

Hello, try changing the pypi source available in all your regions. Is it okay to try deploying again?

chandu

aaP_demo1

chandu
For this issues, You can refer to my thread here

oscars

aaP_demo1

Hi there,

I can install the modules manually with the pip from the venv installed at the django folder and like you said they are installed over /www/server/python_manager/versions/3.12.0/lib/python3.12/site-packages/.

I can copy all of that folder to the venv site-packages folder. Howver the part that you said

I also created the binary file using the module file using this code

I don't understand this, did you just create a bin file with that code inside? is this file located at venv bin folder?

It's kind of sad that this problem existed since 2024 and it's still happening.

Thank you!

oscars

Just tried again migration the server to a bigger one and it's still happening...

oscars

After trying to fix python manager to work installing the modules over the venv folder created nothing worked.

I just reinstalled the old version of aapanel with

curl -k https://node.aapanel.com/install/py3.7_panel6_en.sh |bash

I recommend to anyone that have the same problem to keep using the old version until this is fixed.

Best Regards.

aaP_demo1

oscars
You would not need to reinstall the old panel version. I think python manager needs to optimize the start/restart project bugs. However, I suggest you to use supervisor on the App Store. still using it till now and have no issues.

aaP_demo1

oscars to make python manager install modules over the venv folder you should

cd path/to/directory
/www/wwwroot/yourproject/865...........................................d3ba_venv/bin/pip install -r requirements.txt

Your site-packages will be installed in the 865...........................................d3ba_venv/lib/python3.12/site-packages folder

oscars

aaP_demo1 It actually make sense because the Start/Suspended function doesnt work properly but with the 6.8 panel version it does. at the 7.x it says"check your error logs" however at the logs folder of the project there is nothing.

So there is something that change from 6.8 to 7.x and I can't make it work as intended.

oscars

aaP_demo1 I actually did this, and like you said at the panel version 7.x all the modules will be installed at /www/server/python/.... and not in the venv folder of the project so you have to manually copy from one folder to another every time you install something.

How does the "Running/Suspended" button work? what service is being called? I couldn't find it anywhere...

aaP_demo1

oscars You can try to deploy your project via command line first from your project directory. Then, install supervisor app at the App Store and create a new daemon using your project directory and the full command line to start your project.

to connect domain to the project, you should use proxy though.

oscars

aaP_demo1 Yes, you can do that but doing that it lost the purpose of "python manager" since you can map (to do the proxy) the daemon from python manager itself.

When it was working was a flawless feature but since the Python Manager 2.5 and Panel 7.x it's bugged.

I actually testest a Fresh Server without anything just python manager 2.5 and aaPanel latest version, clonning the django git and trying to install from Python Manager and it fails so it's a broken featured.

I'm testing the old panel version and it seems it's working as intended