Shellinabox broken (but dont know how to diagnose)

Hi,

I have shell in a box installed on port 4200 which has been working a treat for quite a long time (omv v.6)

to be clear this is not the plugin based version that worked with v5 of OMV it is a manual install.

I have ruled the router out by checking over the local lan and validated that the daemon is running (it is).

yet, when I browse to https (or http) ://192.168.0.3:4200 I now get a simple 404 page not found.

how can I diagnose what is going on as shellinabox is reported as running in SSH.

thanks

Dan

tek, I agree, but to my point ... it was working on .6 so I assume that apache is there behind the scenes?

D

ok, that makes sense, the update to omv would of stopped this working...

a follow up question .... is there a way to run shellinabox or a similar server side SSH host on nginx

D

ok, now i am officially lost (re the alias part).

also on my rig I have the nginx plugin running hosting two php sites with two pools.

the address to shellinabox is not responding and simply returns a 404.

D

both but primarily chrome... normally i would expect a different http error if it was browser specific (or even a blank page) this is a straight 404 almost like the request is blocked somewhere once it hits the omv box.

D

will try that when i get home tonight. that being the case, the address normally accessed from outside is a dns subdomain (server.hostname.com:4200), this would never work that being the case (and again it has worked in the past as until very recently it was my preferred method of ssh both local and remote).

D

would you not expect if it were a cert name error to get the standard "this site aint safe" warning and a proceed option instead of a straight 404.

D

Quick update still 404 by host name, DNS or ip....

Mostly chrome but getting nothing in either right now ... I'm happy to choose a browser that works...

D