-
-
Notifications
You must be signed in to change notification settings - Fork 75
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
error while connecting #102
Comments
We were running some maintenance on the servers. Should be all good now. Keeping this open for now as a reference. |
I have set up my own server and I get "connection successful" on my phones. However I can't connect to the proxies nor change the IP using API. Do we need to do modifications to our server? |
im getting this error as well! I even opened up the port on my ubuntu server and still cant connect. I have tmobile |
Does the app show as connected? Where is the server hosted? |
Yes the app shows "connection success" and I get the ports and username and password. The server is hosted in Iran. |
Is there a way for the developer to solve this problem or is this a paid service? |
I tried two other servers in Germany and Turkey from two different datacenters. The same problem remains unfortunately. I appreciate it that you made this awesome application opensource and free. I hope you can solve this problem. Thank you @AbedElezz. |
Have you opened ports 10000-60000? |
I just did. Still no results. |
The app and the script work perfectly fine. My problem was server side. Some companies and datacenters have special limitations, so that you can't use the server as a proxy server. Anyways I think it is better to add these comments to README file:
Thank you again @AbedElezz @YamenAlazzam1 |
This issue has appeared again. Is maintenance going on? |
appeared indeed. Sometimes connecting sometimes not. |
hello, i have downloaded your app Proxidize Android Legacy to create my own 4g proxy but every time i press connect it says "Not connected, restart the app and try again " may i know why?
The text was updated successfully, but these errors were encountered: