Jump to content
Search In
  • More options...
Find results that contain...
Find results in...
Fluffee

[Tutorial] Run Most Application Through a Proxy (Windows/Linux) Most Browsers and OldSchool Clients!

Recommended Posts

How to Run Most Applications Through a Proxy on both Windows and Linux

Windows Instructions

Note: Chrome and Firefox portable do not work with WideCap.

1. Download WideCap from here (http://widecap.ru/en/download/)
2. Run through the installer, and launch WideCap, you should see this screen.
1464452cee.png
3.Go ahead and click on Settings (First option under the Widecap section on the left hand side). Then uncheck the box that says Run with system startup.
59fdbb3822.png
4. Now go ahead and click on New proxy (First option under the proxies section on the left hand side).
5.You should see this screen, in the top field enter the IP address and port (IP:Port format). Confirm that the protocol is set to SOCKS v5 (which is the default), and tick the box for Authentication if necessary. If using an authenticated proxy, enter your username in the login field, and obviously your password in the password field. Then hit the Create New button, next to Chain, and type in a name for your Proxy, then Hit OK
61b2026fb6.png
6. Now that you're back to the main screen, click on the Proxy List section (Second option under the proxies section on the left hand side). Right click on your newly added proxy, and click check selected, to make sure you entered all the information correctly. If the status field rolls over to OK, you're good to go, and can move on to the next step
d30a0e1f41.png
7. Find WideCap in your System tray, right click, and uncheck the box that says Enable Widecap.
11610f949c.png
8. Click on View Programs (Second option under the Programs section on the left hand side). Then drag and drop the icon for the application you want to proxify (run behind a proxy) into WideCap. WideCap supports the proxifying of both .exe and .jar files!
73c595fd6c.gif
9. Right Click on your newly added program, and click on Modify Application, you should see a similar screen depending on what you added. Then click on Create New... (to create a new rule)
581276e221.png
10. In the Chain tab, select the Proxy Chain you created earlier, then under the Main tab, give your new rule a name and hit OK. Then Hit OK again on the modify Application screen.
2138baa178.gif
11. Hit Apply and OK in the main window of WideCap, and then find it in your System Tray again, but this time click the box to Enable Widecap
12.Open your Proxified application, and check to see if the proxy worked! If your IP is changed, congrats, you've got WideCap working!

Linux Instructions (Based off of a Debian Installation)

1. Open a new terminal and run this command

sudo apt-get update && sudo apt-get install -y proxychains

2. Now that proxychains is installed, we're going to go ahead and create a user specific configuration file. To do this, we'll make a directory, then copy the standard proxychains configuration file to it and change the ownership of the configuration file to your user. Run the command below as your user.

mkdir ~/.proxychains/ && cp /etc/proxychains.conf ~/.proxychains/proxychains.conf && sudo chown ${USER:=$(/usr/bin/id -run)} $HOME/.proxychains/proxychains.conf && sudo chgrp ${USER:=$(/usr/bin/id -run)} $HOME/.proxychains/proxychains.confroxychains.conf

3. Once the command is finished, open the proxychains config file in your favorite Linux text editor, for ease of use, I'm going to use nano. To install nano run this command

sudo apt-get install -y nano

To edit the proxychains config file, with nano, run this command

nano ~/.proxychains/proxychains.conf

4. Now, what you'll want to do is scroll all the way down to the bottom, and you should see something like this
4837941af6.png

That last line that says

socks4    127.0.0.1    9050

That's the line we'll be editing. Firstly, we'll go ahead and erase everything on that line, don't worry we'll put it back. The format for the configuration file is

Proxy Type(lowercase) (tab) IP address (tab) Port (tab) Username (tab) Password

Therefore if your proxy was a Socks5 proxy, with an IP of 192.168.1.1, a port of 1080, a username of Fluffee and a password of TRiBot, your final line would look like this:

socks5    192.168.1.1    1080    Fluffee    TRiBot

So, go ahead and modify your last line to fit your own proxy and then hit Control+X to exit, and then hit Y to save (instructions are based off of using nano to edit the file).

5. Proxychains is now setup, but how do you use it? Go ahead and VNC into your Server and open a terminal, or open a Terminal inside your Desktop Environment (if using Linux installed on a PC). From there run the command proxychains followed by the application you would like to run, or the path to the application. For example, try running, if you have Firefox installed:

proxychains firefox

Then navigate to an IP checking website, and see if your proxy worked! :)

