Created a user and am trying to access user space via ssh It has no sites or domains OS is ubuntu (PW has always given me problems because of special characters in PW) In the SSH silo I'm seeing the correct IP and port (not 22, I'm assuming it is correct) username "root" and a PW that I changed a couple of times with a-z and 0-9 8+ byte PW what I am NOT seeing is that the port specified has been opened anywhere Get "access denied" in ssh (putty) Do I need to open the port? Where? openadmin is set to port 22 Any ideas? Thanks

worldhosting hello, what is the exact error message on ssh? Try with -vvv flag First Make sure that ssh Is enabled for user from their user panel. After that check on OpenAdmin > Security > Firewall Is the port open: if ufw there should be a rule for that port, else for csf check TCP_IN ports in csf.conf

everything checks out except in openpanel ssh says user = root in Ports listening for external connections: the userid = panel user name The error I get is "access denied" 32768 tcp 4/- - 380306 russromei rootlesskit --state-dir=/run/user/1000/dockerd-rootless --net=vpnkit --mtu=1500 --slirp4netns-sandbox=auto --slirp4netns-seccomp=auto --disable-host-loopback --port-driver=builtin --copy-up=/etc --copy-up=/run --propagation=rslave /home/russromei/bin/dockerd-rootless.sh /home/russromei/bin/rootlesskit

worldhosting as root user on that server: opencli user-login russromei Then set new ssh password: passwd exit with exit or ctrl + D and try from that same terminal to now login with the new password: ssh root@127.0.0.1:32768 -vvv Is that working? If it is, then try from your device using putty. If not, share the output

not working root@srv10:/var/www/html# ssh root@127.0.0.1:32768 -vvv OpenSSH_9.6p1 Ubuntu-3ubuntu13.5, OpenSSL 3.0.13 30 Jan 2024 debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 19: include /etc/ssh/ssh_config.d/*.conf matched no files debug1: /etc/ssh/ssh_config line 21: Applying options for * debug2: resolve_addr: could not resolve name 127.0.0.1:32768 as address: Name or service not known debug1: resolve_canonicalize: hostname 127.0.0.1:32768 is an unrecognised address debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts' -> '/root/.ssh/known_hosts' debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts2' -> '/root/.ssh/known_hosts2' debug2: resolving "127.0.0.1:32768" port 22 debug3: resolve_host: lookup 127.0.0.1:32768:22 ssh: Could not resolve hostname 127.0.0.1:32768: Name or service not known root@srv10:/var/www/html#

a week and no solution. this is why you test free versions before buying anything. See if it is supported

Hello, Please start by reading the sticky topic: How to ask for assistance? . You haven’t provided enough information for me to replicate the issue on the same OS and panel version, which makes it difficult to offer a solution or determine if it’s a bug. If you're able to reproduce this issue on the demo VPS , which has the same panel version and Ubuntu 24, then please report it as a bug. Otherwise, the issue might be related to something specific to the OS or your server, and will definitely need detail information in order to help. I also noticed I made a mistake while typing from my phone in previous reply: ssh root@127.0.0.1:32768 -vvv for port use -p flag, so it should be: ssh root@127.0.0.1 -p 32768 -vvv

Cannot ssh in

stefan

The existing SSH logic comes from when we had one container per user, with all services preinstalled. Back then, users could ssh into the container to manage services, files, and cron jobs. However, in the current setup—where each service runs in its own container—the main container with ssh no longer makes sense, as it only allows file management, not service control.

I've modified it to ssh into the host server instead but restricted users to the lazydocker container. This way, they can execute commands inside any container and monitor them. It gives them more flexibility but might be a learning curve for those used standard ssh and bit docker.

Pushing to testing now—this should be available in next week's update.

lazydocker on openpanel user

vandai

Hi Stefan,
I cannot connect to ssh.
I enabled ssh access from admin, then created user.
but everytime the user wants to connect with ssh, it always closed.
Here's what we got:

ssh

vandai

Hi @stefan ,
I cannot connect to ssh.
I enabled ssh access from admin, then created user.
but everytime the user wants to connect with ssh, it always closed.
Here's what we got:

SSH Error

stefan

vandai hello, might be related with Cannot login with new created user
, please update scripts from github, create new user and try again.

vandai

The app version is already up to date (v 1.1.9)
Cannot update again, it said "Already up to date"

