Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Connection reset by peer #236

Open
quardbreak opened this issue Sep 6, 2024 · 3 comments
Open

Connection reset by peer #236

quardbreak opened this issue Sep 6, 2024 · 3 comments
Labels
question

Comments

@quardbreak
Copy link

Version

spoofdpi v0.11.1

Operating System

Arch Linux x86_64

How are you running SpoofDPI?

Program was installed from from AUR, the package is spoofdpi-bin (https://aur.archlinux.org/packages/spoofdpi-bin)
Launch command is spoofdpi -banner=false -debug

Description

Hello, I can't connect to blocked websites from Russia while using spoofdpi. Although some parts may be out of scope of this project, I would like to know if there's anything I can do to use this program as intended.

What I do:

  1. Add address 127.0.0.1 and port 8080 in Firefox proxy settings (in my case, it's LibreWolf)
  2. Connect to blocked website https://soundcloud.com/jamatar/02-lepus-rising
  3. I get Error code: PR_END_OF_FILE_ERROR

Log file: spoofdpi-log3.txt
@LiquidTheDangerous
Copy link
Collaborator

@quardbreak I open this site from Russia. Confirm the problem

read: connection reset by peer

Looks like there is a problem on the remote service side

@Ledorub
Copy link
Collaborator

Ledorub commented Sep 6, 2024

Does it work now?

@quardbreak
Copy link
Author

quardbreak commented Sep 6, 2024 •
edited
Loading

@LiquidTheDangerous it's still the same (assuming you mean this is a temporary issue), can't access blocked websites. twitch.tv and other domains which not blocked are accessible with spoofdpi. Here's another try:

Details 
- ADDR    :  127.0.0.1
- PORT    :  8080
- DNS     :  8.8.8.8
- DEBUG   :  true

Press 'CTRL + c to quit'

INF 2024-09-07T00:14:08+03:00 [PROXY] created a listener on port 8080
DBG 2024-09-07T00:14:09+03:00 b0b637c9-0d372354-9991e37f-88133fdc [PROXY] request from 127.0.0.1:33196

CONNECT soundcloud.com:443 HTTP/1.1
User-Agent: Mozilla/5.0 (Windows NT 10.0; rv:130.0) Gecko/20100101 Firefox/130.0
Proxy-Connection: keep-alive
Connection: keep-alive
Host: soundcloud.com:443


DBG 2024-09-07T00:14:09+03:00 b0b637c9-0d372354-9991e37f-88133fdc [DNS] resolving soundcloud.com using general resolver(8.8.8.8:53)
DBG 2024-09-07T00:14:09+03:00 b0b637c9-0d372354-9991e37f-88133fdc [DNS] resolved 108.156.22.78 from soundcloud.com in 29 ms
DBG 2024-09-07T00:14:09+03:00 b0b637c9-0d372354-9991e37f-88133fdc [HTTPS] new connection to the server 192.168.1.146:42038 -> soundcloud.com
DBG 2024-09-07T00:14:09+03:00 b0b637c9-0d372354-9991e37f-88133fdc [HTTPS] sent connection estabalished to 127.0.0.1:33196
DBG 2024-09-07T00:14:09+03:00 b0b637c9-0d372354-9991e37f-88133fdc [HTTPS] client sent hello 662 bytes
DBG 2024-09-07T00:14:09+03:00 b0b637c9-0d372354-9991e37f-88133fdc [HTTPS] writing chunked client hello to soundcloud.com
DBG 2024-09-07T00:14:09+03:00 b0b637c9-0d372354-9991e37f-88133fdc [HTTPS] window-size: 0
DBG 2024-09-07T00:14:09+03:00 b0b637c9-0d372354-9991e37f-88133fdc [HTTPS] using legacy fragmentation
DBG 2024-09-07T00:14:09+03:00 b0b637c9-0d372354-9991e37f-88133fdc [HTTPS] error reading from soundcloud.com: read tcp 192.168.1.146:42038->108.156.22.78:443: read: connection reset by peer
DBG 2024-09-07T00:14:09+03:00 b0b637c9-0d372354-9991e37f-88133fdc [HTTPS] error reading from 127.0.0.1:33196: read tcp 127.0.0.1:8080->127.0.0.1:33196: use of closed network connection
DBG 2024-09-07T00:14:09+03:00 b0b637c9-0d372354-9991e37f-88133fdc [HTTPS] closing proxy connection: 127.0.0.1:33196 -> soundcloud.com
DBG 2024-09-07T00:14:09+03:00 b0b637c9-0d372354-9991e37f-88133fdc [HTTPS] closing proxy connection: soundcloud.com -> 127.0.0.1:33196
DBG 2024-09-07T00:14:09+03:00 0a0b3101-cfd35abe-81e36a8e-0d6fb426 [PROXY] request from 127.0.0.1:33198

CONNECT p.ctreserve.de:36762 HTTP/1.1
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:130.0) Gecko/20100101 Firefox/130.0
Proxy-Connection: keep-alive
Connection: keep-alive
Host: p.ctreserve.de:36762


DBG 2024-09-07T00:14:09+03:00 0a0b3101-cfd35abe-81e36a8e-0d6fb426 [DNS] resolving p.ctreserve.de using general resolver(8.8.8.8:53)
DBG 2024-09-07T00:14:09+03:00 0a0b3101-cfd35abe-81e36a8e-0d6fb426 [DNS] resolved 108.181.126.193 from p.ctreserve.de in 29 ms
DBG 2024-09-07T00:14:09+03:00 0a0b3101-cfd35abe-81e36a8e-0d6fb426 [HTTPS] dial tcp 108.181.126.193:36762: connect: connection refused
DBG 2024-09-07T00:14:09+03:00 dae5740e-9f6354b7-be9a7ee7-d94b029a [PROXY] request from 127.0.0.1:33212

CONNECT p.ctreserve.de:36762 HTTP/1.1
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:130.0) Gecko/20100101 Firefox/130.0
Proxy-Connection: keep-alive
Connection: keep-alive
Host: p.ctreserve.de:36762


