Login / Sign up
> > > Game Update: March 13, 2019


Messages in topic: Game Update: March 13, 2019
Odiiusx
Premium User

Nbr post: 1
Register: 1/10/12
Posted: 4/1/19 1:00 PM

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
Jelan
Admin

Nbr post: 10597
Register: 5/4/01
Posted: 4/1/19 6:15 PM

Hmm what is going now Let me dig into it and get back to you.
mdayriu
Premium User

Nbr post: 5
Register: 6/2/10
Posted: 4/1/19 7:57 PM

Thanks Jelan
Jelan
Admin

Nbr post: 10597
Register: 5/4/01
Posted: 4/1/19 8:53 PM

Fixed, another stupid mistake on my side...
waytjm
Premium User

Nbr post: 4
Register: 8/13/12
Posted: 4/1/19 9:00 PM

Unfortunately no. Still unable to sync from Mangler.
Rrin
Premium User

Nbr post: 2
Register: 10/19/04
Posted: 4/1/19 9:56 PM

Seem to be working for me now. Thanks!
Oxgoad
Premium User

Nbr post: 97
Register: 4/20/11
Posted: 4/1/19 10:32 PM

Works for me, but I'm not on Mangler. Thanks!
zav69
Premium User

Nbr post: 19
Register: 10/31/13
Posted: 4/1/19 11:20 PM

Still Unable to retrieve character status, on trying to Sync a Mangler character.
mdayriu
Premium User

Nbr post: 5
Register: 6/2/10
Posted: 4/2/19 8:36 AM

Still not working on Selos
trox2010
Premium User

Nbr post: 7
Register: 4/9/11
Posted: 4/2/19 5:59 PM

Also just tried on Mangler and still a no go.
Jelan
Admin

Nbr post: 10597
Register: 5/4/01
Posted: 4/2/19 10:45 PM

I fixed an issue with Mangler but I am surprised it does not work with Selos already.
trox2010
Premium User

Nbr post: 7
Register: 4/9/11
Posted: 4/2/19 11:02 PM

Just tried on Mangler and is working now. Thanks.
Oxgoad
Premium User

Nbr post: 97
Register: 4/20/11
Posted: 4/3/19 11:46 PM

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
Camben
Premium User

Nbr post: 5
Register: 5/25/03
Posted: 4/4/19 8:17 PM

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....
Jelan
Admin

Nbr post: 10597
Register: 5/4/01
Posted: 4/5/19 1:07 AM

Should be finally fixed for Selo now. Stupid issue again, I used 'selos' instead of 'selo' for the server name...