legacyproxy icon indicating copy to clipboard operation
legacyproxy copied to clipboard

Cannot start proxy, Cannot locate Gemfile

Open luckenbachjustin opened this issue 4 years ago • 1 comments

Hello,

I recently downloaded your proxy for old web browsers with hope to use it on my raspberry pi 3. I followed the instructions that were in the read me but I keep getting these two errors:

When trying to start the proxy: ruby: No such file or directory -- ./proxy.rb (LoadError)

and

trying "bundle install" Could not locate Gemfile

Is there something I am missing or doing wrong? I have the latest Raspbian buster OS.

Thanks, Justin

luckenbachjustin avatar Apr 11 '20 21:04 luckenbachjustin

As I understand it,

  1. the 'gemfile' contains a list of dependencies
  2. bundle install checks to see if they (and their dependencies) are installed, and
    • automatically fetchs/installs them if they are not.

If bundle install fails, then proxy.rb will likely never work.


First, make sure both Gemfile and proxy.rb are downloaded and in the current directory (wherever you'd like) , by e.g.:

curl -O "https://raw.githubusercontent.com/zenwheel/legacyproxy/master/Gemfile"  # Download the Ruby 'Gemfile' listing dependancies for `proxy.rb`
curl -O "https://raw.githubusercontent.com/zenwheel/legacyproxy/master/proxy.rb" # Download `proxy.rb` itself 

Second, follow the instructions from the README.md file, e.g. for Raspbian:

sudo apt-get install ruby2.3 ruby2.3-dev build-essential patch zlib1g-dev liblzma-dev libmagickwand-dev
sudo gem install bundler
bundle install

Finally, run proxy.rb:

ruby ./proxy.rb

Warning for the unwary

This (proxy.rb) seems to work with very old browsers, but not necessary with moderately old browsers (e.g. "Classilla").

(why? ...) It seems mostly to have to do with newer browsers using the HTTP verb `CONNECT`, which tries to tunnel through proxies to establish secure connections directly with the intended server (to hinder MITM attacks).

If the browser you're testing has issues with this proxy, the first step in isolating the problem should probably be to try the oldest brower you can find for that particular client.

jgrisham avatar Feb 17 '22 03:02 jgrisham