-
Notifications
You must be signed in to change notification settings - Fork 200
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
🐛 : StatusError: HTTPError: 405 Client Error: Method Not Allowed for url: http://localhost:5001/api/v0/version?stream-channels=true
#318
Comments
StatusError: HTTPError: 405 Client Error: Method Not Allowed for url: http://localhost:5001/api/v0/version?stream-channels=true
StatusError: HTTPError: 405 Client Error: Method Not Allowed for url: http://localhost:5001/api/v0/version?stream-channels=true
@hemangjoshi37a what kubo version are you using? You can get it by running this in your shell: ipfs --version |
(base) hemang@hemang-HP-Pavilion-g6-Notebook-PC:~$ ipfs --version
ipfs version 0.17.0 |
Are we attempting to provide users with version-based options? Because I personally think, despite there being consistent releases of Kubo, we should only support a single version of IPFS. It could seem like more work to constantly update code to support changes made in Kubo but it could at least provide a bit of control into what the actual issues are with the library. I was just curious because most of the issues are either associated with version issues or with the connection to the api which I believe is caused by the version being out of date causing an exception to be raised. |
@kasteph @Wizock and all other contributors, I appreciate your insights and comments on this issue. From my understanding, the bug The IPFS version I'm running is @Wizock 's suggestion is intriguing - focusing on a single, consistent version of IPFS and Kubo, which would make debugging and code maintenance more straightforward. This could prevent issues arising from version incompatibility in the future. However, we also need to bear in mind that we are potentially limiting the usability for those on different versions. As a potential resolution to this issue, I'd suggest checking the HTTP method being used in the Nonetheless, I agree that a long-term strategy for managing IPFS version compatibility should be put in place to prevent similar issues in the future. I'm open to further discussions and suggestions from the community. |
Code :
Error :
The text was updated successfully, but these errors were encountered: