VrageRemote - 503 Service Unavailable

Hello Rurido,

Thank you for reaching out to us on the forum regarding this issue, and we sincerely apologize for the delayed response on this thread.

A 503 Service Unavailable response from the VrageRemote endpoint indicates that the Remote API endpoint itself is reachable, but the Remote API service is not available or did not initialize correctly on the dedicated server.

To help us investigate this further, could you please check and confirm a few things for us?

First, please confirm that the Remote API is enabled in the exact configuration file used by the server. The following setting should be present and set to true:

<RemoteApiEnabled>true</RemoteApiEnabled>

If your server is started with a custom -path parameter, please make sure you are editing the configuration file located in that directory rather than the default AppData location.

Next, please confirm whether a Remote API password is set in the configuration file, for example.

<RemoteApiPassword>...</RemoteApiPassword>

If possible, we also recommend testing the endpoint locally from the server machine by accessing

http://127.0.0.1:27017/vrageremote/v1/server/ping

and letting us know whether the response is still a 503 error or if it changes.

Additionally, please share the dedicated server log from a startup where the 503 error occurs. If you notice any log entries related to VrageRemote, the Remote API, or HTTP services during startup, that information would also be helpful.

Finally, could you let us know whether the server is running locally on your own machine or on a hosting provider?

As a temporary workaround, we recommend restarting the dedicated server after confirming that the Remote API is enabled in the correct configuration file, as configuration changes require a server restart to take effect.

This information will help us determine whether the Remote API service is failing to initialize, being blocked by configuration, or affected by the server environment.

Kind Regards,

Keen Software House: QA Department

Hello, thank you for your detailed reply.

The mentioned part in the configuration file at %appdata%\SpaceEngineersDedicated\SpaceEngineers-Dedicated.cfg looks as follows:

<RemoteApiEnabled>true</RemoteApiEnabled>

<RemoteSecurityKey>SomeBase64EncodedString==</RemoteSecurityKey>

<RemoteApiPort>27017</RemoteApiPort>

<RemoteApiIP />

I don't remember setting a custom path variable: I start the server by launching the GUI at C:\SteamCMD\steamapps\common\SpaceEngineersDedicatedServer\DedicatedServer64\SpaceEngineersDedicated.exe without any parameters and as administrator. Then I select Local / Console. In the configuration window Enable Remote API is checked and Port/Security Key are filled. Finally I hit Save & Start and wait for the log message "Game ready...". The log message "Remote Server Listener started. Listening on port 27017" also appears right after starting the server.

I attached the log of a Start -> Game Ready -> API Ping (failed with 503) -> Stop, but other than the first message, I couldn't see anything related to the API. I also did this for a clean instance (named "Test") without mods and a new world. Still the same 503 error - this is the other attached log file.

The server is running on a virtual machine with Windows 2025 Datacenter (24H2, German language pack, administrator user). I also added the urlacl via netsh (from the AllowRemoteHttp.bat file), though I had to modify the command because simply executing the file failed.

Please let me know if you need any other information or if there are any steps to debug this issue. I also tried to attach dnSpy to the active server process, but I couldn't find where the remote api is initialized, maybe you can point me in the right direction here?

Thank you and best regards, Rurido.