App being installed: Leantime Project Manager
Steps taken:
•Add Web Domain (no mail support - no DNS support) named “sub.domain.com”
•Add SSL for “sub.domain.com” - SSL Error - No DNS
•Alter DNS from domain.com and add “sub” A-record pointing to IP of domain.com
•Add SSL for “sub.domain.com” - success
•check default site at https://sub.domain.com - working fine
•Install Leantime in …/public_html directory
•change webroot to …/public_html/public (as per leantime install docs)
•point browser to sub.domain.com/install - Internal Server Error: 500 (misconfiguration)
•Created a “check.php” file in same directory - Error: 500 again
Update:
•re-created check.php on different domain - executed fine
maybe the issue is the leantime app itself
Update 2:
disabled “.htaccess” in …/public_html and in …/public_html/public and the “check.php” file executed as normal. Maybe their traditional install process is over-engineered or something.
Would it break my hestia install if I added docker/portainer to this VPS? could be a possible global solution to some apps that have crazy install requirements.
I wouldn’t run around installing docker on a production hestiaCP machine. I assume it’s going to break SOMETHING.
To be honest, I can’t get docker working on my VPS provider AT ALL without some sort of failure. I’ll keep practicing.
Thanks for your input, I think I have figured out a work-around for my issue for now. I will use my Hestia for its SMPT and just use a cloudflared tunnel and run leantime from my homelab.
Check your log files but it should work fine…
1 Like
as @eris wrote, if you see a 500 error, you will find log entries, about what is wrong. how did you copy the files into your system? maybe they belong to the wrong user? maybe some php settings are off, modules missing, wrong php version etc.
the log files will tell you 
to be fair, docker does not break anything. it can easily coexist with hestia as after a plain installation there is nothing that really interferes with another.
of course it heavily depends on the container/app you want to run afterwards, what needs to be configured to make it accessible from the outside, but that does not mean, docker itself will break anything just because it is there
1 Like
other scripts work fine in domain or sub-domain installations. . . have installed prestacart and wordpress both ways and have done through the quick installer and manually. so that leads me to believe theres an issue specific to Leantime. And the fact that in the documentation, it says that for a subfolder installation, “uncomment line 4 of /public/.htaccess” but line 4 is not commented, that tells me something is off with their documentation. Without proper documentation, it will eat too much time for troubleshooting. faster to just abandon that install method for now, i can deploy it from homelab in docker in about 5 minutes and just use my VPS for the email side.
I didn’t know that. I’ll have to get better at it then.
I’ve been looking towards CyberPanel and other sources for trying to be able to run Node.js and Python and other stuff.
I’m not really DEAD SET on docker. I’m a database guy, I don’t want a random reboot to LOSE DATA. That’s how I see Docker, I don’t really understand the whole persistence thing. And I have SSL errors on my HomeLan (I can’t figure out split-DNS)
yeah, Docker appears easy with running installations with just a command and that kind of promises. almost always this requires an empty environment though.
kinda beats the purpose of containers and degrades docker to some tool for offering somewhat easy installation for people with no admin/linux knowledge.
I always aim for running source installs instead but probably I am just old fashioned. ofc maintaining and updating these kinda installs might be more work, so be it
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.