Forum

Hello!

As seen in the Runtime Logs from the screenshot, this is an application-level error, not an issue with the Zeabur platform. Please troubleshoot your application settings based on the error message.

Additionally, have you tried using the Zeabur Agent to help resolve this issue?

The Zeabur platform is currently operating normally. Please feel free to ask if you have any other questions!

I didn't set it up manually; it was automatically deployed using a Zeabur template.

In the settings, under configuration, create a file at /data/config.json and copy the content from the config.json in the source code documentation into it.

Thanks for the addition, this step is more specific — indeed, there is a Settings → Configurations shortcut interface on the Zeabur service page where you can directly create files mounted to a Volume path, which is more convenient than going into the Volume file manager.

@595306396 You can follow the method suggested by 伊予柑:

1. Go to the ds2api service page
2. Settings → Configurations
3. Add a new config, set the mount path to /data/config.json
4. Paste the config.json example from the ds2api repository README into the content
5. Save and restart the service

This will automatically write the file to the Volume and mount it into the container, allowing the pod to start normally.

May I ask if this is the correct way to do it?

It has turned into this error.

Hello,

Looking at the screenshot, it seems like the file path is incorrect. It should be /data/config.json, not /ata/config.json.

Please try again, and if you still have issues, feel free to reply.

It still doesn't work, I have already corrected it.

Hello!

According to the logs, the application failed to start because the content of /data/config.json is incorrect. You have currently entered the shell command from the README instead of the actual JSON configuration.

Have you followed the steps replied by Bohan Chen above and copied the content from the ds2api repository's config.example.json example?

Please go to Settings → Configurations, click on /data/config.json, delete all existing content, paste the full JSON content from config.example.json, modify the configuration according to your needs, save it, and then restart the service.