Fixing 400 HTTP errors when using HTTP instead of HTTPS
In this tutorial you will learn how to fix 400 HTTP errors which usually occur when HTTPS is enabled and the client is using HTTP instead, which causes the client to skip the request body entirely for
Introduction
400 Client Error: Bad Request for url: https://your-sly-instance-domain/public/api/v3/ecosystem.file.download{
"level": "warn",
"message": "TASK_END",
"fields": {
"exit_status": "400 Client Error: Bad Request for url: https://your-sly-instance-domain/api/v3/ecosystem.file.download ({\"error\":\"Validation error\",\"details\":[{\"message\":\"\\\"moduleId\\\" is required\",\"path\":[\"moduleId\"],\"type\":\"any.required\",\"context\":{\"key\":\"moduleId\",\"label\":\"moduleId\"}},{\"message\":\"\\\"value\\\" must contain at least one of [filePath, isArchive]\",\"path\":[],\"type\":\"object.missing\",\"context\":{\"peers\":[\"filePath\",\"isArchive\"],\"peersWithLabels\":[\"filePath\",\"isArchive\"],\"label\":\"value\"}}]})"
},
"timestamp": "2023-10-04T08:12:42.922Z",
"task_id": 79
}Changing Server Address Using UI

Changing Server Address Using Terminal
Last updated