You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The split-pro script is ready for testing: bash -c "$(curl -fsSL https://github.com/community-scripts/ProxmoxVED/raw/main/ct/split-pro.sh)"
Before first use you must configure email credentials or authentication (OAuth/OIDC) provider in /opt/split-pro/.env and restart the service systemctl restart split-pro.
Receipt uploads are stored in /opt/split-pro_data/uploads
Note: This is not in the official repo yet—it's just a dev version! After merging into ProxmoxVE, it will need to be recreated.
Tried installing it and I get this error towards the end:
✔️ Customized LXC Container
curl: (22) The requested URL returned error: 404
✔️ Completed successfully!
🚀 Split Pro setup has been successfully initialized!
💡 Access it using the following URL:
🌐 http://192.168.0.76:3000
Also unlike other LXC, this one requires a username/password to access it.
Unable to test after initial install as login details for container are unknown, please advise and will retest.
@CerberusStyle the answer is literally 2 messages over your question :D
Before first use you must configure email credentials or authentication (OAuth/OIDC) provider in /opt/split-pro/.env and restart
Unable to test after initial install as login details for container are unknown, please advise and will retest.
@CerberusStyle the answer is literally 2 messages over your question :D Before first use you must configure email credentials or authentication (OAuth/OIDC) provider in /opt/split-pro/.env and restart
Now reread my comment the ' container ' has login details so that command cannot be run as shell cannot be accessed.
I get this issue as well. I experienced this issue at the beginning of my local testing writing this script. There seems to be something off with the community script tools. It fails to get the install script split-pro-install.sh.
Little update: It creates a container called splitpro. I think this might indicate that i looks for splitpro-install.sh. There must be a tiny spelling issue. In split-pro.sh it has to be APP="Split-Pro".
Ok install seems to at least complete as expected and we now have access to the container which is great but before after configuring, when accessing the web UI " internal server error " is displayed. where as before the login page was shown but unable to be used.
At this point I'm going to bow out and we can wait for summoningpixels to run a test on this again see if he gets any issues to or if it runs fine for him or not.
Activity
github-actions commentedon Feb 13, 2026
The split-pro script is ready for testing:
bash -c "$(curl -fsSL https://github.com/community-scripts/ProxmoxVED/raw/main/ct/split-pro.sh)"Before first use you must configure email credentials or authentication (OAuth/OIDC) provider in
/opt/split-pro/.envand restart the servicesystemctl restart split-pro.Receipt uploads are stored in
/opt/split-pro_data/uploadsNote: This is not in the official repo yet—it's just a dev version! After merging into ProxmoxVE, it will need to be recreated.
summoningpixels commentedon Feb 13, 2026
Tried installing it and I get this error towards the end:
Also unlike other LXC, this one requires a username/password to access it.
CerberusStyle commentedon Feb 13, 2026
Unable to test after initial install as login details for container are unknown, please advise and will retest.
fbnlrz commentedon Feb 13, 2026
@CerberusStyle the answer is literally 2 messages over your question :D
Before first use you must configure email credentials or authentication (OAuth/OIDC) provider in /opt/split-pro/.env and restart
CerberusStyle commentedon Feb 14, 2026
Now reread my comment the ' container ' has login details so that command cannot be run as shell cannot be accessed.
johanngrobe commentedon Feb 15, 2026
I get this issue as well. I experienced this issue at the beginning of my local testing writing this script. There seems to be something off with the community script tools. It fails to get the install script
split-pro-install.sh.johanngrobe commentedon Feb 15, 2026
Little update: It creates a container called
splitpro. I think this might indicate that i looks forsplitpro-install.sh. There must be a tiny spelling issue. Insplit-pro.shit has to beAPP="Split-Pro".johanngrobe commentedon Feb 15, 2026
I was able to install split pro successfully.
CerberusStyle commentedon Feb 15, 2026
Ok install seems to at least complete as expected and we now have access to the container which is great but before after configuring, when accessing the web UI " internal server error " is displayed. where as before the login page was shown but unable to be used.
johanngrobe commentedon Feb 15, 2026
I was not able to reproduce. The application needs a few seconds to start. What does
systemctl status split-prosay?Some logs from
journalctl -u split-pro -fwould be nice as well.CerberusStyle commentedon Feb 15, 2026
yer its a tons of errors over and over, on a fresh install, so something is still not right with it somewere.
johanngrobe commentedon Feb 15, 2026
I am pretty sure there is something wrong in your config.
journalctl -u split-pro -n 100would be more helpful to see the full log.2 remaining items
CerberusStyle commentedon Feb 16, 2026
At this point I'm going to bow out and we can wait for summoningpixels to run a test on this again see if he gets any issues to or if it runs fine for him or not.
summoningpixels commentedon Feb 16, 2026
It now installs fine on my end and I do get the web interface once the smtp options are filled out as per @johanngrobe's comment
CerberusStyle commentedon Feb 16, 2026
Sweet thanks must be me, thanks for testing it.
johanngrobe commentedon Mar 2, 2026
Is there anything I can do to make the next step?
github-actions commentedon Mar 16, 2026
A PR has been created for split-pro: community-scripts/ProxmoxVE#12975
michelroegl-brunner commentedon Mar 18, 2026
Merged with #12975 in ProxmoxVE
github-actions commentedon Mar 18, 2026
Files deleted with PR #1586