Port error

When running http://minecraft-api.com/v1/get/hivemc.eu:25565,
'


Warning: socket_connect(): Host lookup failed [-10001]: Unknown host in /var/www/app/models/Minecraft/Minecraft.php on line 58



Warning: socket_send(): unable to write to socket [32]: Broken pipe in /var/www/app/models/Minecraft/Minecraft.php on line 207



Warning: socket_send(): unable to write to socket [32]: Broken pipe in /var/www/app/models/Minecraft/Minecraft.php on line 67



Warning: socket_send(): unable to write to socket [32]: Broken pipe in /var/www/app/models/Minecraft/Minecraft.php on line 69



Warning: socket_send(): unable to write to socket [32]: Broken pipe in /var/www/app/models/Minecraft/Minecraft.php on line 207



Warning: socket_send(): unable to write to socket [32]: Broken pipe in /var/www/app/models/Minecraft/Minecraft.php on line 72



Warning: socket_send(): unable to write to socket [32]: Broken pipe in /var/www/app/models/Minecraft/Minecraft.php on line 74



Warning: socket_send(): unable to write to socket [32]: Broken pipe in /var/www/app/models/Minecraft/Minecraft.php on line 75



Warning: socket_send(): unable to write to socket [32]: Broken pipe in /var/www/app/models/Minecraft/Minecraft.php on line 207



Warning: socket_send(): unable to write to socket [32]: Broken pipe in /var/www/app/models/Minecraft/Minecraft.php on line 207



Warning: socket_send(): unable to write to socket [32]: Broken pipe in /var/www/app/models/Minecraft/Minecraft.php on line 83



Warning: socket_recv(): unable to read from socket [107]: Transport endpoint is not connected in /var/www/app/models/Minecraft/Minecraft.php on line 181



Warning: socket_recv(): unable to read from socket [107]: Transport endpoint is not connected in /var/www/app/models/Minecraft/Minecraft.php on line 88



Warning: socket_recv(): unable to read from socket [107]: Transport endpoint is not connected in /var/www/app/models/Minecraft/Minecraft.php on line 181

false
'

[Nickfost]

Use http://minecraft-api.com/v1/get/hivemc.eu instead

Nick Foster

me@nickfost.com

On Mon, Aug 18, 2014 at 12:26 PM, Spooky182002 notifications@github.com
wrote:

When running http://minecraft-api.com/v1/get/hivemc.eu:25565,
'

Warning: socket_connect(): Host lookup failed [-10001]: Unknown host in
/var/www/app/models/Minecraft/Minecraft.php on line 58

Warning: socket_send(): unable to write to socket [32]: Broken pipe in
/var/www/app/models/Minecraft/Minecraft.php on line 207

Warning: socket_send(): unable to write to socket [32]: Broken pipe in
/var/www/app/models/Minecraft/Minecraft.php on line 67

Warning: socket_send(): unable to write to socket [32]: Broken pipe in
/var/www/app/models/Minecraft/Minecraft.php on line 69

Warning: socket_send(): unable to write to socket [32]: Broken pipe in
/var/www/app/models/Minecraft/Minecraft.php on line 207

Warning: socket_send(): unable to write to socket [32]: Broken pipe in
/var/www/app/models/Minecraft/Minecraft.php on line 72

W arning: socket_send(): unable to write to socket [32]: Broken pipe in
/var/www/app/models/Minecraft/Minecraft.php on line 74

Warning: socket_send(): unable to write to socket [32]: Broken pipe in
/var/www/app/models/Minecraft/Minecraft.php on line 75

Warning: socket_send(): unable to write to socket [32]: Broken pipe in
/var/www/app/models/Minecraft/Minecraft.php on line 207

Warning: socket_send(): unable to write to socket [32]: Broken pipe in
/var/www/app/models/Minecraft/Minecraft.php on line 207

