hi,
I have a problem running the proxy server. with just 1 instance idling (pserver running, but i am not doing anything with the proxy), it will take up to 700MB of RAM in just a few hours? is that some kind of memory leak?
i couldnt find any log files except for a logs folder parallel to the htdocs folder, which is obviously not specifically for each instance. i only duplicated the anon_proxy_server folder under htdocs. is that not the right way to do it? there is only a small error file in the logs folder. since all executables are name pserver, i guess i cant tell which instance it is..
right now, 1 instance of pserver will consume some 800MB of RAM (while the others not doing so) in a few hours and the proxies will stop working.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The logs can be viewed on the left side of the interface under "usage log", "error log"
Take a look at the difference in the configuration of this one that's not doing well. Maybe copy the config file from one of the ones that are working into cache/config.php or restart and copy the cache/config.php from the original archive you had downloaded. You can
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
do you know why i am getting all these socks connections (without needing logins) and failed http? these are not my IPs, and I am not doing anything except or starting pserver.exe. they start almost as soon as i turn on pserver. http://white-light.net/apslog1.jpg
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
People go around and scan common ports, that's how they probably found you. Then they publish it somewhere and all sorts of random people know about it.
Change the proxy port to a strange number and add the user/pass security to it, maybe only allow certain IPs to visit it too if you only access it from certain places.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
finally whitelisting my ip allows me to have pserver running for 5 hours.
now i guess the only problem i have is sometimes i cannot start pserver/forcebindip. normally when i start it, a window (comand prompt) popup. in this case, it flashes and disappears.
i still dont understand the start/restart/stop in the web interface (start.php, stop.php, etc.) which seems to have something to do with me not being able to start pserver/forcebindip. 'stop' gives me 'couldnt stop' and 'restart' gives me another instance of pserver which is obviously not what i want.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
When you click the start button it tells the pserver.exe to start. This is done by creating the cache/startWanted.txt file. Just a blank file.
You can either...
* start it via the browser. And then manually kill the pserver.exe
Then start forcebindip + pserver.
create a blank cache/startWanted.txt file. Then start forcebindip + pserver.
To stop it from automatically starting on reboot, start regedit.exe
Remove the anon_proxy_server key from...
LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Run
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Are you downloading a 700mb file?
Is this the instance running forcebindip?
no, i was not doing anything at all.
also, i noticed that pserver starts itself when windows starts? I do not have anything in the startup folder?
Check the log files for any messages. It shouldn't be doing anything if you're not using it.
If you turn it off via the web interface, it shouldn't start itself automatically.
i couldnt find any log files except for a logs folder parallel to the htdocs folder, which is obviously not specifically for each instance. i only duplicated the anon_proxy_server folder under htdocs. is that not the right way to do it? there is only a small error file in the logs folder. since all executables are name pserver, i guess i cant tell which instance it is..
right now, 1 instance of pserver will consume some 800MB of RAM (while the others not doing so) in a few hours and the proxies will stop working.
The logs can be viewed on the left side of the interface under "usage log", "error log"
Take a look at the difference in the configuration of this one that's not doing well. Maybe copy the config file from one of the ones that are working into cache/config.php or restart and copy the cache/config.php from the original archive you had downloaded. You can
do you know why i am getting all these socks connections (without needing logins) and failed http? these are not my IPs, and I am not doing anything except or starting pserver.exe. they start almost as soon as i turn on pserver.
http://white-light.net/apslog1.jpg
People go around and scan common ports, that's how they probably found you. Then they publish it somewhere and all sorts of random people know about it.
Change the proxy port to a strange number and add the user/pass security to it, maybe only allow certain IPs to visit it too if you only access it from certain places.
finally whitelisting my ip allows me to have pserver running for 5 hours.
now i guess the only problem i have is sometimes i cannot start pserver/forcebindip. normally when i start it, a window (comand prompt) popup. in this case, it flashes and disappears.
i still dont understand the start/restart/stop in the web interface (start.php, stop.php, etc.) which seems to have something to do with me not being able to start pserver/forcebindip. 'stop' gives me 'couldnt stop' and 'restart' gives me another instance of pserver which is obviously not what i want.
Great job there!
When you click the start button it tells the pserver.exe to start. This is done by creating the cache/startWanted.txt file. Just a blank file.
You can either...
* start it via the browser. And then manually kill the pserver.exe
Then start forcebindip + pserver.
To stop it from automatically starting on reboot, start regedit.exe
Remove the anon_proxy_server key from...
LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Run
copying the file works, even though i dont know the reason behind this. lol.
thanks again for the help. you are the best!