> @hennaboy said:
> The webservice config is set to use port 22 and root with the ssh key set in the ssh keys.
>
> You should check the port you are using and if you are permitting root login.
>
> I am looking into being able to alter this with further options.
> @hennaboy said:
> The webservice config is set to use port 22 and root with the ssh key set in the ssh keys.
>
> You should check the port you are using and if you are permitting root login.
>
> I am looking into being able to alter this with further options.
I’ve disabled root from cyberpanel itself, so shouldn’t it have made the changes to the web terminal as well?
I updated, but it still doesn’t work. However, when i re-enabled the root user from cyberpanel itself, the web terminal started working. However, as soon as I disable the root user (again, from cyberpanel itself), the web terminal stops working again.
> @hennaboy said:
> My sshd_config has the following settings
>
> Port xxx
>
> should be the port you have selected in securessh or 22 - If you change the port dont forget you need to add it to any firewall you are running
>
> PermitRootLogin without-password
>
> the webTerminal will not run from another user with the current configuration. So this is requesting that a key be used and password input is not accepted unless the key has a pass phrase
>
> PasswordAuthentication no
>
> same as above passwords are not accepted
>
> Ensure that the webTerminal port is also in your firewall this is port 5678 and is added when you run the upgrade for cyberpanel but just in case double check it is there.
>
> using the above I can access the webTerminal
Works like a charm! Apologies for the late response, I was very busy.
> @hennaboy said:
> My sshd_config has the following settings
>
> Port xxx
>
> should be the port you have selected in securessh or 22 - If you change the port dont forget you need to add it to any firewall you are running
>
> PermitRootLogin without-password
>
> the webTerminal will not run from another user with the current configuration. So this is requesting that a key be used and password input is not accepted unless the key has a pass phrase
>
> PasswordAuthentication no
>
> same as above passwords are not accepted
>
> Ensure that the webTerminal port is also in your firewall this is port 5678 and is added when you run the upgrade for cyberpanel but just in case double check it is there.
>
> using the above I can access the webTerminal
WebTerminal broke yet again after I upgraded cyberpanel the previous time. I upgraded again today and it still seems to be broken. No clue what went wrong, the configs are exactly the way that you told me to set them up a while back.
> @hennaboy said:
> You will always need to use a real terminal anyway as you cannot upgrade CP using the web terminal.
>
> So just continue to use an ssh terminal program?
>
>
>
>
Well I almost always do... but the web terminal has saved my butt a while ago when I locked myself out of ssh due to a stupid mistake (don’t give me hell for that... learned my lesson)
Anyways this isn’t by any means a priority, so feel free to ignore it.
Comments
> Being looked into. Thanks for your post.
Thank you! I appreciate your efforts!
Change file; /usr/local/CyberCP/WebTerminal/CPWebSocket.py
self.sshclient.connect('127.0.0.1', 22, username='root', pkey=k)
replace port 22 here
then restart the ssh server and kill CPWeb process
ps aux | grep CPWeb
kill -9 pid number
> Hello,
>
> Change file; /usr/local/CyberCP/WebTerminal/CPWebSocket.py
>
> self.sshclient.connect('127.0.0.1', 22, username='root', pkey=k)
>
> replace port 22 here
>
> then restart the ssh server and kill CPWeb process
>
> ps aux | grep CPWeb
>
> kill -9 pid number
Did that to no avail. The issue persists.
I haven't tried, but change root in this file.
self.sshclient.connect ( '127.0.0.1', 22, username = 'root', pkey = k)
> Yes,
>
>
> I haven't tried, but change root in this file.
>
>
> self.sshclient.connect ( '127.0.0.1', 22, username = 'root', pkey = k)
I’ve already tried that too, along with the new port. Same issue.
But my server is work to different port.
http://prntscr.com/pvdm0o
You can get the fix using new upgrade guide -> https://cyberpanel.net/docs/upgrading-cyberpanel/
You will also have to restart SSH web server.
> The webservice config is set to use port 22 and root with the ssh key set in the ssh keys.
>
> You should check the port you are using and if you are permitting root login.
>
> I am looking into being able to alter this with further options.
> @hennaboy said:
> The webservice config is set to use port 22 and root with the ssh key set in the ssh keys.
>
> You should check the port you are using and if you are permitting root login.
>
> I am looking into being able to alter this with further options.
I’ve disabled root from cyberpanel itself, so shouldn’t it have made the changes to the web terminal as well?
> I fixed the issue when port other then 22 is used -> https://github.com/usmannasir/cyberpanel/commit/54f83c3d7887e121e4ebfa72a0e07d00fc22619c
>
> You can get the fix using new upgrade guide -> https://cyberpanel.net/docs/upgrading-cyberpanel/
>
> You will also have to restart SSH web server.
Thank you! Will try it in a few hours and update you on the outcome.
> I fixed the issue when port other then 22 is used -> https://github.com/usmannasir/cyberpanel/commit/54f83c3d7887e121e4ebfa72a0e07d00fc22619c
>
> You can get the fix using new upgrade guide -> https://cyberpanel.net/docs/upgrading-cyberpanel/
>
> You will also have to restart SSH web server.
I updated, but it still doesn’t work. However, when i re-enabled the root user from cyberpanel itself, the web terminal started working. However, as soon as I disable the root user (again, from cyberpanel itself), the web terminal stops working again.
Can you look into this too please?
> Change to
>
> PermitRootLogin without-password
Change what exactly? Is there a file i need to make these changes to?
> Sorry used to persons knowing where to look.
>
> /etc/ssh/sshd_config on Centos or the location of ssh config on other distro's
I did those changes then rebooted the ssh server, same issue!
> What do you have set in the sshd_config for PasswordAuthentication
It’s set as “yes”
> My sshd_config has the following settings
>
> Port xxx
>
> should be the port you have selected in securessh or 22 - If you change the port dont forget you need to add it to any firewall you are running
>
> PermitRootLogin without-password
>
> the webTerminal will not run from another user with the current configuration. So this is requesting that a key be used and password input is not accepted unless the key has a pass phrase
>
> PasswordAuthentication no
>
> same as above passwords are not accepted
>
> Ensure that the webTerminal port is also in your firewall this is port 5678 and is added when you run the upgrade for cyberpanel but just in case double check it is there.
>
> using the above I can access the webTerminal
Works like a charm! Apologies for the late response, I was very busy.
> My sshd_config has the following settings
>
> Port xxx
>
> should be the port you have selected in securessh or 22 - If you change the port dont forget you need to add it to any firewall you are running
>
> PermitRootLogin without-password
>
> the webTerminal will not run from another user with the current configuration. So this is requesting that a key be used and password input is not accepted unless the key has a pass phrase
>
> PasswordAuthentication no
>
> same as above passwords are not accepted
>
> Ensure that the webTerminal port is also in your firewall this is port 5678 and is added when you run the upgrade for cyberpanel but just in case double check it is there.
>
> using the above I can access the webTerminal
WebTerminal broke yet again after I upgraded cyberpanel the previous time. I upgraded again today and it still seems to be broken. No clue what went wrong, the configs are exactly the way that you told me to set them up a while back.
Here’s the error:
Connecting...
Error connecting to backend.
connection closed.
> You will always need to use a real terminal anyway as you cannot upgrade CP using the web terminal.
>
> So just continue to use an ssh terminal program?
>
>
>
>
Well I almost always do... but the web terminal has saved my butt a while ago when I locked myself out of ssh due to a stupid mistake (don’t give me hell for that... learned my lesson)
Anyways this isn’t by any means a priority, so feel free to ignore it.
https://s12.directupload.net/images/200615/fmceru94.png