ShellHub/community

gapaluec

@gapaluec

@gustavosbarreto I did change the docker-compose.yml, but still the endpoint API was returning 22
{"api":"localhost", "ssh": "localhost:22", "mqtt": "localhost:1883"}

Also, there should be an option to change "localhost" returned by endpoint to a valid domain name / ip address... As I was trying shellhub on AWS with a domain name.

I can see that port 22 is hardcoded in https://github.com/shellhub-io/shellhub/blob/ee6d67a609310611a05f0639dd6c939c63cfc2f2/gateway/shellhub.conf#L62

Luis Gustavo S. Barreto

@gustavosbarreto

@gapaluec

Luis Gustavo S. Barreto

@gustavosbarreto

@gapaluec can you please open a issue for this?

Luis Gustavo S. Barreto

@gustavosbarreto

@gapaluec shellhub-io/shellhub#20

Luis Gustavo S. Barreto

@gustavosbarreto

New release: https://github.com/shellhub-io/shellhub/releases/tag/v0.0.2

surfinside

@surfinside

Hello,
I would like mount an ssh tunnel, unfortunately I have an error

channel 2: open failed: unknown channel type: unsupported channel type
debug1: channel 2: free: direct-tcpip: listening port 443 for 10.10.10.1 port 443, connect from 127.0.0.1 port 51926 to 127.0.0.1 port 443, nchannels 4
channel 3: open failed: unknown channel type: unsupported channel type
debug1: channel 3: free: direct-tcpip: listening port 443 for 10.10.10.1 port 443, connect from 127.0.0.1 port 51927 to 127.0.0.1 port 443, nchannels 3

MyPC - > INTERNET -> ShellHub <- INTERNET <- Router (10.10.10.1/24) <- RPi (Up on ShellHub (10.10.10.xxx/24))
MyPC:443 = https://10.10.10.1
I thank you in advance

Luis Gustavo S. Barreto

@gustavosbarreto

@surfinside Are you trying to create a tunnel through ShellHub server?

I think this is not supported by ShellHub

https://github.com/shellhub-io/shellhub/blob/master/ssh/server.go#L47

Accoring to this the supported channel types:

"tcpip-forward":        forwardHandler.HandleSSHRequest,
"cancel-tcpip-forward": forwardHandler.HandleSSHRequest,
"tcpip-forward-connected":

direct-tcpip is not supported

surfinside

@surfinside

@gustavosbarreto Thank you for your reply
Yes, i would like create a ssh tunnel with a other device on the LAN of device up in shellhub and mypc with internet.
Ex : MyPC - > INTERNET -> ShellHub <- INTERNET <- RPi (Up on ShellHub (10.10.10.101/24)) | Other RPi with nginx 80&443 (10.10.10.102/24)
mypc:9999 = 10.10.10.102:443
mypc:9998 = 10.10.10.102:80

ssh -L 9999:10.10.10.102:443 pi@rpiname.usershellhub@subname.mydomain.com

What do you think about this ? This is supported by ShellHub ?
https://wiki.archlinux.org/index.php/VPN_over_SSH

surfinside

@surfinside

Hello, i found a solution with
https://github.com/sshuttle/sshuttle
I love ShellHub :)
it's possible to add https with certbot ?
For mongodb, why not add persistent data ?
On Gateway or Ui docker, it's possible to add fail2ban (SSH & Ngnix Jail) ?
Thank you

Luis Gustavo S. Barreto

@gustavosbarreto

t's possible to add https with certbot ?

@surfinside HTTPS support is on our roadmap (end Q1 2020)

For mongodb, why not add persistent data ?

@surfinside You can do this by extending the docker-compose file

Luis Gustavo S. Barreto

@gustavosbarreto

On Gateway or Ui docker, it's possible to add fail2ban (SSH & Ngnix Jail) ?

@surfinside Can you please explain this in more detail?

I love ShellHub :)

@surfinside I'm really appreciate and very pleased to hear that you enjoyed it

Otavio Salvador

@otavio

:-)

haydenbarton96

@haydenbarton96

Hi, Im trying to run 'docker-compose up id' and it says its running on port 22 but i changed the port to 2222 in docker-compose.yml and it doesnt seem to be changing (im trying to keep the openssh port as 22) am i doing something wrong?

Luis Gustavo S. Barreto

@gustavosbarreto

@haydenbarton96 change the SHELLHUB_SSH_PORT variable inside .env file instead of docker-compose.yml

Revert the changes that you made to docker-compose.yml and edit the .env

haydenbarton96

@haydenbarton96

Thank you for the fast reply! However i cant find a .env file, just the docker-compose .yml and .dev.yml files, is it in a different directory to shellhub-v0.1.1?

Ah I found it, the file was just hidden, i just used nano .env in that directory. No errors and everything says its done, but nothing on the localhost, it is port 80 or 8080 isnt it?

haydenbarton96

@haydenbarton96

I get a login screen on port 18083 but the account i added successfully doesnt login and shows "username not found"

Luis Gustavo S. Barreto

@gustavosbarreto

@haydenbarton96 The WebUI is available at http://localhost

@haydenbarton96 Can you please paste the output of docker-compose logs ui?

haydenbarton96

@haydenbarton96

I'm running on a raspberry pi and have been connected through ssh from my pc on the same network, going to the ip of the pi with port 80 or without any port doesnt show anything, but going to the ip of the pi with port 18083 shows the EMQ dashboard, ill post logs now

Attaching to shellhub-v011_ui_1
ui_1 | standard_init_linux.go:211: exec user process caused "exec format error"
ui_1 | standard_init_linux.go:211: exec user process caused "exec format error"
ui_1 | standard_init_linux.go:211: exec user process caused "exec format error"

haydenbarton96

@haydenbarton96

@gustavosbarreto im googling the error now too, but strange that no errors at all came up during the entire install of docker, docker compose and shellhub

Luis Gustavo S. Barreto

@gustavosbarreto

@haydenbarton96 are you running ShellHub server on a RaspberryPi?

ShellHub server is intended to run on x64 (standard PC or VPS like AWS, Azure, DO, etc..)

On your Pi you should install ShellHub Agent instead

Luis Gustavo S. Barreto

@gustavosbarreto

Think ShellHub as your centralized SSH server for all your Pi fleet

I admit that our documentation is not the best, but we appreciate your feedback and will try to improve the documentation whenever we can

Luis Gustavo S. Barreto

@gustavosbarreto

I just released the next major version of ShellHub (v0.2.0) with significant improvements. Check it out

haydenbarton96

@haydenbarton96

Yes im running on the raspberry pi 4 with 64 bit ubuntu, i will look into shellhub agent and shellhub v0.2.0, thank you :)

Rohit Joshi

@rjoshi

I am running ShellHub V0.0.5 what is the proper way to update server and Agent to new version?

With V0.0.5 I often face an issue where Device shows as online on the server but when I try to SSH session fails. Only way to recover from this is to restart agent container at the device. Is this a known issue?

Luis Gustavo S. Barreto

@gustavosbarreto

@rjoshi I'm sorry for the late reply

To update the server you need to checkout the latest released tag (v0.2.0)

Luis Gustavo S. Barreto

@gustavosbarreto

Then stop the server by running 'docker-compose stop' and start it again running 'docker-compose up - d'

To update the agent you need to it manually

Follow these steps:

Stop the container: docker stop shellhub

Remove the container: docker rm shellhub

Luis Gustavo S. Barreto

@gustavosbarreto

Open the new Web UI and add the device by clicking on 'Add device' button

Automatic updates is on our roadmap

Where communities thrive

People

Repo info

Activity