Warning: socket_send(): unable to write to socket [32]: Broken pipe in
/var/www/app/models/Minecraft/Minecraft.php on line 83

Warning: socket_recv(): unable to read from socket [107]: Transport
endpoint is not connected in /var/www/app/models/Minecraft/Minecraft.php
on line 181

Warning: socket_recv(): unable to read from socket [107]: Transport
endpoint is not connected in /var/www/app/models/Minecraft/Minecraft.php on
line 88Warning: socket_recv(): unable to read from socket [107]: Transport
endpoint is not connected in /var/www/app/models/Minecraft/Minecraft.php on
line 181 false '

—
Reply to this email directly or view it on GitHub
#8.

What if its running on another port, will it still work?

[Nickfost]

yup

Nick Foster

me@nickfost.com

On Mon, Aug 18, 2014 at 2:24 PM, Spooky182002 notifications@github.com
wrote:

What if its running on another port, will it still work?

—
Reply to this email directly or view it on GitHub
#8 (comment)
.

[Nickfost]

The self hosted route may be more resource intensive but its much greater in terms of reliability

[jackfirth]

I'm having the same issue, but relying on the default port won't work because I'm running on a non-standard port and there's multiple servers running on different ports for the same IP

[jackfirth]

I don't think this is the cause, but a related issue is that the constructor for MinecraftAPI has a default server value of "localhost:25565" while index.php uses just "localhost". As for the actual issue, according to this StackOverflow question it might have something to do with the hosting server's blocking of ports.

[jackfirth]

Okay, this is strange. I'm using Chrome as my browser and when I use that to view the response I still get the same error, but when I View Source the response then resend the request in the browser, it comes back as perfectly valid JSON with no issues whatsoever. I also experienced this same behavior earlier today at a separate computer with a different IP (also Chrome), and just now I cleared my browser history to see if that reset the issue. It doesn't, I'm now getting the API response perfectly fine - but only for that server. I can repeat this behavior - any server I request a specific port number for, it sends out the warning messages, but as soon as I View Source it responds fine.

[Nickfost]

I think it's an issue only related to the public API. I host this privately and it works perfectly. You should consider hosting your own.

On Tue, Aug 19, 2014 at 11:31 PM, JackFirth notifications@github.com
wrote:

Okay, this is strange. I'm using Chrome as my browser and when I use that to view the response I still get the same error, but when I View Source the response then resend the request in the browser, it comes back as perfectly valid JSON with no issues whatsoever. I also experienced this same behavior earlier today at a separate computer with a different IP (also Chrome), and just now I cleared my browser history to see if that reset the issue. It doesn't, I'm now getting the API response perfectly fine - but only for that server. I can repeat this behavior - any server I request a specific port number for, it sends out the warning messages, but as soon as I View Source it responds fine.

Reply to this email directly or view it on GitHub:
#8 (comment)

Strange.. i need to get this to work for one of my projects
On 20 Aug 2014 09:54, "Nick Foster" notifications@github.com wrote:

I think it's an issue only related to the public API. I host this
privately and it works perfectly. You should consider hosting your own.

On Tue, Aug 19, 2014 at 11:31 PM, JackFirth notifications@github.com
wrote:

Okay, this is strange. I'm using Chrome as my browser and when I use
that to view the response I still get the same error, but when I View
Source the response then resend the request in the browser, it comes back
as perfectly valid JSON with no issues whatsoever. I also experienced this
same behavior earlier today at a separate computer with a different IP
(also Chrome), and just now I cleared my browser history to see if that
reset the issue. It doesn't, I'm now getting the API response perfectly
fine - but only for that server. I can repeat this behavior - any server I
request a specific port number for, it sends out the warning messages, but

as soon as I View Source it responds fine.

Reply to this email directly or view it on GitHub:

#8 (comment)

—
Reply to this email directly or view it on GitHub
#8 (comment)
.

[Nickfost]

i'd conclude that the website is not running identical code to what is published here.