Jump to content

503 Failed to send server listings


mixli1230
  • Fixed

help pls!


Steps to Reproduce

[00:00:25]: Setting lobby region to default: US
[00:00:25]: Registering master server in US lobby
[00:00:25]: Validating portal[1] <-> <nil>[1] (inactive)        
[00:00:25]: Validating portal[2] <-> <nil>[2] (inactive)        
[00:00:25]: Validating portal[3] <-> <nil>[3] (inactive)        
[00:00:25]: Validating portal[4] <-> <nil>[4] (inactive)        
[00:00:25]: Validating portal[5] <-> <nil>[5] (inactive)        
[00:00:25]: Validating portal[6] <-> <nil>[6] (inactive)        
[00:00:25]: Validating portal[7] <-> <nil>[7] (inactive)        
[00:00:26]: Validating portal[8] <-> <nil>[8] (inactive)        
[00:00:26]: Validating portal[9] <-> <nil>[9] (inactive)        
[00:00:26]: Validating portal[10] <-> <nil>[10] (inactive)      
[00:00:26]: Failed to send server listings
[00:00:26]: Failure error code received: 503
[00:00:26]: With Body: <html>
<head><title>503 Service Temporarily Unavailable</title></head>
<body>
<center><h1>503 Service Temporarily Unavailable</h1></center>
</body>
</html>




User Feedback


A developer has marked this issue as fixed. This means that the issue has been addressed in the current development build and will likely be in the next update.
20 minutes ago, mixli1230 said:

help pls


[00:01:44]: Registering master server in US lobby
[00:01:45]: Failed to send server listings
[00:01:45]: Failure error code received: 503
[00:01:45]: With Body: <html>
<head><title>503 Service Temporarily Unavailable</title></head>
<body>
<center><h1>503 Service Temporarily Unavailable</h1></center>
</body>
</html>

server_log_2022-01-18-21-04-21.txt 18.66 kB · 1 download

 

server_log_2022-01-18-21-04-21.txt 18.66 kB · 1 download

  

Quote

[00:00:25]: Setting lobby region to default: US

This was found in your server log. As a temporary workaround could you add the parameter "-region EU" to your launch options for your dedicated server instance?

Share this comment


Link to comment
Share on other sites

1 minute ago, JesseB_Klei said:

  

This was found in your server log. As a temporary workaround could you add the parameter "-region EU" to your launch options for your dedicated server instance?

tell me how to remove it?

6 minutes ago, JesseB_Klei said:

  

This was found in your server log. As a temporary workaround could you add the parameter "-region EU" to your launch options for your dedicated server instance?

I didn't understand anything, my server just can't register in the lobby, explain why, everything was fine before that!

Share this comment


Link to comment
Share on other sites

Just now, mixli1230 said:

tell me how to remove it?

It is using it automatically and at no error on your part. If you have access to the launch options to the dedicated server instance you are making then adding the additional parameter "-region EU" at the end should resolve the issue for now. We are currently working on making this not be needed. According to your log your current launch options is the string "-conf_dir DST_Overworld" so the goal is to make it read "-conf_dir DST_Overworld -region EU".

  • Like 1

Share this comment


Link to comment
Share on other sites

8 minutes ago, JesseB_Klei said:

It is using it automatically and at no error on your part. If you have access to the launch options to the dedicated server instance you are making then adding the additional parameter "-region EU" at the end should resolve the issue for now. We are currently working on making this not be needed. According to your log your current launch options is the string "-conf_dir DST_Overworld" so the goal is to make it read "-conf_dir DST_Overworld -region EU".

Okay, it worked, but how can I write it there now, since I also have caves?

start.sh

Share this comment


Link to comment
Share on other sites

7 minutes ago, mixli1230 said:

Okay, it worked, but how can I write it there now, since I also have caves?

start.sh 1.44 kB · 0 downloads

This is not something Klei can officially support at this time with custom user setups and scripts. This region launch option is a workaround and it will not be needed once the underlying issue is fully resolved on our end. But to give you a hint of where you could put it look at your run_shared variable or look at the two times screen is being called with all of its launch options.

  • Like 1
  • Thanks 1

Share this comment


Link to comment
Share on other sites



Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×
  • Create New...