Fixing QOProxy after patches...

Ok, well I realy havnt contirubted much to this site i mainly use it for getting hack.s scamms, and exploits so i thought i would give a shot at helping a few noobs with QOProxy


Ok as you all know sometimes patches change you server's ip adresses.

And with QOProxy aimbot when you first get it it fixes to the servers ip you use it for.

If there is a patch and you arent able to log onto your proxy server go to the new server folder from the patch and check to see if the ip's have changed for your servers.....

If they have changed al you have to do is coppy what there new ip is and go to ur QOProxy file and go to its QOProxy configuration settings...


Find where it sez remoteloginip= yada yada

and delete the old ip and put ur new ip in and save settings...

Go back to ur new server file change wich server u want fro proxy 127.0.0.1 run cmd like usual and log into proxy server again like usual

k TY. bye "just trying to help"

Uhh, useless since QoProxy wont work anymore, at least for mostly everyone, The new QoProxy is only for Staff and wont work-dats wut i heard

Wow, idiot. I have a perfectly working one.......

U just change the qoproxy's remoteloginip to the new ip of the server and walla it works again simple -.- doesn't take a genious

127.0.0.1 is your own computer network if you didnt know that it makes it look back on the client itself <.<

lol i have a proxy with alot more 'options' than that

Quote:

Originally posted by evulhotdog@Nov 23 2006, 08:51 lol i have a proxy with alot more 'options' than that

same to bad its not for the public. Don't ya love private hackers :D

Quote:

Originally posted by Unknownwho18+Nov 24 2006, 02:03--></span><table border='0' align='center' width='95%' cellpadding='3' cellspacing='1'><tr><td>QUOTE (Unknownwho18 @ Nov 24 2006, 02:03)</td></tr><tr><td id='QUOTE'> <!--QuoteBegin--evulhotdog@Nov 23 2006, 08:51 lol i have a proxy with alot more 'options' than that

same to bad its not for the public. Don't ya love private hackers :D [/b][/quote]
its also a private site =P

Quote:

Originally posted by iliveoncaffiene@Nov 23 2006, 03:59 Wow, idiot. I have a perfectly working one.......

Your a [PM] tho CaFf >.>

thx for the help.
i could have found out my self .... one day ...
hbuy this is much faster.

i dont even know how to get it actually work lol.. i dont need it maybe when my tro is higher if it still works..

lolzzzz mine still working... :D

dam mine stopped working, and i dont noe how to fix it?

Quote:

Originally posted by harro22@Nov 23 2006, 02:34 Ok, well I realy havnt contirubted much to this site i mainly use it for getting hack.s scamms, and exploits so i thought i would give a shot at helping a few noobs with QOProxy Ok as you all know sometimes patches change you server's ip adresses. And with QOProxy aimbot when you first get it it fixes to the servers ip you use it for. If there is a patch and you arent able to log onto your proxy server go to the new server folder from the patch and check to see if the ip's have changed for your servers..... If they have changed al you have to do is coppy what there new ip is and go to ur QOProxy file and go to its QOProxy configuration settings... Find where it sez remoteloginip= yada yada and delete the old ip and put ur new ip in and save settings... Go back to ur new server file change wich server u want fro proxy 127.0.0.1 run cmd like usual and log into proxy server again like usual k TY. bye "just trying to help"

Change This (QOproxy/qoproxy.ini)

localloginport=9958
localmapport=5816
remoteloginport=9958
remoteloginip=69.41.179.98
remoteloginip=216.93.174.65 <----- change this to (below)
proxyip=127.0.0.1
consoleout=yes
logfile=coproxy.log
filter=99999


Conquer2.0/server.dat

Server4=Mars
Ip4=69.59.142.13 <--to w/e your servers ip is (found here) *NOTE* u must change this IP to 127.0.0.1 before running QOProxy
ServerName4=Mars
HintWord4=
Pic4=servericon17

so for mars server here the ini should look like this:

localloginport=9958
localmapport=5816
remoteloginport=9958
remoteloginip=69.41.179.98
remoteloginip=69.59.142.13 <---(note the change)
proxyip=127.0.0.1
consoleout=yes
logfile=coproxy.log
filter=99999

and the server.dat in your CO folder should look like this:

Server4=Mars
Ip4=127.0.0.1 <---------(note the change from 69.59.142.13)
ServerName4=Mars
HintWord4=
Pic4=servericon17

#fixed