Docker container ERR_INVALID_CHAR
Opened this issue · 0 comments
peteh commented
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
- Follow instructions to get cookie
- Write cookie into .env file based on example
- Run docker compose build
- Run docker compose up
- Call http://localhost:3000/api/get_limit
- Get error:
suno-api-1 | Error fetching limit: TypeError [ERR_INVALID_CHAR]: Invalid character in header content ["Cookie"]
suno-api-1 | at ClientRequest.setHeader (node:_http_outgoing:662:3)
suno-api-1 | at new ClientRequest (node:_http_client:289:14)
suno-api-1 | at Object.request (node:https:379:10)
suno-api-1 | at M._performRequest (/app/.next/server/chunks/943.js:78:5910)
suno-api-1 | at new M (/app/.next/server/chunks/943.js:78:1369)
suno-api-1 | at Object.value [as request] (/app/.next/server/chunks/943.js:78:1909)
suno-api-1 | at /app/.next/server/chunks/943.js:306:6909
suno-api-1 | at /app/.next/server/chunks/943.js:306:1944
suno-api-1 | at new Promise (<anonymous>)
suno-api-1 | at e9 (/app/.next/server/chunks/943.js:306:1860)
suno-api-1 | at i_.request (/app/.next/server/chunks/943.js:306:20567)
suno-api-1 | at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
suno-api-1 | at async m.getAuthToken (/app/.next/server/app/api/get_limit/route.js:1:3006)
suno-api-1 | at async m.init (/app/.next/server/app/api/get_limit/route.js:1:2866)
suno-api-1 | at async _ (/app/.next/server/app/api/get_limit/route.js:1:6976) {
suno-api-1 | code: 'ERR_INVALID_CHAR'
suno-api-1 | }
Expected behavior
Get correct response for limits
Desktop (please complete the following information):
- OS: Docker on Kubuntu 24.04
- Version: latest master