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

Access MK in Digital Ocean #44

Closed
dalcero opened this issue Jul 8, 2019 · 8 comments
Closed

Access MK in Digital Ocean #44

dalcero opened this issue Jul 8, 2019 · 8 comments

Comments

@dalcero
Copy link

dalcero commented Jul 8, 2019

Hello. As I access the Mikrotik with a Digital Ocean server, I have already released ports 8728 and 8729 and it still does not work .. It gives the error (Unable to establish socket session, Connection timed out)

@BenMenking
Copy link
Owner

A couple things I would check:

Is api and/or api-ssl service enabled on mikrotik?
Are there any mikrotik rules preventing connection to 8728 or 8729?
Are my digital Ocean access rules setup correctly?

@tahsin352
Copy link

@dalcero have you setup iptables or firewall in your digital ocean server?? what do you mean by "already released ports 8728 and 8729 " ?
"Connection timed out" means port is not enabled for access.
Is your mikrotik working? or it is a problem with API access to mikrotik?

@rainiur
Copy link

rainiur commented Aug 1, 2019

api service is enabled and my server does not have a firewall. I am making a connection but unable to authenticate. I am able to login through the GUI with the username and password but unable to connect via the api. I am running 6.45.1. Any ideas?

@BenMenking
Copy link
Owner

Can you provide more troubleshooting information? What message does the script return?

@wecc
Copy link

wecc commented Nov 2, 2019

I'm not entirely sure but I think this issue might not be related to timeouts but instead caused by a breaking change in the login process (introduced in 6.45.1).

We also encountered issues being unable to login and after some troubleshooting, we discovered it was actually the login that failed and the multiple retries giving the impression of a timeout.

From the 6.45.1 release notes (https://mikrotik.com/download/changelogs):

Important note!!!
Due to removal of compatibility with old version passwords in this version, downgrading to any version prior to v6.43 (v6.42.12 and older) will clear all user passwords and allow password-less authentication. Please secure your router after downgrading.
Old API authentication method will also no longer work, see documentation for new login procedure: https://wiki.mikrotik.com/wiki/Manual:API#Initial_login

The wiki link describes the changes in more detail.

I'd be happy to help to solve this issue, please let me know if I can provide any additional details.

@pchf3788
Copy link

I hope the author updates API version, rookie learning!

@bgf2
Copy link

bgf2 commented Jan 28, 2020

yes that is because the API is updated in routeros but its not updated in this class yet.

@Chupaka
Copy link

Chupaka commented Jan 30, 2020

but its not updated in this class yet.

WUT? It was updated more than a year ago!
#30

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

9 participants