Wasp•4w ago

Payload Too Large?

[ Server!] PayloadTooLargeError: request entity too large [ Server!] at readStream (/mnt/d/TRANSL8 WASP/Transl8/app/.wasp/out/server/node_modules/raw-body/index.js:163:17) [ Server!] at getRawBody (/mnt/d/TRANSL8 WASP/Transl8/app/.wasp/out/server/node_modules/raw-body/index.js:116:12) [ Server!] at read (/mnt/d/TRANSL8 WASP/Transl8/app/.wasp/out/server/node_modules/body-parser/lib/read.js:79:3) [ Server!] at jsonParser (/mnt/d/TRANSL8 WASP/Transl8/app/.wasp/out/server/node_modules/body-parser/lib/types/json.js:138:5)
[ Server!] at Layer.handle [as handle_request] (/mnt/d/TRANSL8 WASP/Transl8/app/.wasp/out/server/node_modules/express/lib/router/layer.js:95:5) [ Server!] at trim_prefix (/mnt/d/TRANSL8 WASP/Transl8/app/.wasp/out/server/node_modules/express/lib/router/index.js:328:13)
[ Server!] at /mnt/d/TRANSL8 WASP/Transl8/app/.wasp/out/server/node_modules/express/lib/router/index.js:286:9 [ Server!] at Function.process_params (/mnt/d/TRANSL8 WASP/Transl8/app/.wasp/out/server/node_modules/express/lib/router/index.js:346:12) [ Server!] at next (/mnt/d/TRANSL8 WASP/Transl8/app/.wasp/out/server/node_modules/express/lib/router/index.js:280:10) [ Server!] at logger (/mnt/d/TRANSL8 WASP/Transl8/app/.wasp/out/server/node_modules/morgan/index.js:144:5) How could I fix this? I tried a bit from older questions but couldn't make it work on videos on my end (or larger images), on localhost.

8 Replies

kapa.ai•4w ago

Hi @lazi. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave: ---------------------- Based on the error message you've provided, it appears you're encountering a "Payload Too Large" error when trying to upload large files (videos or larger images) to your Wasp application running on localhost. This error occurs when the size of the request body exceeds the limit set by the server. To fix this issue in a Wasp application, you can try the following approach: 1. Use the apiMiddleware to configure the body-parser limits. 2. Implement a file upload solution using multer, which is better suited for handling large file uploads. Here's an example of how you can modify your Wasp application to handle larger file uploads:

import { MiddlewareConfigFn } from '@wasp/middleware';
import multer from 'multer';

export const apiMiddleware: MiddlewareConfigFn = (config) => {
  const upload = multer();

  config.set('multer', upload.single('file'));
  config.update('json', { limit: '50mb' });
  config.update('urlencoded', { limit: '50mb', extended: true });
};

import { MiddlewareConfigFn } from '@wasp/middleware';
import multer from 'multer';

export const apiMiddleware: MiddlewareConfigFn = (config) => {
  const upload = multer();

  config.set('multer', upload.single('file'));
  config.update('json', { limit: '50mb' });
  config.update('urlencoded', { limit: '50mb', extended: true });
};

This code snippet is based on the solution provided in the API can't handle FormData GitHub issue. In this configuration: - We're using multer to handle file uploads. - We're increasing the limit for JSON and URL-encoded payloads to 50MB. You'll need to adjust these limits based on your specific requirements. Remember to install the multer package in your project:

npm install multer

npm install multer

After making these changes, restart your Wasp application and try uploading your large files again. If you're still encountering issues or need more specific guidance, you might want to provide more details about your Wasp application setup and the specific file upload implementation you're using. ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ---------------------- Sorry @lazi, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist: Perhaps try again in 15mins?

Vinny (@Wasp)•4w ago

hey @lazi I did a similar thing recently without using multer. In a server setup function:

import type { MiddlewareConfigFn } from 'wasp/server';

import express from 'express';

export const serverMiddlewareFn: MiddlewareConfigFn = (middlewareConfig) => {
  middlewareConfig.set('express.json', express.json({ limit: '50mb' }));
  return middlewareConfig;
};

import type { MiddlewareConfigFn } from 'wasp/server';

import express from 'express';

export const serverMiddlewareFn: MiddlewareConfigFn = (middlewareConfig) => {
  middlewareConfig.set('express.json', express.json({ limit: '50mb' }));
  return middlewareConfig;
};

then in main.wasp:

app YourApp {

//....

  server: {
    middlewareConfigFn: import { serverMiddlewareFn } from "@src/server/serverSetup",
  },

//....

}