DBG 2024-09-07T00:14:09+03:00 dae5740e-9f6354b7-be9a7ee7-d94b029a [DNS] resolving p.ctreserve.de using general resolver(8.8.8.8:53)
DBG 2024-09-07T00:14:09+03:00 dae5740e-9f6354b7-be9a7ee7-d94b029a [DNS] resolved 108.181.126.193 from p.ctreserve.de in 29 ms
DBG 2024-09-07T00:14:09+03:00 dae5740e-9f6354b7-be9a7ee7-d94b029a [HTTPS] dial tcp 108.181.126.193:36762: connect: connection refused
DBG 2024-09-07T00:14:09+03:00 d2d7c953-c6f09545-e6552b8f-3d75e771 [PROXY] request from 127.0.0.1:33216

CONNECT p.ctreserve.de:36762 HTTP/1.1
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:130.0) Gecko/20100101 Firefox/130.0
Proxy-Connection: keep-alive
Connection: keep-alive
Host: p.ctreserve.de:36762


DBG 2024-09-07T00:14:09+03:00 d2d7c953-c6f09545-e6552b8f-3d75e771 [DNS] resolving p.ctreserve.de using general resolver(8.8.8.8:53)
DBG 2024-09-07T00:14:09+03:00 d2d7c953-c6f09545-e6552b8f-3d75e771 [DNS] resolved 108.181.126.193 from p.ctreserve.de in 24 ms
DBG 2024-09-07T00:14:09+03:00 d2d7c953-c6f09545-e6552b8f-3d75e771 [HTTPS] dial tcp 108.181.126.193:36762: connect: connection refused
DBG 2024-09-07T00:14:09+03:00 94e248bd-088afbb8-49e1148d-11c78e93 [PROXY] request from 127.0.0.1:33228

CONNECT p.ctreserve.de:36762 HTTP/1.1
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:130.0) Gecko/20100101 Firefox/130.0
Proxy-Connection: keep-alive
Connection: keep-alive
Host: p.ctreserve.de:36762


DBG 2024-09-07T00:14:09+03:00 94e248bd-088afbb8-49e1148d-11c78e93 [DNS] resolving p.ctreserve.de using general resolver(8.8.8.8:53)
DBG 2024-09-07T00:14:09+03:00 94e248bd-088afbb8-49e1148d-11c78e93 [DNS] resolved 108.181.126.193 from p.ctreserve.de in 20 ms
DBG 2024-09-07T00:14:09+03:00 94e248bd-088afbb8-49e1148d-11c78e93 [HTTPS] dial tcp 108.181.126.193:36762: connect: connection refused
DBG 2024-09-07T00:14:09+03:00 439f2554-9ffdaa43-27826a02-6efe6b49 [PROXY] request from 127.0.0.1:33230

