Skip to content
This repository has been archived by the owner on Apr 10, 2024. It is now read-only.

Failed to connect to localhost/0:0:0:0:0:0:0:1:8545 when running the class org.web3j.examples.rx.Main #1

Open
bitsabhi opened this issue Jan 24, 2018 · 4 comments

Comments

@bitsabhi
Copy link

bitsabhi commented Jan 24, 2018

No description provided.

@bitsabhi
Copy link
Author

Logs....

Caused by: java.net.ConnectException: Failed to connect to localhost/0:0:0:0:0:0:0:1:8545
at okhttp3.internal.connection.RealConnection.connectSocket(RealConnection.java:225)
at okhttp3.internal.connection.RealConnection.connect(RealConnection.java:149)
at okhttp3.internal.connection.StreamAllocation.findConnection(StreamAllocation.java:195)
at okhttp3.internal.connection.StreamAllocation.findHealthyConnection(StreamAllocation.java:121)
at okhttp3.internal.connection.StreamAllocation.newStream(StreamAllocation.java:100)
at okhttp3.internal.connection.ConnectInterceptor.intercept(ConnectInterceptor.java:42)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:92)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:67)
at okhttp3.internal.cache.CacheInterceptor.intercept(CacheInterceptor.java:93)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:92)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:67)
at okhttp3.internal.http.BridgeInterceptor.intercept(BridgeInterceptor.java:93)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:92)
at okhttp3.internal.http.RetryAndFollowUpInterceptor.intercept(RetryAndFollowUpInterceptor.java:120)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:92)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:67)
at okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.java:185)
at okhttp3.RealCall.execute(RealCall.java:69)
at org.web3j.protocol.http.HttpService.performIO(HttpService.java:104)
at org.web3j.protocol.Service.send(Service.java:31)
at org.web3j.protocol.core.Request.send(Request.java:71)
at org.web3j.protocol.core.filters.BlockFilter.sendRequest(BlockFilter.java:24)
at org.web3j.protocol.core.filters.Filter.run(Filter.java:45)
... 13 more
Caused by: java.net.ConnectException: Connection refused: connect
at java.net.DualStackPlainSocketImpl.waitForConnect(Native Method)
at java.net.DualStackPlainSocketImpl.socketConnect(Unknown Source)
at java.net.AbstractPlainSocketImpl.doConnect(Unknown Source)
at java.net.AbstractPlainSocketImpl.connectToAddress(Unknown Source)
at java.net.AbstractPlainSocketImpl.connect(Unknown Source)
at java.net.PlainSocketImpl.connect(Unknown Source)
at java.net.SocksSocketImpl.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at okhttp3.internal.platform.Platform.connectSocket(Platform.java:124)
at okhttp3.internal.connection.RealConnection.connectSocket(RealConnection.java:223)
... 35 more

@MuratDoner-zz
Copy link

Use this to start over localhost and will work:
geth --rpc --rpcaddr "127.0.0.1" --rpcport "8545"

You are currently using IPC as far I see.

@SnuK87
Copy link

SnuK87 commented Aug 9, 2018

I had the same problem when running the node via mist.

Starting it via geth --rpc --rpcaddr "127.0.0.1" --rpcport "8545" solved the problem.

@PolyRibina
Copy link

The latest versions of Geth (after 1.10.8-stable) do not support --rpc but fortunately, as you can see in the Command-line Options, it has been replaced by the --http option. So your command should look like this:

geth --http --http.addr "127.0.0.1" --http.port "8545"

This solved my problem.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants