Troubleshooting Guide
This guide outlines common deployment and runtime issues encountered in the Teydex KYC project, along with their resolutions.
Access Control Headers
These header necessary for the web application logic and they should be setted for incoming requests. These fields should not be overriden and if these fields will be updated manually, they should be updated without leaving out the following values.
Access-Control-Allow-Headers:
accept, authorization, content-type, user-agent, x-csrftoken, x-requested-with
Access-Control-Allow-Methods:
DELETE, GET, OPTIONS, PATCH, POST, PUT
413 Request Entity Too Large
What is this error?
The 413 Request Entity Too Large error occurs when a client sends a request body that exceeds the maximum size allowed by the web server or proxy. This typically happens during:
- File uploads (images, videos, PDFs, etc.)
- Large JSON payloads or form submissions
NGINX, by default, sets a relatively low limit for request body size, which can block large uploads.
Solution Example (NGINX)
To allow larger requests, you need to increase the client_max_body_size directive in your NGINX configuration.
Step-by-step:
-
Open your NGINX config file
Depending on your system, the config may be in one of the following:
/etc/nginx/nginx.conf/etc/nginx/conf.d/default.conf/etc/nginx/sites-available/your-site
-
Set
client_max_body_sizeInside the
http,server, orlocationblock (based on your setup), add:server {
client_max_body_size 10M;
# ... other config ...
}You can also put it in the
httpblock to apply globally:http {
client_max_body_size 10M;
# ...
} -
Restart NGINX
After saving the file, restart NGINX for changes to take effect:
sudo systemctl restart nginx
Final Notes
- Choose a size that balances user needs and server safety. Typical values range from
5Mto50M. - Always restart NGINX after changes.
- If you're using a reverse proxy like Traefik or Caddy, be sure to update their upload limits as well.