Bitcoin Forum

Bitcoin => Bitcoin Technical Support => Topic started by: Richy_T on December 19, 2015, 05:10:50 PM



Title: Upgraded to 0.12 now RPC calls giving 401 Unauthorized
Post by: Richy_T on December 19, 2015, 05:10:50 PM
Have RPC calls (or how the username/password are specified) changed? This was working fine until the upgrade.


Title: Re: Upgraded to 0.12 now RPC calls giving 401 Unauthorized
Post by: achow101 on December 19, 2015, 05:22:11 PM
0.12 of what software? Bitcoin Core?


Title: Re: Upgraded to 0.12 now RPC calls giving 401 Unauthorized
Post by: Richy_T on December 19, 2015, 09:23:45 PM
0.12 of what software? Bitcoin Core?

Sorry, yes. 0.12.0


Title: Re: Upgraded to 0.12 now RPC calls giving 401 Unauthorized
Post by: achow101_alt on December 21, 2015, 01:27:39 AM
There shouldn't be anything that is causing this. I don't think there were any changes to the RPC server for 0.12.


Title: Re: Upgraded to 0.12 now RPC calls giving 401 Unauthorized
Post by: Richy_T on December 22, 2015, 05:22:28 PM
There shouldn't be anything that is causing this. I don't think there were any changes to the RPC server for 0.12.

I haven't had chance to check yet but I believe it may be the rpcallowip option. I didn't need this in the version I was running previously but I suspect I do now.


Title: Re: Upgraded to 0.12 now RPC calls giving 401 Unauthorized
Post by: AtheistAKASaneBrain on December 22, 2015, 06:17:30 PM
Wait, 0.12 is already out? I've just tried going into Bitcoin.org and the version availible to download is still 0.11.2 so im pretty confused... also in the "News" section above in this forum it still says Bitcoin Core: 0.11.2? Are you talking about some sort of RC version? (release candidate)


Title: Re: Upgraded to 0.12 now RPC calls giving 401 Unauthorized
Post by: cr1776 on December 22, 2015, 06:32:08 PM
Wait, 0.12 is already out? I've just tried going into Bitcoin.org and the version availible to download is still 0.11.2 so im pretty confused... also in the "News" section above in this forum it still says Bitcoin Core: 0.11.2? Are you talking about some sort of RC version? (release candidate)

If he is running 0.12, he is running a beta - could be part of the issues. 


0.12.0 is hoped for by Feb 1, 2016.

https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-September/011182.html


Title: Re: Upgraded to 0.12 now RPC calls giving 401 Unauthorized
Post by: Richy_T on December 22, 2015, 06:49:22 PM
Wait, 0.12 is already out? I've just tried going into Bitcoin.org and the version availible to download is still 0.11.2 so im pretty confused... also in the "News" section above in this forum it still says Bitcoin Core: 0.11.2? Are you talking about some sort of RC version? (release candidate)

If he is running 0.12, he is running a beta - could be part of the issues.  


0.12.0 is hoped for by Feb 1, 2016.

https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-September/011182.html

Hmm. I just did a git clone. I thought it would be the latest stable release (I'm not that familiar with git).


Title: Re: Upgraded to 0.12 now RPC calls giving 401 Unauthorized
Post by: cr1776 on December 22, 2015, 06:56:53 PM
Wait, 0.12 is already out? I've just tried going into Bitcoin.org and the version availible to download is still 0.11.2 so im pretty confused... also in the "News" section above in this forum it still says Bitcoin Core: 0.11.2? Are you talking about some sort of RC version? (release candidate)

If he is running 0.12, he is running a beta - could be part of the issues.  


0.12.0 is hoped for by Feb 1, 2016.

https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-September/011182.html

Hmm. I just did a git clone. I thought it would be the latest stable release (I'm not that familiar with git).


Something like should get a particular branch to be sure which one you are on if you don't want to be running bleeding edge:
git clone -b <branch> <remote_repo>

e.g.
git clone -b v0.11.2  https://github.com/bitcoin/bitcoin

or to update:

cd bitcoin
git pull
git checkout v.0.11.2



Title: Re: Upgraded to 0.12 now RPC calls giving 401 Unauthorized
Post by: Richy_T on December 22, 2015, 06:59:23 PM
I'll give that a try. Thanks.


Title: Re: Upgraded to 0.12 now RPC calls giving 401 Unauthorized
Post by: achow101 on December 22, 2015, 07:33:27 PM

Hmm. I just did a git clone. I thought it would be the latest stable release (I'm not that familiar with git).
The current matter branch, which is what you cloned, is now for 0.13. 0.12 is not in its own branch but it isn't stable yet. It just has feature freeze. The latest stable would be in the 0.11 branch with the v0.11.2 tag.


Title: Re: Upgraded to 0.12 now RPC calls giving 401 Unauthorized
Post by: Richy_T on December 22, 2015, 08:21:31 PM

Hmm. I just did a git clone. I thought it would be the latest stable release (I'm not that familiar with git).
The current matter branch, which is what you cloned, is now for 0.13. 0.12 is not in its own branch but it isn't stable yet. It just has feature freeze. The latest stable would be in the 0.11 branch with the v0.11.2 tag.

It would explain why I couldn't find any release notes :D


Title: Re: Upgraded to 0.12 now RPC calls giving 401 Unauthorized
Post by: cr1776 on December 22, 2015, 08:41:27 PM

Hmm. I just did a git clone. I thought it would be the latest stable release (I'm not that familiar with git).
The current matter branch, which is what you cloned, is now for 0.13. 0.12 is not in its own branch but it isn't stable yet. It just has feature freeze. The latest stable would be in the 0.11 branch with the v0.11.2 tag.

It would explain why I couldn't find any release notes :D

For sure!  ;-)

Hopefully this doesn't indicate a bug in 0.12.


Title: Re: Upgraded to 0.12 now RPC calls giving 401 Unauthorized
Post by: Richy_T on December 22, 2015, 09:24:43 PM

Hmm. I just did a git clone. I thought it would be the latest stable release (I'm not that familiar with git).
The current matter branch, which is what you cloned, is now for 0.13. 0.12 is not in its own branch but it isn't stable yet. It just has feature freeze. The latest stable would be in the 0.11 branch with the v0.11.2 tag.

It would explain why I couldn't find any release notes :D

For sure!  ;-)

Hopefully this doesn't indicate a bug in 0.12.

Possibly they are just enforcing the rpcallowip option if they haven't before. Though localhost might be enabled by default and it may indeed be a bug *shrug*

Edit: Hmm, looks like rpcallowip is only for unauthenticated RPC connections? Oh well, I'm sure they'll sort it out before release. Quite possibly they're doing something clever like encrypting the rpcpassword.

I did notice they're letting the useragent comment be specified by an option which could make things interesting.