alecgorge/jsonapi

errors in log

Opened this issue · 5 comments

tryolivier commented

hello

I have errors in logs

I use the last dev version : http://ci.alecgorge.com/job/JSONAPI/lastSuccessfulBuild/artifact/builds/Spigot-all/JSONAPI-BLEEDING-mc1.9-R0.1-SNAPSHOT.jar

errors in logs http://hastebin.com/ayuqulowez.vbs

You know why ? and how resolve ?

thanks !

electronicboy commented

Guess of the translation but that port is already in use by another
program, you'll need to change the port in the config or find what is using
the network port and change that. (Could be another server with jsonapi)
On May 2, 2016 12:18 PM, "tryolivier" notifications@github.com wrote:

hello

I have errors in logs

I use the last dev version :
http://ci.alecgorge.com/job/JSONAPI/lastSuccessfulBuild/artifact/builds/Spigot-all/JSONAPI-BLEEDING-mc1.9-R0.1-SNAPSHOT.jar

errors in logs http://hastebin.com/ayuqulowez.vbs

You know why ? and how resolve ?

thanks !

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
#485

tryolivier commented

but I use Jsonapi on all server of my bungeecord

so I don't understand

electronicboy commented

Each instance of JSONAPI needs to be on a different network port, this can be changed in the configuration files for the plugin.

On 2 May 2016, at 13:19, tryolivier notifications@github.com wrote:

but I use Jsonapi on all server of my bungeecord

so I don't understand

—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub #485 (comment)

tryolivier commented

I put a different port on each server and now I have that :

http://hastebin.com/wilimugaku.coffee

I put 12001 on 1 server 12002 on an other 12003 on an other ...

OliverUv commented

If you set JSONAPI to use port X, it will also use port X+1 and X+2 (for websockets and pure sockets connections.) Try setting 12001 and 12010 and 12020 instead.