WeTTY Plugin Connection refused

1. offizieller Beitrag

    Hi,


    I installed the WeTTY plugin that recently came out.

    Although webpage opens fine when I enter any user name (without even been asked for a password)

    I get "connection refused"


    I initially had issues with the new File Browser plugin and with WeTTY. When installed both webpages where unreachable.

    After a reboot both pages are accessible and while File Browser works fine I still have the problem with WeTTY.



    **Screenshots**



    Linux openmediavault 5.16.0-0.bpo.4-amd64 #1 SMP PREEMPT Debian 5.16.12-1~bpo11+1 (2022-03-08) x86_64 GNU/Linux



    • Offizieller Beitrag

    That's strange, it was working some days ago while i have developed the plugin. Looking at the changelog and DockerHub i realized that there is a new container out since then. I assume something has changed in the meanwhile. maybe a regression in the container.


    Since two days there is version 2.4 out, maybe 2.3 will work. Need to check that.

    • Offizieller Beitrag

    Due the fact that the plugin has worked at 21.03.2022 (the date the plugin was created) the following packages have been installed on my test system:


    Code
    podman:amd64 (3.0.1+dfsg1-3+b2, 3.0.1+dfsg1-3+deb11u1), 
libc-l10n:amd64 (2.31-13+deb11u2, 2.31-13+deb11u3), 
libc-bin:amd64 (2.31-13+deb11u2, 2.31-13+deb11u3), 
systemd-sysv:amd64 (247.3-6, 247.3-7), 
golang-github-containers-common:amd64 (0.33.4+ds1-1, 0.33.4+ds1-1+deb11u1), 
openssl:amd64 (1.1.1k-1+deb11u2, 1.1.1n-0+deb11u1)

    This means one of those packages have introduced something that breaks the WeTTY app.


    I assume it has something to do with SECCOMP because i found this in the logs.


    Code
    Mar 30 07:08:16 omv6box systemd[1]: Started WeTTY (Web + TTY) container.
Mar 30 07:08:16 omv6box systemd[1]: run-rc7dd5c0653644ee882108d6254792f4a.scope: Succeeded.
Mar 30 07:08:16 omv6box audit[6104]: SECCOMP auid=4294967295 uid=0 gid=0 ses=4294967295 subj==containers-default-0.33.4 (enforce) pid=6104 comm="node" exe="/usr/local/bin/node" sig=0 arch=c000003e syscall=324 compat=0 ip=0x7f5a5ec0713b code=0x50000
Mar 30 07:08:16 omv6box kernel: audit: type=1326 audit(1648624096.635:30): auid=4294967295 uid=0 gid=0 ses=4294967295 subj==containers-default-0.33.4 (enforce) pid=6104 comm="node" exe="/usr/local/bin/node" sig=0 arch=c000003e syscall=324 compat=0 ip=0x7f5a5ec0713b code=0x50000

    I just ran into this same issue. Was working a few days ago, no system changes since.

    That said, I'm on OMV5, and Wetty is hosted in docker with the svenihoney/wetty image.

    I'm using the IP not the fqdn, and I've tried logging in with multiple users.

    Hello,


    I installed OMV 6 yesterday and did the system update and reboot after doing so. Installed wetty from plugins and when I tried to login I am getting the message

    ssh: could not resolve hostname nas1 name does not resolve.


    I have another OMV 6 running on Proxmox VM and it is working just fine. See attached pictures.


    Do you have any idea what can be wrong? I can SSH to same server with putty no problem.


    Thank you in advance for the suggestions.


    RT

    for getting wetty to work, you need first to install openmediaextras and activate docker. After that wetty will work without problems. This because its not a aplication but an docker image. ;)

    • Offizieller Beitrag
    Zitat von chipcat

    for getting wetty to work, you need first to install openmediaextras and activate docker. After that wetty will work without problems. This because its not a aplication but an docker image. ;)

    No, wetty is an application that runs on podman... docker is not required. If you install the wetty plugin from the plugins list, it will set everything up for you.

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!

Benutzerkonto erstellen Anmelden