That concludes the tutorial on how to use a proxy with Oldschool or any browser, on both Linux and Windows. If you have any questions feel free to post in the comments!

Edited by Fluffee
  • Like 6

Share this post


Link to post
Share on other sites
On 2016-03-17 at 7:30 AM, moiz.frost said:

chrome doesnt work

 

On 2016-03-17 at 7:33 AM, moiz.frost said:

Neither does firefox portable

You're right, Chrome is apparently incompatible with WideCap. I haven't tested Firefox portable, but I do know that the regular Firefox works fine with WideCap!

I have updated the original post to reflect this, thanks :)

  • Like 1

Share this post


Link to post
Share on other sites
On 3/17/2016 at 1:19 AM, Aibunker said:

Doesn't this basically just mean people can do this instead of purchasing Vip-E if they just want to use the proxy? :P

Yea, but VIP-E seems tailored towards goldfarmers and if you are running decent size goldfarm, cost of VIP-E is not that much and you are supporting development of TRiBot.

Share this post


Link to post
Share on other sites
Just now, bzq said:

I do not recommend instal widecap, hacked after

The correlation between WideCap and you getting hacked is a coincidence and nothing more, you should however check through your PC as you've obviously picked up something nasty on the net, which you're going to need to deal with.

Share this post


Link to post
Share on other sites

Love the guide, very detailed. I have one problem tho, when I right click the proxy and click "check selected" instead of status field rolling to "ok" It says "connection timed out". I assume there is something wrong with proxy? Please help this is the second proxy I have bought on Virmach both of them are timed out, whenever I try to login Tribot using them proxies I get an error message saying could not connect to specified proxy. Really appreciate some help, thanks

Share this post


Link to post
Share on other sites
36 minutes ago, tadzeus said:

Love the guide, very detailed. I have one problem tho, when I right click the proxy and click "check selected" instead of status field rolling to "ok" It says "connection timed out". I assume there is something wrong with proxy? Please help this is the second proxy I have bought on Virmach both of them are timed out, whenever I try to login Tribot using them proxies I get an error message saying could not connect to specified proxy. Really appreciate some help, thanks

That's probably an issue on VirMach's end, try contacting their customer support!

  • Like 1

Share this post


Link to post
Share on other sites
Just now, ibot4funn said:

Will this guide load the RS client with the same ip as the proxy? I've tried manually entering in the proxy through firefox but it doesnt seem to load the client with the proxy ip. @iFluffee

As far as I know it should, yes

You could always proxify a .jar, like OSBuddy, instead of FIrefox

Share this post


Link to post
Share on other sites

Do you have to actually buy and use a proxy from widecap like it states before downloading? this is what it says when clicking on the link in the tutorial " Download full version you can from here. (4.16 MB) | Don't forget to buy the socks from 5socks.net Servicebefore download the program

is this needed or can i just download it? Or can i use it and download it by using a brwoser running one of my proxies? 

Share this post


Link to post
Share on other sites
Just now, runescapeprodigy said:

Do you have to actually buy and use a proxy from widecap like it states before downloading? this is what it says when clicking on the link in the tutorial " Download full version you can from here. (4.16 MB) | Don't forget to buy the socks from 5socks.net Servicebefore download the program

is this needed or can i just download it? Or can i use it and download it by using a brwoser running one of my proxies? 

You can purchase proxies from any site, they just want you to purchase from them! So no, you don't need to purchase proxies from their site!

Share this post


Link to post
Share on other sites
Just now, runescapeprodigy said:

Alright thanks you so much Fluffee and for oyur other guides! So I can just download it directly from my home Ip and then add the proxies i use just like in your guide right? Just to be 100% clear that i can download it just fine like your guide says. 

Yeah, just follow the guide and you'll be okay :)

Share this post


Link to post
Share on other sites
1 hour ago, runescapeprodigy said:

One last thing, do you know how to check what ipaddress your osbuddy is running on? It doesnt´seem to tell you anywhere now ive checked and set everything up. 

I don't think OSBuddy has an option to show this.
But if you are using a 3rd party program like WideCap to proxy your OSBuddy, the program should let you know.

Share this post


Link to post
Share on other sites

