Arch Linux

goodwinmcd

Member

Registered: 2016-03-21

Posts: 26

Shellinabox

Trying to set my computer up to be accessed remotely through my browser.  I downloaded shellinabox using

yaourt shellinabox

I tried starting it with

systemctl start shellinaboxd

But that didn't work.  So then I just did

shellinaboxd -b

and it's acting like it is running but I do not see anything on port 4200 and it is not loading when I go to "ipaddress:4200" in my browser.  I read the manual and am stuck.  Any alternatives to shellinabox for arch?

Can someone help me out? Thanks.

edit:  Tried gateone.  It shows that it's listening on port 443 but still can't connect to it.  I'm just using all the default config giles and this is the error I'm getting.

I 160817 15:31:45 server:4492] Listening on https://*:443/
[I 160817 15:31:45 server:4545] Process running with pid 8335
[W 160817 15:32:05 iostream:1276] SSL Error on 16 ('192.168.1.105', 54132): [SSL: HTTP_REQUEST] http request (_ssl.c:590)
[W 160817 15:32:05 iostream:1276] SSL Error on 16 ('192.168.1.105', 54134): [SSL: HTTP_REQUEST] http request (_ssl.c:590)
[W 160817 15:32:05 iostream:1276] SSL Error on 16 ('192.168.1.105', 54136): [SSL: HTTP_REQUEST] http request (_ssl.c:590)
[W 160817 15:32:05 iostream:1276] SSL Error on 16 ('192.168.1.105', 54138): [SSL: HTTP_REQUEST] http request (_ssl.c:590)
[W 160817 15:32:05 iostream:1276] SSL Error on 16 ('192.168.1.105', 54140): [SSL: HTTP_REQUEST] http request (_ssl.c:590)
[W 160817 15:32:05 iostream:1276] SSL Error on 16 ('192.168.1.105', 54142): [SSL: HTTP_REQUEST] http request (_ssl.c:590)
[W 160817 15:32:05 iostream:1276] SSL Error on 16 ('192.168.1.105', 54144): [SSL: HTTP_REQUEST] http request (_ssl.c:590)
[W 160817 15:32:05 iostream:1276] SSL Error on 16 ('192.168.1.105', 54146): [SSL: HTTP_REQUEST] http request (_ssl.c:590)
[W 160817 15:32:05 iostream:1276] SSL Error on 16 ('192.168.1.105', 54148): [SSL: HTTP_REQUEST] http request (_ssl.c:590)
[W 160817 15:32:05 iostream:1276] SSL Error on 16 ('192.168.1.105', 54150): [SSL: HTTP_REQUEST] http request (_ssl.c:590)
[I 160817 15:32:15 async:514] Shutting down the MultiprocessRunner executor.
[W 160817 15:32:44 iostream:1276] SSL Error on 12 ('192.168.1.112', 45261): [SSL: HTTP_REQUEST] http request (_ssl.c:590)
[W 160817 15:32:44 iostream:1276] SSL Error on 12 ('192.168.1.112', 45262): [SSL: HTTP_REQUEST] http request (_ssl.c:590)
[W 160817 15:32:44 iostream:1276] SSL Error on 12 ('192.168.1.112', 45263): [SSL: HTTP_REQUEST] http request (_ssl.c:590)
[W 160817 15:32:51 iostream:1276] SSL Error on 12 ('192.168.1.112', 45265): [SSL: HTTP_REQUEST] http request (_ssl.c:590)
[W 160817 15:32:51 iostream:1276] SSL Error on 13 ('192.168.1.112', 45266): [SSL: HTTP_REQUEST] http request (_ssl.c:590)
[W 160817 15:32:51 iostream:1276] SSL Error on 12 ('192.168.1.112', 45267): [SSL: HTTP_REQUEST] http request (_ssl.c:590)

UPDATE:  I solved the problem by typing in https://ipaddress:4200 and shellinabox worked.  Same with gate one.  I guess it's required to have the https:// part in the URL.  Not sure why if someone wants to explain.

Last edited by goodwinmcd (2016-08-18 13:03:15)

Awebb

Member

Registered: 2010-05-06

Posts: 6,282

Re: Shellinabox

UPDATE:  I solved the problem by typing in https://ipaddress:4200 and shellinabox worked.  Same with gate one.  I guess it's required to have the https:// part in the URL.  Not sure why if someone wants to explain.

The behavior is what I would expect from anything, that is not a run in the mill httpd. Your browser defaults to http. Both shellinabox and gateone do not have a reason to react to http:// by default. You need to tell them to offer https, whenever http is requested. The fact, that the protocol part in URL's is often omitted these days, is that most services only offer either http or https and there is little reason to default to anything else. The reason, why some servers are configured to default to https (or why some servers even have the feature), is pure practicality: When you serve a website with an SSL certificate, you want people to use that, so http is being redirected to https, and since most people cannot be bothered to type protocol parts these days anymore, you need your http defaulting browsers to understand, that they are supposed to use https. A tool like gateone does not have to deal with users incapable of specifying their protocol by default. A server responding with a different protocol than the requested one, does not exhibit expected behavior.

This was just a short excerpt of a lengthy lecture I once received from a network administrator, upon possessing the audacity to ask a similar question. Possible consequences seem to be the sudden opening of Hell rifts and the sudden devouring of ALL firstborn.

In case of Gateone, I actually remember the feature request: https://github.com/liftoff/GateOne/issues/68. It "now" has an https_redirect option.