-rpcallowip

[ruimarinho]

-rpcallowip

[nunofgs]

Hey there @ekkis,

This is more of a configuration issue (not directly related to this repo) but I'm happy to help:

I see a few solutions here:

1. Allow the entire "172.x.x.x" range (using -rpcallow=172.0.0.0/8)
2. Specify a subnet of your choosing, as described in the documentation, then use it with the -rpcallowip= parameter.
3. Use network_mode: "bridge" which will make the container join the default bridge network and use the 172.17.0.x range.

Hope this helps!

[ekkis]

yes, you're right, it's not really a concern of this repo, so thanks for the suggestions. I need to research whether Docker creates all its networks within the 172.x range. if it does then #1 above certainly would work.

as for #2, rpcallow= is intriguing as I don't see it documented. this is where I'm looking: https://en.bitcoin.it/wiki/Running_Bitcoin and presumably it lets me allow by network name? if that were the case that would be ideal because that I know

[nunofgs]

rpcallow= is intriguing as I don't see it documented.

Sorry, that was a typo. In essence I was referring to setting a subnet manually, and then specifying it with -rpcallowip=.

[pavoltravnik]

Hey there @ekkis,

This is more of a configuration issue (not directly related to this repo) but I'm happy to help:

I see a few solutions here:

1. Allow the entire "172.x.x.x" range (using -rpcallow=172.0.0.0/8)
2. Specify a subnet of your choosing, as described in the documentation, then use it with the -rpcallowip= parameter.
3. Use network_mode: "bridge" which will make the container join the default bridge network and use the 172.17.0.x range.

Hope this helps!

Shouldn't it be 172.16.0.0/12?
Private_IPv4_addresses