i install shellinabox on centos5, it runs well and i can connect from foreign IP, but when i config it with nginx, it shows "File not found"

[GoogleCodeExporter]

What steps will reproduce the problem?
1.make&make install shellinabox on centsos5.7, it runs well and i can connect 
port 4200

2.insert the setting to nginx.conf
location /shellinabox
{proxy_pass http://127.0.0.1:4200;}
i didn't turn on ssl setting with nginx and shellinabox.

3.when i visit http://www.***.com/shellinabox, it shows me a errot, "File not 
found", just like if i visit http://www.***.com:4200/index.html

What is the expected output? What do you see instead?

i think it should shows shellinabox login page, but just "File not found", just 
like if i visit http://www.***.com:4200/index.html

What version of the product are you using? On what operating system?
1.nginx/1.0.10
2.newest shellinabox

Please provide any additional information below.
i think when i visit www.***.com/shellinabox, the nginx engine searchs for 
index.html, index.php, etc, but shellinabox didn't have such a file, so it 
returns a file not found

is there anybody configure shellinabox with nginx well? it's a wonderful tool 
to visit my server with web ssh, but i can't set it up.

thanks in advance.

Original issue reported on code.google.com by digginch...@gmail.com on 1 Jan 2012 at 12:27

• Merged into: #167

[GoogleCodeExporter]

You probably have the same problem I had, I wrote a patch that you can find 
there:
https://code.google.com/p/shellinabox/issues/detail?id=167

Please note that you have to end the url with a /.

If you really want to make http://www.***.com/shellinabox possible instead of 
http://www.***.com/shellinabox/, then use the patch that I am attaching to this 
post.
It should work just fine, but unlike the one at issue 167 it hasn't been tested 
extensively and might break things.

Original comment by decoy113...@gmail.com on 6 Mar 2012 at 10:05

Attachments:

• patch4.c

[GoogleCodeExporter]

Original comment by beewoo...@gmail.com on 31 Mar 2012 at 11:22

• Changed state: Duplicate

[GoogleCodeExporter]

Mind that an easy workaround is to add the slash to the proxy_pass directive, 
e.g.:
proxy_pass http://127.0.0.1:4200/;

Original comment by alexande...@esaturnus.com on 2 Jul 2013 at 8:26