Go-ethereum: Unable to attach

Created on 24 Dec 2017  Â·  26Comments  Â·  Source: ethereum/go-ethereum

System information

Geth version: 1.8.0-unstable-9d187f02
OS & Version: Windows

When I try to attach to the running local node, I get an unexpected error message:

PS C:\Users\mutexin> geth attach
Fatal: Unable to attach to remote geth: no known transport for URL scheme "c"
PS C:\Users\mutexin> geth attach --datadir "D:\Programs\Ethereum"
Fatal: Unable to attach to remote geth: no known transport for URL scheme "d"

Most helpful comment

Apparently on Windows we now have to specify the IPC path, and it was not necessary in Geth 1.7.3:
geth attach ipc:\\.\pipe\geth.ipc

All 26 comments

I think you should:
geth attach http://host:port
or
geth attach /xxxx/geth.ipc
xxxx is your datadir path

I'm getting the same error in the stable release of Geth 1.8, but only on Windows. On MacOS everything seems to be fine.

Apparently on Windows we now have to specify the IPC path, and it was not necessary in Geth 1.7.3:
geth attach ipc:\\.\pipe\geth.ipc

geth attach ipc:\\.\pipe\geth.ipc

This solution works for Win10 and v1.8.0-stable

It does. But once again an undocumented change, and a discrepancy between Windows and other platforms. As an online instructor trying to keep my cours material up-to-date, these things are a PITA

Quick Q - where do you find the IPC file? I'm running geth without installing it (just unzipped the folder)

never mind - just run the command in the same folder as the other instance and it seems to work

Is that expected behavior or will that be reverted to auto-discover the pipe on windows? I couldn't find anything in the changelogs, did I miss it?

BTW, within Git Bash (for Windows) it is also possible to connect as well as

./geth attach ipc:\\\\.\\pipe\\geth.ipc

image

but the console output is not colored.

Hi, specifying port worked for me. I had two nodes running in different ports and below attach command worked

geth attach http://localhost:8545
geth attach http://localhost:8547

confirmed geth attach ipc:\.\pipe\geth.ipc works for win env

Hi Team,

I am using windows 32 bit GoEth.
Receiving below issue please help out.

capture

Regards,
Ravi Shankar .L

@FirstBlockChain This is not Q&A, go to https://ethereum.stackexchange.com/
For a new bug report or on stackexchange , specify used version, and the way you launched.

At first glance, you may have missed \ before .
Seen
geth attach ipc:\.\pipe\geth.ipc

Should be
geth attach ipc:\\.\pipe\geth.ipc

Can this be made by default in windows? geth attach ipc:\\.\pipe\geth.ipc

Same error with this conditions:

can you give me 2 enthereum in the testnet..it's hard to get them ..my wallet address is:0x341453f0026b436b6f506626f74191e2461bbe16

can you give me 2 enthereum in the testnet..it's hard to get them in china.my wallet address is:0x341453f0026b436b6f506626f74191e2461bbe16

how can i find my ipc path on windows?

It always was geth attach ipc:\\.\pipe\geth.ipc, never a plain path. @davoodmood use the one mentioned previously. Geth also prints the path on startup.

@karalabe Why not make it default on windows?

Hmmm, it isn't? Then it should definitely be changed.

when we use : geth attach ipc:\.\pipe\geth.ipc ,we need to keep our startnode.cmd or geth --networkid 123 --dev --datadir data1 --rpc --rpcaddr 192.168.1.5 --rpc port 8545 --port 30303 running.

Apparently on Windows we now have to specify the IPC path, and it was not necessary in Geth 1.7.3:
geth attach ipc:\\.\pipe\geth.ipc

This is not working for me on Windows 10, Geth version 1.8.17-stable-8bbe7207. I get the error "Fatal: Unable to attach to remote geth: Timed out waiting for pipe '\.\pipe\geth.ipc' to come available"

After a long time I found out how to solve this.

First initialize your geth like this (if you want to use rinkeby):
geth --rinkeby --rpc --rpcapi="personal,eth,network,web3,net" --ipcpath "\.\pipe\geth.ipc"

And then open the console with the command:
geth attach ipc:\.\pipe\geth.ipc

After a long time I found out how to solve this.

First initialize your geth like this (if you want to use rinkeby):
geth --rinkeby --rpc --rpcapi="personal,eth,network,web3,net" --ipcpath ".\pipe\geth.ipc"

And then open the console with the command:
geth attach ipc:.\pipe\geth.ipc

still not helping

Tried all the above but got "unable to attach to remote geth: Access is denied."
What else can i do about this?

Was this page helpful?
0 / 5 - 0 ratings

Related issues

freshonline picture freshonline  Â·  3Comments

keitaj picture keitaj  Â·  3Comments

vogelito picture vogelito  Â·  3Comments

carver picture carver  Â·  3Comments

prene picture prene  Â·  3Comments