Hi all,
I have forwarded the relevant port from my firewall into the Grin wallet and it’s currently listening on my local IP which is also the target port from the forward.
The issue here is that Bitforex won’t accept MY-IP:port as the address? It says the address isn’t valid?
Any help would be appreciated
Make sure you are putting your public IP into Bitforex, not your internal IP which probably starts with 192.168…
You can learn your public IP by searching the web for the phrase, “What is my IP?”
EDIT: another thing to check would be to see if you need to type http:// before the IP address.
Thanks for the reply. I am putting in my external/WAN IP then a colon and the external port that forwards to my internal IP/port/wallet. Obviously no spaces.
Does it need http:// or https:// infront of it?
That’s the correct IP to put in. Try it with http:// in front. If that doesn’t work, does anyone else have any ideas?
I know a workaround. You could withdraw to a different exchange that does support what you want, and then withdraw again. Tradeogre was cool because you actually download a file when you withdraw. Bitmesh has been top notch all around. Polo is good too. Anyway, dunno if that helps but I figured I’d say it anyway.
So I’ve tried to send it to my IP with and without the secure https:// and the other with http://. Also sent to Poloniex around an hour ago too.
The non secure one says ‘audit complete’ on Bitforex, the other two say ‘applying’ and are still cancellable. Absolutely no idea, should I keep waiting?
Edit: Also have tried to send 0.5 grin from Kucoin. It say status: in progress (it has been almost 24 hrs), remark: test. Seriously, this coin sounds great but if people can’t easily send or receive them, it’s not going to take off very much…
The plot thickens:
support@bitforex.com|20:04 (0 minutes ago)||![]
Dear user,
We don’t support the GRIN address from poloniex.com. Please change your withdrawal address. We will cancel your withdrawal. Thanks for your support!
Best Regards,
So I’ve now been able to send a few Grin to myself, but the transactions are unconfirmed and don’t seem to want to finalize. Also can’t find them on the block explorer.
./grin-wallet txs shows transactions but the references can’t be searched in the block explorer?
step 1/4
You have to wait a while.
Could you elaborate? I thought Grin was supposed to be a much smaller blockchain than BTC? Surely it can’t take a few days to sync?
Does it still sync? Can you post the node log (~/.grin/main/grin-server.log)?
I’ve made sure all ports, 3413, 3414 & 3415 were forwarded, which I thought fixed it, but it’s dropped to 0.2kbps download at 98% on step 2/4 again.
Here’s the Pastebin. Thanks
Dropping below 100% and moving across steps is normal, the errors in your log are not:
20190519 12:55:57.309 ERROR grin_util::logger -
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Chain(Error { inner:
TxHashSetErr: Permission denied (os error 13) })': src/libcore/result.rs:997stack backtrace:
20190519 12:57:38.347 INFO grin_servers::grin::server - Starting server, genesis block: 40adad0aec27
20190519 12:57:38.390 ERROR grin_util::logger -
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Chain(Error { inner:
TxHashSetErr: Permission denied (os error 13) })': src/libcore/result.rs:997stack backtrace:
20190519 13:07:34.330 ERROR grin_util::logger -
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: IOError(Os { code: 11, kind: WouldBlock, message: "Resource temporarily unavailable" })': src/libcore/result.rs:997stack backtrace:
20190519 13:08:06.308 ERROR grin_util::logger -
thread 'apis' panicked at 'error binding to 127.0.0.1:3413: error creating server listener: Address already in use (os error 98)': /home/vsts/.cargo/registry/src/github.com-1ecc6299db9ec823/hyper-0.12.27/src/server/mod.rs:115stack backtrace:
Seems like you have permission issues with running grin. Not sure why that’s the case in your system, usually grin can run just fine as a normal user.
Thanks. I’ve been running it even as sudo, and have set the grin folders as chmod 777 but it still kicks me out when it gets to step 3/4. Can’t remember the exact message off the top of my head.
Edit: I’ve tried to find the folder ‘src/libcore’ but can’t find where it’s stored. It’s not an Ubuntu one
Do you see any errors in the log now? Note that if you run as root you will get a .grin folder under /root. In general, you shouldn’t need to run grin as root, it’s far from safe. Also, I would suggest that you close all ports but 3415 which you only need if you plan to receive payments via http.
I can see activity, but it’s still literally 0.1 kbps or so. The stuff in the log that could be relevant is:
0190521 15:17:46.742 INFO grin_servers::common::adapters - Received 32 block headers from 132.232.134.4:13414
20190521 15:18:02.687 INFO grin_servers:
:sync::header_sync - sync: ban a fraud peer: 132.232.134.4:13414, claimed height: 180866, total difficulty: 535174123132719
20190521 15:19:06.725 INFO grin_servers::common::adapters - Received 32 block headers from 47.97.198.21:3414
20190521 15:19:06.725 ERROR grin_store::types - Corrupted storage, could not read an entry from data file: Custom { kind: Other, error: IOErr(“failed to fill whole buffer”, UnexpectedEof) }
20190521 15:19:06.725 ERROR grin_store::types - Corrupted storage, could not read an entry from data file: Custom { kind: Other, error: IOErr(“failed to fill whole buffer”, UnexpectedEof) }
20190521 15:19:06.727 ERROR grin_store::types - Corrupted storage, could not read an entry from data file: Custom { kind: Other, error: IOErr(“failed to fill whole buffer”, UnexpectedEof) }
20190521 15:19:06.727 ERROR grin_store::types - Corrupted storage, could not read an entry from data file: Custom { kind: Other, error: IOErr(“failed to fill whole buffer”, UnexpectedEof) }
20190521 15:19:06.979 INFO grin_servers::common::adapters - Received 32 block headers from 47.97.198.21:3414
20190521 15:23:53.924 INFO grin_servers::common::types - DandelionEpoch: next_epoch: is_stem: true (90%), relay: Some(PeerAddr(V4(104.248.215.214:3414)))
20190521 15:33:45.662 INFO grin_servers::common::adapters - Received 32 block headers from 18.233.83.171:3414
20190521 15:33:45.745 ERROR grin_store::types - Corrupted storage, could not read an entry from data file: Custom { kind: Other, error: IOErr(“failed to fill whole buffer”, UnexpectedEof) }
20190521 15:33:45.745 ERROR grin_store::types - Corrupted storage, could not read an entry from data file: Custom { kind: Other, error: IOErr(“failed to fill whole buffer”, UnexpectedEof) }
20190521 15:33:45.745 ERROR grin_store::types - Corrupted storage, could not read an entry from data file: Custom { kind: Other, error: IOErr(“failed to fill whole buffer”, UnexpectedEof) }
20190521 15:33:45.745 ERROR grin_store::types - Corrupted storage, could not read an entry from data file: Custom { kind: Other, error: IOErr(“failed to fill whole buffer”, UnexpectedEof) }
20190521 15:33:45.831 INFO grin_servers::common::adapters - Received 32 block headers from 18.233.83.171:3414
From the wallet CLI:
leopheard@hp-laptop:~/.wine/dosdevices/z:/home/leo/Data/grin-wallet$ ./grin-wallet info
Password: xxxx
20190521 15:32:33.902 ERROR grin_wallet_impls::node_clients::http - Get chain height error: Request error: Cannot make request: an error occurred trying to connect: Connection refused (os error 111)
Connection refused? Might reboot router, restart computer and try again.
Sorry to bump, but my latest logs are here:
Should I accept the grin that are stuck as lost forever? The node crashes after stage 3/4 or 4/4 and says ‘illegal instruction’
Don’t think Grins can be ‘lost’ unless there is a bug in the restore process, which is still a possibility but highly unlike. More likely, your grins are sitting in the sender’s wallet so you need to request the sender to rebroadcast the tx. As far as the node error you are seeing, I’d suggest opening a github issue at mimblewimble/grin.
Some coins are still showing as awaiting confirmation and they’ve been there over a month. Will they still be in my original balance on the exchange?