PDA

View Full Version : setting up chrooted ssh user, jailkit installed after ispconfig


bn61
15th March 2010, 12:31
I want to set up a chrooted ssh user. Everytime I try to login remotely the session gets closed immediately after the login.
I guess it has something to do that I installed jailkit (2.11) after I installed ISPConfig3. (It's working on another machine where I did it right.)ispconfig_update.sh... was not enough.
Any suggestions on how to fix that?

till
15th March 2010, 14:19
You have to update ispconfig again and select to reconfigure services. Use the manual update instructions for this.

Then delete the chrooted ssh user that you created before and recreate it.

bn61
15th March 2010, 14:56
I am drawing a blank on this. What do you mean byYou have to update ispconfig again and select to reconfigure services. Use the manual update instructions for this.?

till
15th March 2010, 15:00
Take a look in the ispconfig release notes, they contain a section called manual update instructions as you can not do the update with the ispconfig_update.sh again if the version installed on your system is the same then the version used for updating.

http://www.howtoforge.com/forums/showthread.php?t=44013

bn61
15th March 2010, 15:38
Still no luck.

till
15th March 2010, 15:46
Then you might have to recreate the website. The initail ssh jail for the website is created when you created the first ssh chrooted user. If jailkit was not installed properly before, this jail can be broken and jailing will not work then.

I recommend that you first test the jailkit functionality by creating a new dummy site with a domain like example.tld and then create a new jailed ssh user in this site. Wait a few minutes and if the jail works, then recreate the initial site.

bn61
15th March 2010, 17:19
I had to set up website and client new.

Thanks for your help!

lolo6tm
5th May 2011, 16:02
If you create zan SSH/Jailkit user using ISPConfig admin account it won't work, at least for me. You got to create it using the reseller/client account which owns the concerned website.

Hope it will help ...