CONNECT p.ctreserve.de:36762 HTTP/1.1
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:130.0) Gecko/20100101 Firefox/130.0
Proxy-Connection: keep-alive
Connection: keep-alive
Host: p.ctreserve.de:36762


DBG 2024-09-07T00:14:09+03:00 439f2554-9ffdaa43-27826a02-6efe6b49 [DNS] resolving p.ctreserve.de using general resolver(8.8.8.8:53)
DBG 2024-09-07T00:14:09+03:00 439f2554-9ffdaa43-27826a02-6efe6b49 [DNS] resolved 108.181.126.193 from p.ctreserve.de in 30 ms
DBG 2024-09-07T00:14:09+03:00 439f2554-9ffdaa43-27826a02-6efe6b49 [HTTPS] dial tcp 108.181.126.193:36762: connect: connection refused
DBG 2024-09-07T00:14:09+03:00 415edea6-ca953905-e6dc47cc-d4a07168 [PROXY] request from 127.0.0.1:33234

CONNECT p.ctreserve.de:36762 HTTP/1.1
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:130.0) Gecko/20100101 Firefox/130.0
Proxy-Connection: keep-alive
Connection: keep-alive
Host: p.ctreserve.de:36762


DBG 2024-09-07T00:14:09+03:00 415edea6-ca953905-e6dc47cc-d4a07168 [DNS] resolving p.ctreserve.de using general resolver(8.8.8.8:53)
DBG 2024-09-07T00:14:09+03:00 415edea6-ca953905-e6dc47cc-d4a07168 [DNS] resolved 108.181.126.193 from p.ctreserve.de in 18 ms
DBG 2024-09-07T00:14:09+03:00 415edea6-ca953905-e6dc47cc-d4a07168 [HTTPS] dial tcp 108.181.126.193:36762: connect: connection refused
DBG 2024-09-07T00:14:09+03:00 22fc0bf0-492a64ec-960561e2-da8b76d7 [PROXY] request from 127.0.0.1:33244

CONNECT p.ctreserve.de:36762 HTTP/1.1
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:130.0) Gecko/20100101 Firefox/130.0
Proxy-Connection: keep-alive
Connection: keep-alive
Host: p.ctreserve.de:36762


DBG 2024-09-07T00:14:09+03:00 22fc0bf0-492a64ec-960561e2-da8b76d7 [DNS] resolving p.ctreserve.de using general resolver(8.8.8.8:53)
DBG 2024-09-07T00:14:09+03:00 22fc0bf0-492a64ec-960561e2-da8b76d7 [DNS] resolved 108.181.126.193 from p.ctreserve.de in 19 ms
DBG 2024-09-07T00:14:09+03:00 22fc0bf0-492a64ec-960561e2-da8b76d7 [HTTPS] dial tcp 108.181.126.193:36762: connect: connection refused
DBG 2024-09-07T00:14:09+03:00 79fdea99-a9995648-08c964e7-d9c25665 [PROXY] request from 127.0.0.1:33256

CONNECT p.ctreserve.de:36762 HTTP/1.1
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:130.0) Gecko/20100101 Firefox/130.0
Proxy-Connection: keep-alive
Connection: keep-alive
Host: p.ctreserve.de:36762


DBG 2024-09-07T00:14:09+03:00 79fdea99-a9995648-08c964e7-d9c25665 [DNS] resolving p.ctreserve.de using general resolver(8.8.8.8:53)
DBG 2024-09-07T00:14:09+03:00 79fdea99-a9995648-08c964e7-d9c25665 [DNS] resolved 108.181.126.193 from p.ctreserve.de in 17 ms
DBG 2024-09-07T00:14:09+03:00 79fdea99-a9995648-08c964e7-d9c25665 [HTTPS] dial tcp 108.181.126.193:36762: connect: connection refused
DBG 2024-09-07T00:14:09+03:00 b06b27ca-972a4788-99af6c09-d9834aa3 [PROXY] request from 127.0.0.1:33262

CONNECT p.ctreserve.de:36762 HTTP/1.1
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:130.0) Gecko/20100101 Firefox/130.0
Proxy-Connection: keep-alive
Connection: keep-alive
Host: p.ctreserve.de:36762


