Skip to content
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

How to setup on Microsoft azure? #44

Closed
mrbaranovskiy opened this issue Jun 1, 2018 · 8 comments
Closed

How to setup on Microsoft azure? #44

mrbaranovskiy opened this issue Jun 1, 2018 · 8 comments

Comments

@mrbaranovskiy
Copy link

I've configured and ran the agent under ubuntu server but cannot access through the proxy. Probably there should be some additional port rules or smth like that...

@loskiq
Copy link
Contributor

loskiq commented Jun 1, 2018

Create a new virtual machine. Desirable is Debian 9.

Execute the command:

apt-get update && apt-get install git curl libssl-dev gcc make zlib1g-dev
git clone https://github.com/TelegramMessenger/MTProxy.git
cd MTProxy

Then follow the instructions of README.

@mrbaranovskiy
Copy link
Author

mrbaranovskiy commented Jun 1, 2018

Yes, I've done all of that. Agent works. I can event psping shows that 443 is responsive when the agent runs. (to do that I've allower the inbound and outbound rules for the ports.)

When I setup the proxy for the desktop app - "Connecting" infinite.

I'll play around...

@raccoon4x
Copy link

same problems. =(
but php version by danogentili worked

@iqdoctor
Copy link

iqdoctor commented Jun 1, 2018

Similar problem on Azure.
#41
Other hosters - ок.

@stek29 stek29 closed this as completed Jun 1, 2018
@stek29 stek29 added the duplicate This issue or pull request already exists label Jun 1, 2018
@stek29 stek29 reopened this Jun 1, 2018
@stek29 stek29 removed the duplicate This issue or pull request already exists label Jun 1, 2018
@stek29
Copy link
Collaborator

stek29 commented Jun 1, 2018

Maybe Azure has some settings for ipv4 forwarding too? (see #39 (comment))

@mrbaranovskiy
Copy link
Author

mrbaranovskiy commented Jun 2, 2018

IP forwarding doesn't help.
It looks like the server is accessible. I see the activity on the port. But for some reason, the connection is not accepted. I'll try to debug.

@mrbaranovskiy
Copy link
Author

mrbaranovskiy commented Jun 10, 2018

Looks like ports are closed by default on azure,
so go to the azure CLI and execute.

az vm open-port --resource-group myResourceGroup --name myVM --port 443

On my environment ip forwarding is turned on (not sure it is mandatory).

@ram3ai
Copy link

ram3ai commented Jun 7, 2019

Adding --nat-info private_ip:public_ip helped in my case.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants