ProxyMan icon indicating copy to clipboard operation
ProxyMan copied to clipboard

install not working on Ubuntu 18.10 however main.sh works

Open tejasvi opened this issue 5 years ago • 20 comments

user@love:~/ProxyMan-master$ sudo ./install
Failed to install :(
You can still use it > ./main.sh set

Worked fine in Fedora though.

tejasvi avatar Mar 05 '19 13:03 tejasvi

Well, install doesn't require sudo. It just copies the files to your $HOME/.local/bin so that they are available in $PATH.

Installing using sudo makes it available to the path of root, not user.

If the problem still persists, then the issue might be this one. Let me know if you are able to fix this.

himanshub16 avatar Mar 07 '19 11:03 himanshub16

It doesn't works either way. Besides I'm using fresh vanilla Ubuntu 18.10 install, so its not an issue.

tejasvi avatar Mar 07 '19 12:03 tejasvi

I second this. Fresh Ubuntu 18.04 failed to install.

ilhamfp avatar Mar 13 '19 06:03 ilhamfp

I've the same issue on Linux Mint 19.1 Tessa 64-bit

ehayik avatar May 15 '19 14:05 ehayik

Finally I could install it. I moved the ProxyMan folder to /opt and executed the install file

ehayik avatar May 15 '19 18:05 ehayik

I would need to reproduce this on some Ubuntu machine in order to understand the error. If you could help me get the result of these snippets, it would be helpful:

./install
which proxyman
ls ~/.local/bin
echo $PATH

In a new shell,

which proxyman
ls ~/.local/bin
echo $PATH

himanshub16 avatar May 21 '19 16:05 himanshub16

no working here too. not proxied docker also

bitdaric avatar May 22 '19 12:05 bitdaric

@bitdaric What is the issue regarding docker?

himanshub16 avatar May 23 '19 05:05 himanshub16

I am having the same issue in Ubuntu 19.04.

thomas@Someones-PC:~/Downloads$ cd ProxyMan-3.1.1/ thomas@Someones-PC:~/Downloads/ProxyMan-3.1.1$ ./install Failed to install :( You can still use it > ./main.sh set thomas@Someones-PC:~/Downloads/ProxyMan-3.1.1$ which proxyman thomas@Someones-PC:~/Downloads/ProxyMan-3.1.1$ ls ~/.local/bin proxyman thomas@Someones-PC:~/Downloads/ProxyMan-3.1.1$ echo $PATH /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/home/thomas/.dotnet/tools

Entering the same commands in a new shell gives the same results. It functions fine if run using ./main.sh but that is obviously not ideal in the long run.

tamathews avatar May 25 '19 11:05 tamathews

Seems like I either need to pollute /bin, /usr/bin/, /usr/local/bin. There will certainly be distros creating this issue.

himanshub16 avatar May 27 '19 18:05 himanshub16

Update: I tried the current version (177 commit) again on Ubuntu 18.04, it works!

ilhamfp avatar Jun 15 '19 10:06 ilhamfp

same issue on ubuntu 19.04 :(

EdoardoVarani avatar Jul 03 '19 09:07 EdoardoVarani

Can confirm. Get the same error for Ubuntu 19.

vsvipul avatar Jul 29 '19 14:07 vsvipul

😢

himanshub16 avatar Jul 29 '19 18:07 himanshub16

I also faced the same problem when i tried to install it in my Debian 9.x vm. The issue is "proxyman" was copied to $HOME/.local/bin but this path was not in my PATH environment location. Mypath: /usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games

Solution: First set the PATH variable in the ~/.bashrc file. Open the file with your text editor and add the following line at the end of it: export PATH="$PATH:$HOME/.local/bin" Then run: $ source ~/.bashrc

Next run the installation: ./install

Now it should complete successfully

brsanjay avatar Sep 12 '19 17:09 brsanjay

Thanks @brsanjay . That worked for a fresh Ubuntu 19.10. I had it working in 19.04 but I had to do the same thing there. It looks to me like the install script could/should add an option to add the export PATH line automatically to the .bashrc if the "which proxyman" fails and if the .bashrc file exists. Not sure if this is the best way to fix it but it would work.

nathanbrizzee avatar Nov 06 '19 00:11 nathanbrizzee

I had a similar issue installing this on WSL/Ubuntu 18.04 (LTS). Proxyman installed nicely, but which proxyman did not find the ~/.local/bin folder that was created during the install. If the folder does not exist, Ubuntu doesn't add it to the PATH. When the install script then creates the folder, the current session doesn't have the folder in the PATH.

Solution: source ~/.profile then found the ~/.local/bin folder and correctly added it to PATH; which proxyman then worked perfectly. Note that the install worked in the first place, but the which check at the end of the install script returned nothing.

Perhaps source ~/.profile should be added to the install script before testing if the binary works?

safferli avatar Nov 29 '19 20:11 safferli

I can verify that this issue comes from not having ~/.local/bin in $PATH. I encountered this issue on several machines with Ubuntu and ArchLinux.

deg0nz avatar Jan 27 '20 22:01 deg0nz

in fedora 32 install works ubuntu 20.04 install not working again, but main.sh - works ubuntu software center not proxying using latest release as of now - ProxyMan version 3.1.2

ghost avatar May 26 '20 13:05 ghost

With Ubuntu 20.04 you need to logout and login again for the $HOME/.local/bin path to get added to $PATH. It will just be added if this path is present (see $HOME/.profile). A source $HOME/.profile in the installer script before the which proxyman &> /dev/null would fix this. I am not sure for other distros...

truehumandesign avatar Jun 04 '20 11:06 truehumandesign