Topic: CLI failure
Expected behavior- CLI Login
Actual behavior CLI Failure using both typed in gmail and password and username/password combination
Resources (screenshots, code snippets etc.) Error Login failed: connect EHOSTUNREACH 93.105.88.243:8080
*I have tried using VPN and cell phone hotspot to rule out any firewall and still have no success. Please advise on what to do. *No documentation shows how to address this error.
FREE CONSULTATION
Hire our experts to build a dedicated project. We'll analyze your business requirements, for free.
Open
- User: Pro
- Premium support: No
- Technology: Other
- MDB Version: -
- Device: Mac
- Browser: chrome
- OS: OSX Big Sur
- Provided sample code: No
- Provided link: No
Sebastian Kaczmarek staff pro premium commented 4 years ago
It may sound weird but... does this problem occur on a different machine? I'm asking because it looks like for some reason the
8080port is being used for the login request which is wrong. That's why I'm wondering if you havePORTenvironment variable set on your system (or it gets overridden) and it's being used instead of the correct port number that should be set for your CLI version (automatically, no user intervention required).goodfellastech pro premium priority commented 4 years ago
I will try that today. I’m using Amazon C9 so I don’t set the port requests for the CLI. I will try that and let you know.
goodfellastech pro premium priority commented 4 years ago
Same error on local install on 2 machines. For some reason right now using the commands "npm install -g mdb-cli" and then "mdb login" us automatically triggering a request to that port.
I have not touched any settings on my end as my outbound app.js file port is using default process.ENV.PORT variables on all instances to allow it use whatever port is necessary for requests.
goodfellastech pro premium priority commented 4 years ago
Update: I was able to log in on a MacBook pro after reinstalling nodeJS and forcing the install using "sudo npm install mdb-cli -g".
I have had no such luck using Amazon AWS servers C9 application. Any idea there as I think the block might be from their server settings.
goodfellastech pro premium priority commented 4 years ago
So am I reading correctly in the fine print at the end of instructions that there is no way this is going to work for AWS C9 EC2 instances? This must be installed directly on a computer and can not be run remotely? This is disappointing, as I have several projects that I can not use this new CLI on because of this.
Sebastian Kaczmarek staff pro premium commented 4 years ago
@goodfellastech I must admit we haven't think about such use-cases when testing MDB CLI. However, I think you can override the
PORTvariable just for themdbcommand using this command:PORT=3033 mdb login. This should set the correct port number for MDB CLI. Please note that you need to use thePORT=3033prefix each time in that case. Maybe you could create an alias such asalias mdbcli="PORT=3033 mdb"and then use it like this:mdbcli login. Let me know if that helps