Membre
Nbr msg: 1
Enregistré: 11/01/2012
|
Ecrit le: 01/04/2019 19:00
|
|
|
Would appear the same across all servers, and it only started when trying to add the new TLP's.
An error occurred when synchronizing the characters: null
|
|
|
Admin
Nbr msg: 11520
Enregistré: 05/05/2001
|
Ecrit le: 02/04/2019 00:15
|
|
|
Hmm what is going now Let me dig into it and get back to you.
|
|
|
Membre
Nbr msg: 5
Enregistré: 02/06/2010
|
Ecrit le: 02/04/2019 01:57
|
|
|
Thanks Jelan
|
|
|
Admin
Nbr msg: 11520
Enregistré: 05/05/2001
|
Ecrit le: 02/04/2019 02:53
|
|
|
Fixed, another stupid mistake on my side...
|
|
|
Membre
Nbr msg: 7
Enregistré: 13/08/2012
|
Ecrit le: 02/04/2019 03:00
|
|
|
Unfortunately no. Still unable to sync from Mangler.
|
|
|
Membre Premium
Nbr msg: 2
Enregistré: 20/10/2004
|
Ecrit le: 02/04/2019 03:56
|
|
|
Seem to be working for me now. Thanks!
|
|
|
Membre
Nbr msg: 97
Enregistré: 20/04/2011
|
Ecrit le: 02/04/2019 04:32
|
|
|
Works for me, but I'm not on Mangler. Thanks!
|
|
|
Membre Premium
Nbr msg: 21
Enregistré: 31/10/2013
|
Ecrit le: 02/04/2019 05:20
|
|
|
Still Unable to retrieve character status, on trying to Sync a Mangler character.
|
|
|
Membre
Nbr msg: 5
Enregistré: 02/06/2010
|
Ecrit le: 02/04/2019 14:36
|
|
|
Still not working on Selos
|
|
|
Membre
Nbr msg: 7
Enregistré: 09/04/2011
|
Ecrit le: 02/04/2019 23:59
|
|
|
Also just tried on Mangler and still a no go.
|
|
|
Admin
Nbr msg: 11520
Enregistré: 05/05/2001
|
Ecrit le: 03/04/2019 04:45
|
|
|
I fixed an issue with Mangler but I am surprised it does not work with Selos already.
|
|
|
Membre
Nbr msg: 7
Enregistré: 09/04/2011
|
Ecrit le: 03/04/2019 05:02
|
|
|
Just tried on Mangler and is working now. Thanks.
|
|
|
Membre
Nbr msg: 97
Enregistré: 20/04/2011
|
Ecrit le: 04/04/2019 05:46
|
|
|
Hi Jelan. If you take a look over at the rankings, not a single player is listed for Selo. I just now created a character and tried to sync it. I received the message "Unable to retrieve character's status."
This is a shot in the dark, but is the server case-sensitive? On sync, Selo is not capitalized.
Also, on the site, it's showing up as Selos instead of Selo. Perhaps the typo is affecting it?
In any event, here's the error log:
[20:55:27] [SEVERE] Unable to retrieve character's status.
magelo.aZ:
Apr 03, 2019 8:55:28 PM magelo.ky a
WARNING: An exception due to the connection occurred, a lockdown will be initiated.
magelo.mU: 404 page not found
at magelo.kz.b(kz.java:19)
at magelo.ky.a(ky.java:7)
at magelo.kE.run(kE.java:15)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: java.io.FileNotFoundException: https://sentry.magelo.com/api/2/store/
at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(Unknown Source)
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source)
at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(Unknown Source)
at magelo.kz.b(kz.java:2)
... 5 more
Apr 03, 2019 8:55:28 PM magelo.kE run
SEVERE: An exception occurred while sending the event to Sentry.
magelo.mU: 404 page not found
at magelo.kz.b(kz.java:19)
at magelo.ky.a(ky.java:7)
at magelo.kE.run(kE.java:15)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: java.io.FileNotFoundException: https://sentry.magelo.com/api/2/store/
at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(Unknown Source)
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source)
at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(Unknown Source)
at magelo.kz.b(kz.java:2)
... 5 more
|
|
|
Membre
Nbr msg: 5
Enregistré: 26/05/2003
|
Ecrit le: 05/04/2019 02:17
|
|
|
Still not working. Can we please make this a priority? These servers have been out for nearly 3 weeks now and it still won't sync with Selo....
|
|
|
Admin
Nbr msg: 11520
Enregistré: 05/05/2001
|
Ecrit le: 05/04/2019 07:07
|
|
|
Should be finally fixed for Selo now. Stupid issue again, I used 'selos' instead of 'selo' for the server name...
|
|
|