I seem to have an issue when trying to move the 32 bit jar osbuddy into it. 64bit works fine just throwing in the shortcut, but it refuses to take the jar whether i put it in the actual osbuydd folder, its just a shortcut or directly from downloads. What did any of you do to fix that? Am i missing some tricks? 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Similar Content

    • By Proxy-Seller
      Hello and welcome to ProxySeller!   Our service would like to offer you personal, static proxy-servers with price range starting from $0.6 depending on what location you are looking for.   Currently we have USA, France, Germany, Russia, Ukraine Kazakhstan, Netherlands, England and Canada available, new countries coming soon as well. We are selling elite, private USA IPv4 proxies just for $1.5 per month ! We do not provide any speed or trafic restrictions to our customers. Wide range of nets and subnets. 24/7 technical support, if you will face any kind of issues during proxy use, they will be solved with the big pleasure by our specialists, You don`t have to worry about proxy "sudden death" - we guarantee reliable technical workability of proxy during whole paid period. Also we are checking our proxy for workability with demanded resource before sending them to you, so all you have to do is just insert IP`s in required browser or software - and you`re ready to work! Our proxy works perfectly for craigslist, supreme and similar sneakers resources, dating sites like pof and match.com as well as for SEO-purposes!   Affiliate program   The reliable and stable source of your income! If you have cooperated with us, you are guaranteed to receive 30% on the first payment and for the rest ones you will receive 10%. Share with your friends, acquaintances, partners with your affiliate link, in messangers or on your e-mail. You can share links in comments below the videos, articles, etc. Affiliate programm advantages: Referrals for their entire duration. No minimum amount for withdrawal. You can choose the payment system for withdrawal of accumulated funds: WebMoney, QIWI Wallet, Yandex Money. Consultations on partnerships 24/7/365   Discount for buying 10 package proxies and more - 3% Discount for buying 25 package proxies and more - 5% Discount for buying 50 package proxies and more - 10% Discount for buying 75 package proxies and more - 10% Discount for buying 100 package proxies and more - 15% Discount for buying 250 package proxies and more - 20% Discount for buying 500 package proxies and more - 35% Discount for buying 750 package proxies and more - 35% Discount for buying 1000 package proxies and more - 40% Discount for purchasing proxy for 2 months - 3% Discount for purchasing proxy for 3 months - 5% Discount for purchasing proxy for 6 months - 7% Discount for purchasing proxy for 9 months - 10% Discount for purchasing proxy for 12 months - 12%   We have IPv6 of such locations: USA, Russia, Ukraine, Germany, France, Netherlands and Canada are available for the purchase. For purchasing small plan tariff (5-49 addresses) - price is 0.15$ per proxy for month For purchasing medium plan tariff (50-499 addresses) - price is 0.11$ per proxy for month For purchasing large plan tariff (from 500 and above addresses) - price is 0.08$ per proxy for month PROXYSELLER Our contacts: E-mail: [email protected] Skype: proxy-seller.com ICQ: 310-040  
    • By twizzletwanger
      Hi!
      I have multiple proxies that I like to jump to and from. Can I do this without having to close the app and re-open to select a new proxy?
      Thanks!
    • By IceKontroI
      Overview
      A while back I had to create an implementation of a Server and Client communications system for a personal script of mine. My implementation was shit. Here's a much better one. It's still a bit unrefined so if you have an improvement, post it and I'll consider it for revision. The implementation for a lot of the class events is abstract, meaning the user determines what he wants to do when those events fire. Both Server and Client feature a heartbeat system, where after a certain time interval, the Client will send some info to the Server to let it know it's still alive. Likewise every time interval the Server does the same, but for each Client Connection it has saved. Servers and Clients both always have threads open which wait for Objects to be read. When an Object is read, an event will be fired as mentioned below. If the Object read is a Request (covered later on), then it will be displayed through a separate designated event. Implementations of the following events are not mandatory. If you don't want to handle certain events, simply create a constructor for the Server/Client, but leave the blocks for the unused event blank.
      Server events
      public abstract void onConnectionGain(Connection connection); Fired whenever a Client successfully connects to the Server, providing you the Connection that was just established. public abstract void onConnectionLoss(Connection connection, Exception e); Fired whenever a Connection is dropped, except when the Server closes a Connection manually when its shutdown() method is called. The Exception describes the circumstances that lead to the Connection being dropped. public abstract void onWrite(Serializable object); Fired whenever an Object is written to every Connection in the Server's list of current Connections. public abstract void onWrite(Serializable object, Connection connection); Same as above, but fires once for each Connection in the Server's Connection list at the time of writing the Object. public abstract void onRead(Object object, Connection connection); Fires whenever an Object is received on the Server's end from a Client Connection. Does not fire when a Request is received, the following event handles those cases. public abstract void onRequest(Request request, Connection connection); Fires whenever a Request is received on the Server's end from a Client. This class should handle implementation of how exactly you want to handle Requests. Requests will be covered in detail later on in the post. public abstract void onShutdown(); Fires at the end of Server#shutdown(). Client events
      public abstract void onConnectionGain(); Fired when the Client successfully established a Connection to the Server. public abstract void onConnectionLoss(Exception e); Fired when the Client's Connection to the Server drops. The Exception describes the circumstances that lead to the Connection being dropped. public abstract void onRead(Object object); Fires when the Client receives an Object from the Server. This again does not fire when a Request is received, that is handled by the event below. public abstract void onRequest(Request request); Fires when a Request is received on the Client's end, from the Server. public abstract void onShutdown(); Fires at the end of Client#shutdown(). Functionality
      The primary function of a Server/Client implementation like this is to facilitate communication between the Client and Server. Communication can happen across multiple scripts and even multiple computers. They must all be on the same network, however. Reading more than one Object at a time is unsupported (would corrupt underlying streams), and the same for writing. You can, however, read and write at the same time. To set this up, the user must specify which port the Server will be set up on, and then create Clients that attempt to connect to that port. You can do this through the constructors like so:
      Note  the implementations of each event in the example above do not need to contain any actual code, they just need to have their headers. Clients will automatically attempt to re-connect to the Server with their designated port number. If the Server connection is lost while a Client is still online, it will fire a onConnectionLoss(...) event and wait 1 second before reconnecting. If a Client connection drops while the Server is still online, the Server will simply fire onConnectionLoss(...) and do nothing special.
      When a Connection is dropped, either Server or Client, you won't know about it until you try to read/write to it. This is why both Server and Client implement a "heartbeat" system. Every time interval (0.5 seconds) the Server sends a null Object to each Client, and each Client does the same for its Server. This simply ensures a minimum read/write frequency between the Server and Client so that dropped connections can be handled properly. On read/write from a disconnected Connection, an error will be thrown, which will properly remove the Connection from the Server's list and fire onConnectionLoss(...).
      Writing
      Communication between Server and Client is two-way, meaning the Server can send Objects and Requests to any of its Connections and the Client can do the same to its designated Server. A Server can have as many Connections as your heap space allows, however a Client can only have 1 Server Connection. Reads happen automatically via their own threads, however writes must be handled directly by the user. Anything you want to write must be Serializable, otherwise you'll get an Exception. Here's how the write methods work:
      Server
      public void write(Serializable object) Simply writes the given Serializable to every Connection in the Server's current Connection list. Fires onWrite(Serializable object); public void write(Serializable object, Connection connection) Writes the Serializable to only the specified Connection. Fires onWrite(Serializable object, Connection connection); Client
      public void write(Serializable object) Writes the given object Fires onWrite(Serializable object); When writing Requests, if the Request is unfulfilled (see section below), it will appear in the recipient's onRequest(...) event.
      Requests
      Finally I'll get to Requests, which is one of the main things I built this system to handle. A Request is a specialized Object, sent to a recipient, with the expectation for it to be returned, but with some modification. A Client may want to send a Request containing a Point with coordinates (-1, -1), expecting it to be returned with different coordinates. Here's an example of what that might look like:
      Simply extend Request<T> where T is the type of Object you want to be able to modify and implement Serializable so that the Request can actually be sent. When you initialize the Request<Point>, it will contain a Point (or otherwise specified type) variable called "target" which will be null until the Request is fulfilled. To fulfill the Request, simply call Request#fulfill(Object ... args) with the proper argument parameters (in this case 2 ints). The Request will automatically process the parameters in the way specified by your abstract implementation of Request#execute(Object ... args), and update the "target" from null to whatever the result actually is. If Request#execute(...) throws an Exception at any point, the Request will simply be processed as unfulfilled and ignored, even if it is written back to the sender. Here's what Request fulfillment looks like:
      To send Requests, simply call the Client or Server's fulfill(...) method. It will write the specified Request to the target(s), wait for it to be returned as fulfilled, and then return it. If it doesn't receive the Request within a designated time frame, it'll throw a RequestTimeoutException. Requests use System.nanoTime() as an identifier to ensure the originally sent Request is returned at the end of the method call. This is a failsafe to ensure you don't accidentally return a different Request to the one that was originally sent out.
      Classes
      That's it. Here are the classes:
       
    • By Dakers011
      Over 10,000 RuneScapers Have Used MMOearn Since 2016
       

       
      Our Goal Is To Save You Money!
      Buy RuneScape Gold From MMOearn Now!
      No One Can Beat Our Price, Free!
       
       
    • By RSGM Sales
      *WE HAVE NO HIDDEN CHECKOUT FEES WHEN U PURCHASE GOLD!* MANY OTHER SITES WILL CHARGE YOU UP TO 5% EXTRA BUT WILL ONLY DISPLAY THIS WHEN YOU ARE PAYING. WITH RUNESCAPEGOLDMARKT YOU PAY THE PRICE YOU SEE. NOT A CENT MORE!   Moderator Partnered with Montreal
    • By ProduceSync
      I just bought VIP and a script. I can't get Proxies to work or Looking glass to work. If I can't get anything to work I'll be getting a refund.
    • By OliverandFelix
      When using looking glass do I still connect to Runescape using the proxy selected through Tribot, or will the mirrored client run through my main ip adress as osbuddy has no option to use a proxy?
    • By TRiLeZ
      This release will:
      Fix Settings UI placement bug Fix game object location bug Fix small layout bug making the client shift up and down Fix client crashing bug where loading the client with a small display area will cause the client to crash Fix annoying Linux bug relating to painting events and peers Fix settings saving bug where settings are saved to disk more often than they should Fix RSInterface#isBeingDrawn bug affecting a limited amount of people Drop Java 1.7 bytecode version for 1.8 Important: Since the downloadable RS client uses Java 7, it will no longer be compatible with Looking Glass. To make up for this, we will add support for using other clients such as RuneLite (at a later date). This change was necessary to allow us to use Java 8 syntax. It also paves the way for Java 9/10/11 support. Edit: Release 9.312_1 will:
      Fix LG GZIP error Fix Client Starter for Linux 🙌
  • Our picks

    • This release will:

      Add new internal framework for capturing exceptions


      Fix issue with not selecting the last column in world hopper (Thanks @Todd)


      Add a message about pin usage in Banking#openBank (Thanks @Todd)


      Disable the firewall by default (Thanks @Todd)


      Fix handling of the welcome screen after login (Thanks @Encoded)


      Fix wrong amount bank withdrawal (Thanks @Encoded)


      Fix Screen#isInViewport


      Fix Game#isInViewport (Thanks @Encoded)


      Call onBreakEnd for ListenerManager Breaking Listeners (Thanks @Encoded)


      Fix Prayer#getPrayerPoints NumberFormatException (Thanks @JoeDezzy1)



      Note: If you are using LG, please restart both the RS client and TRiBot.
        • Thanks
        • Like
      • 19 replies
    • This release will:

      Fix LG for both OSBuddy and RuneLite


      Fix issue where the resizable client isn't able to be made smaller (Thanks @JoeDezzy1)


      Fix detection of the logout game tab when resizable mode and side panels are enabled (Thanks @JoeDezzy1)


      Add initial support for Sentry to allow us to identify and easily debug exceptions happening with all TRiBot users


      Add methods to determine if the bank is actually loaded, and not just the overarching interface (Thanks @wastedbro)



      Upcoming updates:

      Improved CLI support


      Full Sentry support


      Much more
        • Like
      • 64 replies
    • This release will:

      Fix NPE in Camera API (Thanks @wastedbro)


      Update deposit box interface ids (Thanks @Encoded)


      Add various bank methods (Thanks @wastedbro)


      Banking#getWithdrawXQuantity


      Banking#getDefaultWithdrawQuantity


      Banking#arePlaceholdersOn




      Fix resizeable minimap bug (Thanks @wastedbro)


      Remove Java 8 requirement


      Please note: TRiBot is not yet fully compatible with Java 10+




      Fix the break handler issues by ensuring the break handler thread never gets paused


      Fix broken settings hooks



      Upcoming updates:

      Improved CLI support


      Much more



      Note: If you are using LG, please restart both the RS client and TRiBot
        • Like
      • 68 replies
    • This release will:

      Add support for using custom F key bindings to switch between game tabs (Thanks @erickho123)


      Fix tab opening for "Skills" and "Kourend Tasks" (Thanks @erickho123)



      Note: If you are using LG, please restart both the RS client and TRiBot
        • Like
      • 34 replies
    • This release will:

      Fix an issue where breaks would stop firing


      Fix Combat#getWildernessLevel, use dynamic search for text and cache ID for later calls


      Fix an NPE in the Combat API


      Fix Mouse#leaveGame bug where the mouse wouldn't actually leave the game screen
        • Like
      • 21 replies
  • Recently Browsing   0 members

    No registered users viewing this page.

×