-
Notifications
You must be signed in to change notification settings - Fork 397
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.
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
Client can't connect to 1.8 spigot Server #67
Comments
Hello, |
Here ya go ;)
Using a Raspberry Pi + Mono from the repo. (Raspdebian) |
Thanks for your report, the crash has been fixed! Regarding the issue with this particular server: Even if ping is working this does not means that a Minecraft server is running on the server on port 25565. Or 4464 in your case. The app actually properly handles the ip:port syntax so I dont't know why it can't even etablish a connection. As you are running the app on a raspberry pi I guess you haven't tried on the Minecraft game itself, but could you try connecting on a computer where you are sure you can connect to the server? |
No the Server is online and i'm connected to it via the original mc client. |
I mean, can you try connecting using Minecraft Console Client, on a computer where you can access the server using the main Minecraft Game. |
i have also tried it. arch linux + mono from repo. same error |
I think the issue is on a lower level because it means that when in my code i use the function to connect using TCP to "the given server", it fails whereas a server should be reachable: this is outside the client's code. For investigation purposes, could you provide the server address? I suspect a DNS record issue while resolving "the sever address" (eg my.server.com) to "the server IP" (eg 123.123.123.123). |
mc.lyze.at or zap.lyze.at:4464 or 134.255.231.125:4464 |
mc.lyze.at -> cannot resolve (get a SOA dns record, "Unknown Host" from Minecraft) |
Well thats weird. http://i.imgur.com/w7X1HhG.png | http://i.imgur.com/742FPKK.png And also mc.lyze.at is a redirect to zap.lyze.at:4464 And you can't resolve mc.lyze.at because its a direct redirect to the port number. so when you write zap.lyze.at:4464 to make e.g. a ping it should also give you a cannot resolve as you see here:
|
Don't know why, but the addresses are now working except And when trying Not tried to actually login but it seems to work, no "Failed to connect" issue 😕 |
Ok thanks. Currently connecting works with zap.lyze.at:4464. It works normally when i start it myself via However when i try to start it as a cronjob at every Systemreboot the Client connects and disconnects after a second or two. Thats the cronjob entry: Thats the log file: |
Not sure why it does not work properly as a job, there is no particular reason why it would not work as a job but would work when manually launched. However, mono's implementation of AES crypto is incomplete so the current workaround to get the app working on mono will lose connection if no interaction is made (no message sent or received during a certain amount of time, ~30 secs). See thread post no 955 for detailed info. The app will properly work with the regular .NET framework, which is getting open source and should eventually be ported to linux in the future, resolving the issue. |
Where the ip is correct and pingable.
Where this is the config file:
Perhapse it can't connect to Servers with a custom port number
Note i'm using the Spigot Version: CraftBukkit version git-Spigot-952179b-f98775c (MC: 1.8) (Implementing API version 1.8-R0.1-SNAPSHOT)
The text was updated successfully, but these errors were encountered: