Unity Mirror Problem Client Recv: failed to connect to ip=localhost port=7777 reason=System.Net.Sockets.SocketException (0x80004005): Could not resolve host 'localhost'

Questions & Answers
1

Hello! So I was having this Problem. I’m using Unity Mirror. When I Test the Host, the Host was Perfectly Working, and When I was testing the Join, I cant join keeps showing me this Error "Client Recv: failed to connect to ip=localhostport=7777 reason=System.Net.Sockets.SocketException (0x80004005): Could not resolve host ‘localhost’ ". Please Help Me solve this issue. Thank You

2

it keeps showing this Error
Client Recv: failed to connect to ip=Athena port=7777 reason=System.Net.Sockets.SocketException (0x80004005): Could not resolve host ‘Athena’
at System.Net.Dns.Error_11001 (System.String hostName) [0x00015] in <480201908ed94ddaa0561e2e6e0ddd4e>:0
at System.Net.Dns.GetHostByName (System.String hostName) [0x00021] in <480201908ed94ddaa0561e2e6e0ddd4e>:0
at System.Net.Dns.GetHostEntry (System.String hostNameOrAddress) [0x00052] in <480201908ed94ddaa0561e2e6e0ddd4e>:0
at System.Net.Dns.GetHostAddresses (System.String hostNameOrAddress) [0x00056] in <480201908ed94ddaa0561e2e6e0ddd4e>:0
at System.Net.Sockets.TcpClient.Connect (System.String hostname, System.Int32 port) [0x00053] in <480201908ed94ddaa0561e2e6e0ddd4e>:0
at Telepathy.Client.ReceiveThreadFunction (Telepathy.ClientConnectionState state, System.String ip, System.Int32 port, System.Int32 MaxMessageSize, System.Boolean NoDelay, System.Int32 SendTimeout, System.Int32 ReceiveTimeout, System.Int32 ReceiveQueueLimit) [0x0000f] in C:\Users\Benedict Peralta\Flee the Laboratory\Assets\Mirror\Runtime\Transport\Telepathy\Telepathy\Client.cs:133
UnityEngine.Debug:Log (object)
Telepathy.Client:ReceiveThreadFunction (Telepathy.ClientConnectionState,string,int,int,bool,int,int,int) (at Assets/Mirror/Runtime/Transport/Telepathy/Telepathy/Client.cs:156)
Telepathy.Client/<>c__DisplayClass14_0:b__0 () (at Assets/Mirror/Runtime/Transport/Telepathy/Telepathy/Client.cs:240)
System.Threading.ThreadHelper:ThreadStart ()

3

this happens if the ip address is correct and connects but there is no server running on that ip/port (explained if you double click on the information message and follow it to the script location