app YourApp {

//....

  server: {
    middlewareConfigFn: import { serverMiddlewareFn } from "@src/server/serverSetup",
  },

//....

}

laziOP•4w ago

I tried this approach more or less but didn't get it to work properly - i finally went with just setting up an AWS S3 bucket and using the file-upload functionalities included in OpenSaaS anyway 😄 Thank you @Vinny (@Wasp) ! @kapa.ai app/.wasp/out/web-app: removeDirectoryRecursive:removeContentsRecursive:removePathRecursive:removeContentsRecursive:removeDirectory: permission denied (Permission denied) Any idea on this? I'm using Cursor and WSL

kapa.ai•4w ago

Let me check the knowledge base for you again. One moment! :books: ---------------------- Based on the error message you've provided and the information that you're using Cursor and WSL (Windows Subsystem for Linux), it appears you're encountering a permission issue when Wasp is trying to remove a directory. This is likely related to file system permissions in your WSL environment. The error suggests that Wasp doesn't have the necessary permissions to remove the .wasp/out/web-app directory. This issue is often encountered when working with WSL, especially if the project is located on the Windows file system rather than the Linux file system within WSL. To address this issue, you can try the following solutions: 1. Ensure your project is on the Linux file system: As mentioned in the Wasp Quick Start documentation, there's a caution note for WSL2 users: "If you are using WSL2, make sure that your Wasp project is not on the Windows file system, but instead on the Linux file system. Otherwise, Wasp won't be able to detect file changes, due to the issue in WSL2." This same issue can cause permission problems like the one you're experiencing. 2. Change ownership of the project directory: If your project is already on the Linux file system, you might need to change the ownership of the project directory. You can do this by running the following command in your WSL terminal:

   sudo chown -R $(whoami) /path/to/your/project

   sudo chown -R $(whoami) /path/to/your/project

Replace /path/to/your/project with the actual path to your Wasp project. 3. Run Wasp with sudo: As a last resort, you could try running Wasp commands with sudo. However, this is not recommended as a long-term solution:

   sudo wasp start

   sudo wasp start

If you continue to face issues, you might want to check out the guide for Windows development with Wasp using WSL. This guide provides step-by-step instructions for setting up a proper development environment for Wasp on Windows using WSL. Remember, it's crucial to ensure your project is on the Linux file system within WSL, not on the Windows file system, to avoid various issues including file permissions and change detection problems. ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ---------------------- Sorry @lazi, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist: Perhaps try again in 15mins?

laziOP•4w ago

@kapa.ai $ sudo wasp start sudo: wasp: command not found

kapa.ai•4w ago

Let me check the knowledge base for you again. One moment! :books: ---------------------- Based on the error message you're seeing, it appears that the wasp command is not recognized when using sudo. This is likely because the wasp executable is not in the system-wide PATH that sudo uses. To resolve this issue, you have a few options: 1. Use the full path to the wasp executable: First, find out where wasp is installed by running which wasp in your terminal. Then use the full path with sudo:

   sudo /path/to/wasp start

   sudo /path/to/wasp start

2. Add Wasp to your PATH: This is a more permanent solution. You need to add the directory containing the wasp executable to your PATH. Here's how you can do it: a. Open your shell configuration file (e.g., ~/.bashrc or ~/.zshrc) in a text editor. b. Add the following line at the end of the file:

      export PATH="$HOME/.local/bin:$PATH"

      export PATH="$HOME/.local/bin:$PATH"

c. Save the file and reload your shell configuration with source ~/.bashrc (or ~/.zshrc). This solution is based on the Github issue about Wasp install location not being on PATH. 3. Use sudo -E: The -E flag tells sudo to preserve the user's environment variables, including PATH:

   sudo -E wasp start

   sudo -E wasp start

However, it's important to note that running Wasp with sudo is not recommended as a long-term solution. It's better to resolve the underlying permission issues that are causing you to need sudo in the first place. If you're using WSL, make sure your Wasp project is on the Linux file system, not the Windows file system. This can help avoid permission issues. You can find more information about this in the Wasp guide for Windows development using WSL. If you continue to face issues, you might want to consider reinstalling Wasp to ensure it's properly set up in your environment. ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ---------------------- Sorry @lazi, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist: Perhaps try again in 15mins?

laziOP•4w ago

Nevermind me Kapa, good bot. It was yet again an environment issue on my end - some Docker conflict now. Fixed with an actual PC restart (which was due for some time)

Vinny (@Wasp)•4w ago

ok nice. glad you're getting things working @lazi

Gaming

Programming

Payload Too Large?

Did you find this page helpful?