Until now, I still cannot connect to SSH. And this also affect to the normal linux user (that not created by openpanel). Getting the same error.
Now i only able to connect to the server using VNC. My linux user cannot login, even the root user too.

stefan

vandai is ssh service running on the server? any errors in log?

Here is everything SSH-related on OpenPanel install: https://github.com/stefanpejcic/OpenPanel/blob/2de8757b1618c091951ae94346efea0812d545e7/install.sh#L676

so just try:

rm /etc/ssh/sshd_config.d/99-ssh-openpanel-users-settings.conf && systemctl restart sshd

vandai

Ok i see that it forced to use lazydocker.sh for user other than root
But the problem is the lazydocker returns the error as the screenshot i shared previously.
Sometimes it loads the lazydocker UI in terimnal, but then it closed immediately.

If i removed the lazydocker line (in 99 config file), i can login to ssh normally, and other users too. But this means the user access as normal linux user and he can access anywhere.
So i think need to fix on the lazydocker issue.

Have any idea why is that (on the error messages on the screenshot)?
Or have some workaround for that?

vandai

I managed to be able to capture the error messages:

^C2025/04/07 13:20:38 An error occurred! Please create an issue at https://github.com/jesseduffield/lazydocker/issues

*errors.errorString There was not enough window space to start the application
/tmp/gobuild/vendor/github.com/jesseduffield/gocui/gui_notwin.go:57 (0x7fa465)
/tmp/gobuild/vendor/github.com/jesseduffield/gocui/gui.go:104 (0x7f5a97)
/tmp/gobuild/pkg/gui/gui.go:226 (0x81b119)
/tmp/gobuild/pkg/gui/subprocess.go:20 (0x82bc25)
/tmp/gobuild/pkg/app/app.go:59 (0x835125)
/tmp/gobuild/pkg/app/app.go:59 (0x835117)
/usr/local/go/src/runtime/proc.go:250 (0x436332)
/usr/local/go/src/runtime/asm_amd64.s:1571 (0x463681)
.....

So i think there is some issue with lazydocker

stefan

looks like: https://github.com/jesseduffield/lazydocker/issues/211

remove the lazydocker image completelly from host os:

docker --context default image rm lazydocker

then it should be re-downloaded on next user login. is it ok then?

vandai

Running those command returns:
Error response from daemon: No such image: lazydocker:latest

So i run these instead:

docker images
docker rmi <image_id>

It was deleted, and when i tried to login to ssh again it shows that it is downloading the lazydocker again.
But after downloaded, it is still showing the same error and then force closed.

In docker images i see the image created 2 years ago, while in the github the latest realease was nov 2024.
How to get the latest version on this?

stefan

vandai you are right, it wasnt updated in years: https://hub.docker.com/layers/lazyteam/lazydocker/latest/images/sha256-cec8892650a2aaac25647eb120cf3316763db32b814253443fc863f522856883

maybe swith to build context: https://github.com/jesseduffield/lazydocker/blob/master/docker-compose.yml

Example: https://github.com/jesseduffield/lazydocker?tab=readme-ov-file#docker

I'll look into this

vandai

is that will be added in the next update release? or need to that manually? if manually, where should i do that?

and btw, since i need the user have access to ssh / terminal, i think web terminal is temporary solution for now.
But how to activate the web terminal?
I already enable the Web terminal in the admin, but when user clicks on the web terminal in his panel, the page showing timeout. Seems the terminal service is not running.

vandai

I finally managed to run the lazydocker.

I edited file /etc/openpanel/ssh/lazydocker.sh

Changed the exec command into this:

exec docker run --rm -it -v \
/hostfs/run/user/$USER_UID/docker.sock:/var/run/docker.sock \
-v $HOME:/.config/jesseduffield/lazydocker \
lazyteam/lazydocker

Login to SSH with the user account, lazydocker successfully loaded.
Then i pressed SHIT + E to switch to terminal mode.
Just a bit confusing because the user is now root.

@stefan any suggestion to improve the command? because i cannot use other parameters (like cpus, memory, pids-limit, security-opt, no-new-privileges), it will throw invalid parameter error.

And how about the web terminal? how to activate it?

stefan

vandai I dont have solution for terminal, ill add it on todo for when I have the time.

you are root user inside the cotnianer you mean, right? and not on the host-os?
that is ok, since its docker rootless, your root uid:0 in each container is actually uid of the OpenPanel user.