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 update to latest version? #256

Closed
Iowerth opened this issue Feb 1, 2019 · 5 comments
Closed

How to update to latest version? #256

Iowerth opened this issue Feb 1, 2019 · 5 comments

Comments

@Iowerth
Copy link

Iowerth commented Feb 1, 2019

Hello. I have version mtproxy-0.01 compiled at Jun 1 2018 12:06:27 by gcc 5.4.0 20160609 64-bit after commit e231d04
And I want to update MTProxy up to latest version to use 'dd' prefix. How can I do it? Sorry, I'm newbie to this.
I think that some instruction may be helpful.

@Iowerth Iowerth changed the title How to update to last version? How to update to latest version? Feb 1, 2019
@onikethem
Copy link

onikethem commented Feb 1, 2019 via email

@HirbodBehnam
Copy link

Hello
There is no specific way to upgrade. You need to rebuild the proxy yourself. You have to clone the project and build it again. And dont use docker as it's outdated.

Also if you server's OS is Centos 7, you can have a look at my automatic installer. Link

@onikethem
Copy link

onikethem commented Feb 1, 2019 via email

@AlexMTX
Copy link

AlexMTX commented Feb 1, 2019

If you have installed it according to a readme, you must have a MTProto git repository. Update it, rebuild and update the service:

git pull
make
systemctl daemon-reload
systemctl restart MTProxy.service
systemctl status MTProxy.service

Please, note that 'dd' must be added on a client's side, i.e. add 'dd' to the secret in the connection link before sharing it and it should be added on a client's phone like this. However, the current version allows a non-padded messaging too. I mean if a client deletes manually 'dd' in his config it will work too and may cause blocking.
I would include a pull request to force only padded messaging to fix this. #248
Tell me if you need more details on this

@Iowerth
Copy link
Author

Iowerth commented Feb 2, 2019

@AlexMTX thx, it was helpful! I've update it :)

@Iowerth Iowerth closed this as completed Feb 2, 2019
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

4 participants