DBG 2024-09-07T00:14:09+03:00 b06b27ca-972a4788-99af6c09-d9834aa3 [DNS] resolving p.ctreserve.de using general resolver(8.8.8.8:53)
DBG 2024-09-07T00:14:09+03:00 b06b27ca-972a4788-99af6c09-d9834aa3 [DNS] resolved 108.181.126.193 from p.ctreserve.de in 20 ms
DBG 2024-09-07T00:14:09+03:00 b06b27ca-972a4788-99af6c09-d9834aa3 [HTTPS] dial tcp 108.181.126.193:36762: connect: connection refused
DBG 2024-09-07T00:14:09+03:00 3682b220-8693d65e-53f543c1-f912e143 [PROXY] request from 127.0.0.1:33270

CONNECT p.ctreserve.de:36762 HTTP/1.1
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:130.0) Gecko/20100101 Firefox/130.0
Proxy-Connection: keep-alive
Connection: keep-alive
Host: p.ctreserve.de:36762


DBG 2024-09-07T00:14:09+03:00 3682b220-8693d65e-53f543c1-f912e143 [DNS] resolving p.ctreserve.de using general resolver(8.8.8.8:53)
DBG 2024-09-07T00:14:09+03:00 3682b220-8693d65e-53f543c1-f912e143 [DNS] resolved 108.181.126.193 from p.ctreserve.de in 19 ms
DBG 2024-09-07T00:14:10+03:00 3682b220-8693d65e-53f543c1-f912e143 [HTTPS] dial tcp 108.181.126.193:36762: connect: connection refused

And here's another try to connect, now with ntc.party:

Details 
CONNECT ntc.party:443 HTTP/1.1
User-Agent: Mozilla/5.0 (Windows NT 10.0; rv:130.0) Gecko/20100101 Firefox/130.0
Proxy-Connection: keep-alive
Connection: keep-alive
Host: ntc.party:443


DBG 2024-09-07T00:09:50+03:00 db4e535b-b736efb8-bf8847c2-dd7a9798 [DNS] resolving ntc.party using general resolver(8.8.8.8:53)
DBG 2024-09-07T00:09:50+03:00 db4e535b-b736efb8-bf8847c2-dd7a9798 [DNS] resolved 130.255.77.28 from ntc.party in 20 ms
DBG 2024-09-07T00:09:50+03:00 db4e535b-b736efb8-bf8847c2-dd7a9798 [HTTPS] new connection to the server 192.168.1.146:45476 -> ntc.party
DBG 2024-09-07T00:09:50+03:00 db4e535b-b736efb8-bf8847c2-dd7a9798 [HTTPS] sent connection estabalished to 127.0.0.1:59850
DBG 2024-09-07T00:09:50+03:00 db4e535b-b736efb8-bf8847c2-dd7a9798 [HTTPS] client sent hello 657 bytes
DBG 2024-09-07T00:09:50+03:00 db4e535b-b736efb8-bf8847c2-dd7a9798 [HTTPS] writing chunked client hello to ntc.party
DBG 2024-09-07T00:09:50+03:00 db4e535b-b736efb8-bf8847c2-dd7a9798 [HTTPS] window-size: 0
DBG 2024-09-07T00:09:50+03:00 db4e535b-b736efb8-bf8847c2-dd7a9798 [HTTPS] using legacy fragmentation
DBG 2024-09-07T00:09:50+03:00 db4e535b-b736efb8-bf8847c2-dd7a9798 [HTTPS] error reading from ntc.party: read tcp 192.168.1.146:45476->130.255.77.28:443: read: connection reset by peer
DBG 2024-09-07T00:09:50+03:00 db4e535b-b736efb8-bf8847c2-dd7a9798 [HTTPS] error reading from 127.0.0.1:59850: read tcp 127.0.0.1:8080->127.0.0.1:59850: use of closed network connection
DBG 2024-09-07T00:09:50+03:00 db4e535b-b736efb8-bf8847c2-dd7a9798 [HTTPS] closing proxy connection: 127.0.0.1:59850 -> ntc.party
DBG 2024-09-07T00:09:50+03:00 db4e535b-b736efb8-bf8847c2-dd7a9798 [HTTPS] closing proxy connection: ntc.party -> 127.0.0.1:59850

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
question
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@Ledorub @quardbreak @LiquidTheDangerous