*TLDR; Behind NGINX proxy? Add client_max_body_size 512M; to your server block.*
This one may seem obvious to some, but it is easy to overlook. I was getting errors in my console that were completely misleading: [Error] Origin https://my-dpace-angular-ui is not allowed by Access-Control-Allow-Origin. Status code: 413 [Error] XMLHttpRequest cannot load https://my-dspace-restapi/server/api/core/bundles/083ff9dd-4ef7-49ff-8ba8-8184e7e5b08a/bitstreams due to access control checks. [Error] Failed to load resource: Origin https://my-dspace-angula-rui is not allowed by Access-Control-Allow-Origin. Status code: 413 (bitstreams, line 0) Okay, so this must be a problem with CORS, right? Check local.cfg... rest.cors.allowed-origins = ${dspace.ui.url} What gives? Check everywhere else the CORS might be set: sh /dspace/bin/beginwildgoosechase.sh grep -rl "cors.allowed" #find everywhere there is cors setting, etc. Fast forward to a discovery that I can only upload files under 1mb. It must be some issue with Tomcat, so I check /dspace/webapps/server/WEB-INF/classes/application.properties > spring.servlet.multipart.max-file-size = 512mb Maybe it only accepts byte sizes? Restart tomcat... still doesn't work. Wait! Tomcat is behind an Nginx proxy: Add "client_max_body_size 200M;" to the server block of my site configuration. FINALLY! -- All messages to this mailing list should adhere to the Code of Conduct: https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx --- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/8359722f-41b5-48dd-a4b9-cf4c21777ba2n%40googlegroups.com.
