github-starred/frp

Fork 0

mirror of https://github.com/fatedier/frp.git synced 2026-05-15 08:05:49 -06:00

[GH-ISSUE #2115] Game Server cant be Pinged or reached (error: dial tcp ip:port: connect: connection refused) #1680

New issue

Closed

opened 2026-05-05 13:04:30 -06:00 by gitea-mirror · 6 comments

gitea-mirror commented

2026-05-05 13:04:30 -06:00

Owner

Originally created by @ghost on GitHub (Nov 26, 2020).
Original GitHub issue: https://github.com/fatedier/frp/issues/2115

[REQUIRED] hat version of frp are you using

Version: v0.34.3

[REQUIRED] What operating system and processor architecture are you using
OS: Ubuntu 20.04.1 LTS
CPU architecture: Home Server: AMD Ryzen 3400G(arm64) / VPS Server Intel(R) Xeon(R) CPU E5-2620 v3(arm64)

[REQUIRED] description of errors
When Server and client are perfectly fine connected and a ping is beeing sent to the Minecraft Server (by clicking refresh) the Proxy gets a Connection refused Error

[proxy.go:793] [5f58084e5a63e00b] [Minecraft] connect to local service [127.0.0.1:25566] error: dial tcp 127.0.0.1:25566: connect: connection refused

confile

[Minecraft]
type = tcp
local_port = 25566
remote_port = 25566

log file

https://pastebin.com/8TAUbrs7

Steps to reproduce the issue

Start Proxy like normal and have Minecraft server started
Try Pinging Server

Supplementary information

Can you guess what caused this issue
No

Checklist:

I included all information required in the sections above
I made sure there are no duplicates of this report (Use Search)

Originally created by @ghost on GitHub (Nov 26, 2020). Original GitHub issue: https://github.com/fatedier/frp/issues/2115     **[REQUIRED] hat version of frp are you using**  Version: v0.34.3 **[REQUIRED] What operating system and processor architecture are you using** OS: Ubuntu 20.04.1 LTS CPU architecture: Home Server: AMD Ryzen 3400G(arm64) / VPS Server Intel(R) Xeon(R) CPU E5-2620 v3(arm64) **[REQUIRED] description of errors** When Server and client are perfectly fine connected and a ping is beeing sent to the Minecraft Server (by clicking refresh) the Proxy gets a Connection refused Error [proxy.go:793] [5f58084e5a63e00b] [Minecraft] connect to local service [127.0.0.1:25566] error: dial tcp 127.0.0.1:25566: connect: connection refused **confile**  [Minecraft] type = tcp local_port = 25566 remote_port = 25566 **log file**  https://pastebin.com/8TAUbrs7 **Steps to reproduce the issue** 1. Start Proxy like normal and have Minecraft server started 2. Try Pinging Server **Supplementary information** **Can you guess what caused this issue** No **Checklist**:  - [x] I included all information required in the sections above - [x] I made sure there are no duplicates of this report [(Use Search)](https://github.com/fatedier/frp/issues?q=is%3Aissue)

gitea-mirror closed this issue

2026-05-05 13:04:31 -06:00

gitea-mirror commented

2026-05-05 13:04:33 -06:00

Author

Owner

@fatedier commented on GitHub (Nov 27, 2020):

Run netstat -antp|grep 25566 to see if your local service listen on this port?

@fatedier commented on GitHub (Nov 27, 2020): Run `netstat -antp|grep 25566` to see if your local service listen on this port?

gitea-mirror commented

2026-05-05 13:04:34 -06:00

Author

Owner

@ghost commented on GitHub (Nov 27, 2020):

I am sure that the service is running because im able to connect to the server locally over lan

i used a normal reverse shell before but wanted to simplefy things with a proxy

the reverse shell is still working properly and i can acess the minecraft server over my vps public ip adress

but when i try to use the proxy instead it always ends in the same error

@ghost commented on GitHub (Nov 27, 2020): I am sure that the service is running because im able to connect to the server locally over lan i used a normal reverse shell before but wanted to simplefy things with a proxy the reverse shell is still working properly and i can acess the minecraft server over my vps public ip adress but when i try to use the proxy instead it always ends in the same error

gitea-mirror commented

2026-05-05 13:04:34 -06:00

Author

Owner

@fatedier commented on GitHub (Nov 27, 2020):

Can you just paste the outputs of cmd i write above?

@fatedier commented on GitHub (Nov 27, 2020): Can you just paste the outputs of cmd i write above?

gitea-mirror commented

2026-05-05 13:04:35 -06:00

Author

Owner

@ghost commented on GitHub (Nov 27, 2020):

Heres the Line u requested
netstat -antp|grep 25566
tcp 0 0 192.168.0.51:25566 0.0.0.0:* LISTEN 1979/docker-proxy

maybe it is useful when i also tell u that the minecraft server is running over the website pterodactyl that creates docker containers

@ghost commented on GitHub (Nov 27, 2020): Heres the Line u requested netstat -antp|grep 25566 tcp 0 0 192.168.0.51:25566 0.0.0.0:* LISTEN 1979/docker-proxy maybe it is useful when i also tell u that the minecraft server is running over the website pterodactyl that creates docker containers

gitea-mirror commented

2026-05-05 13:04:35 -06:00

Author

Owner

@Becods commented on GitHub (Nov 28, 2020):

Heres the Line u requested
netstat -antp|grep 25566
tcp 0 0 192.168.0.51:25566 0.0.0.0:* LISTEN 1979/docker-proxy

maybe it is useful when i also tell u that the minecraft server is running over the website pterodactyl that creates docker containers

Your listening address is 192.168.0.51, so have you configured it correctly in the frpc.ini file?

@Becods commented on GitHub (Nov 28, 2020): > Heres the Line u requested > netstat -antp|grep 25566 > tcp 0 0 192.168.0.51:25566 0.0.0.0:* LISTEN 1979/docker-proxy > > maybe it is useful when i also tell u that the minecraft server is running over the website pterodactyl that creates docker containers Your listening address is 192.168.0.51, so have you configured it correctly in the frpc.ini file?

gitea-mirror commented

2026-05-05 13:04:36 -06:00

Author

Owner

@ghost commented on GitHub (Nov 28, 2020):

Oh, I fixed it!
It was really just setting additional value local_ip = 192.168.0.51 and it worked.
I fell really stupid.... but thanks so much for the help

@ghost commented on GitHub (Nov 28, 2020): Oh, I fixed it! It was really just setting additional value local_ip = 192.168.0.51 and it worked. I fell really stupid.... but thanks so much for the help