Recommendation for WeTTY

Quote from gregeeh

Hi all,

What's the recommended way to install WeTTY on OMV6? Via the Plug-in or Docker?

TIA

Either one. They are essentially the same best I can tell. Wetty (the plugin) runs on Podman, where the other would run on docker.

One thing, if you reverse proxy wetty (which I do)... the main docker-container for wetty requires the the URL end in /wetty, which makes it a pain to reverse proxy with swag... but it's relatively easy to overcome. Either way however, both work exactly the same.

Only other caveat.. I *think* the plugin is only available for amd64. So if you're using a Pi or other SBC.. you'll need to use the docker container...

https://hub.docker.com/r/wettyoss/wetty:

Here's the command to install it. The -b trigger on the end will allow you to use it at server-ip:port instead of server-ip:port/wetty

docker run --restart=always --name=wetty1 -p 3000:3000 wettyoss/wetty --ssh-host=YOUR.SERVER.IP -b

Quote from gregeeh

Thanks for your prompt reply.

I tried using a Portainer Stack:

Code

services:
    wetty:
    container_name: wetty
    environment:
        - REMOTE_SSH_SERVER=192.168.10.2
        - REMOTE_SSH_PORT=22
        - REMOTE_SSH_USER=root
        - PUID=1000
        - PGID=100
        - TZ=Australia/Sydney
    ports:
        - '3000'
    labels:
        - "diun.enable=true"
    hostname: wetty.localdomain
    network_mode: bridge
    restart: unless-stopped
    image: wettyoss/wetty

Display More

And it's looking like this in Portainer. Note the port number.

And I cannot login using any of those port numbers. Just shows " Cannot Get /".

Display More

1. Your ports are wrong... shouldn't that be something like:

porty-youwant:3000

As for the labels, hostname, etc. I've never messed with it like that

However, after fixing your ports I suspect you'd have to access it at wetty.localdomain/wetty (at least that has been my experience with it)