Shellinabox broken (but dont know how to diagnose)

    Mmm I hear you re a plugin, the only problem is the biggest use for this is where I can't use putty like at work....


    Thanks for your continued support though you have pretty much taught me debian' !

    • Offizieller Beitrag

    That must be wrong. shellinabox is a web server itself that communicates on port 4200. The vt100.js file is client side that communicates with the shellinabox server over http/https protocol. Our plugin just proxies it to port 80.

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.1.6 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    • Offizieller Beitrag

    If I remember correctly, these packages have the patch.

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.1.6 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    • Offizieller Beitrag

    I just tried it on a VM. Works fine. Not sure what you did differently.


    Code
    wget http://omv-extras.org/debian/pool/main/s/shellinabox/shellinabox_2.14-1_amd64.deb
dpkg -i shellinabox_2.14-1_amd64.deb
apt-get -f install
Navigate to https://192.168.1.188:4200 and it works.

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.1.6 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    When you install shellinabox and the self signed certs are created they are using hostname if you have assigned one in OMV. If you try to sign on via https://ipofyouromv:4200 in ie11 it will not display the page. It works fine in chrome via https://ifofyoruomv:4200 or https://hostname:4200. In IE11 if you are trying to connect to https://ipofyouromv:4200 and it does not connect add this site to compatibility view and then you will be able to access the site, even given the cert/domain mismatch.


    After this you still need a different init script to allow root access and perhaps some changes to the arguments @ /etc/default/shellinabox.

    • Offizieller Beitrag

    Works on Firefox 31 and Chrome on my system.

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.1.6 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    IE11 just has stricter security.


    BTW, you can look here at the filename to see what domain was setup with the certs: /var/lib/shellinabox/


    Mine says certificate-kralizecvm.pem and kralizecvm is my hostname.


    I just noticed something crazy. If compatibility view is set for ipofyouromv you cannot access omv webgui via ipofyoruomv in IE11.


    This all such a PITA. Bottom line is you should use same hostname as your ipofomv, or use a hostname with everything and not use ipofyoruomv. I noticed these issues with other programs too (e.g. owncloud, openvpn, etc...)

    ok guys, thanks again, I will look at this when i am local to the machine again (im at work).... Im not convinced this is the issue as I am getting no response in any browser via any method (https, http, ip, dns or hostname) and they all return a 404 (almost like its not listening on the port 4200 or a port conflict).


    D

    ok, I had a look last night at this, the certificate in /var/lib/shellinabox and the name in there is my public dns name (server.XXXXXXXXXX.com) which is fine as thats the route i usually go .


    however, still no access (a straight 404 page not found) when browsing to server.xxxxxxxxxxxxxxx.com:4200 with either http or https


    D

    This problem with IE11 not resolving hostnames does not seem to be a cert/domain mismatch issue. If you connect via http with http:/ipofyouromv/ or http://hostname the hostname will not get the login screen. I tried on fedaykin and it works on IE11, and kralizec can't.


    The results were the same with or without ssl.

    Ok,


    this is the worst way to resolve a problem but here goes!


    yesterday there was an update to shellinabox showing on updates. I installed the update and before logging deleted the cert file from /var/lib/shellinabox once that was done I logged into shellinabox from chrome (by dns host name) and it works!


    do i know what was really wrong ? ... most definitely not, but it is now working which is good!


    D

  • chente

    Hat das Thema geschlossen.

Jetzt mitmachen!

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

Benutzerkonto erstellen Anmelden