400 BAD REQUEST ON macOS

[tansunit]

Hello, some issues need help.

Node is running well, with Ubuntu 17.04.

Client is macOS 10.12.5, when I run this command

chmod +x mysterium_client_osx_amd64
sudo ./mysterium_client_osx_amd64 --node=[THE NODE KEY]

It responses:

Server response invalid: 400 BAD REQUEST

What's wrong with it?

[julien-blanchon]

Same issues.

[larkwins]

@mrmindorg Have u solved it?

[ghost]

Same

[JamesWuChina]

Now I am run the server side Same issues,i know the causes of the problem may be in the .env config MYSTERIUM_API_URL ,but i don't how to solved it.

[donce]

Hey @JamesWuChina, you have to be running api service, as described in Step 3 in CONTRIBUTING.md

[zyfdegh]

I also got this error in latest builds (api: 3/30 master e3deb5, node: 4/11 master cabd5b). The mysterium node failed to start and printed these

server response invalid: 404 NOT FOUND (http://my.hostname.com:8001/identities) error message: {unknown API method}

It's caused by incompatible API routes between mysterium api-server and clients.

After I inspect the codes and I find the mysterium API server (https://github.com/MysteriumNetwork/api) provides an API POST /v1/identities but the clients call them without v1/, it'sPOST /identities, that's the root cause resulting a 404 not found error.

[zyfdegh]

Fixed by appending v1/ to the URL in .env.
So, finally it will be something like this MYSTERIUM_API_URL=http://my.hostname.com:8001/v1

[donce]

@zyfdegh maybe you want to improve CONTRIBUTING.md to clarify this? :)

[zyfdegh]

Sure, I will. @donce

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This issue has been automatically closed because it has not had activity for a long time. If this issue is still valid, please ping a maintainer and ask them to label it as "pinned". Thank you for your contributions.