Hello Rakhi!
ON that issue, it happens when your web server proxy is blocking the
uploads for nginx, add this
*location ^~ /server/ { proxy_pass http://127.0.0.1:8080
<http://127.0.0.1:8080>; proxy_http_version 1.1;
client_max_body_size 512M; proxy_set_header Host
$host; proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto https; proxy_set_header
Connection ""; proxy_buffering off;
proxy_read_timeout 300; }*
In your backend proxy.
For Apache, use :
*# Enable required modules:*
*# a2enmod proxy proxy_http headers*
*<Location "/server/">*
* ProxyPass "http://127.0.0.1:8080/ <http://127.0.0.1:8080/>"*
* ProxyPassReverse "http://127.0.0.1:8080/ <http://127.0.0.1:8080/>"*
* # Allow large uploads (512 MB)*
* LimitRequestBody 536870912*
* # Forward original host*
* ProxyPreserveHost On*
* # Forward client IP information*
* RequestHeader set X-Real-IP "%{REMOTE_ADDR}s"*
* RequestHeader set X-Forwarded-For "%{REMOTE_ADDR}s"*
* RequestHeader set X-Forwarded-Proto "https"*
* # Disable proxy buffering equivalent*
* SetEnv proxy-sendcl 1*
* # Increase backend timeout*
* ProxyTimeout 300*
*</Location>*
Cheers,
Kevon
On Mon, Jun 22, 2026 at 10:02 PM Rakhi Dhibar <[email protected]>
wrote:
> Hello All Dspace Tech,
>
> I am facing a persistent issue with DSpace-CRIS 2025.02.00 where file
> uploads and item deposits are repeatedly failing during the submission
> process.
>
> Environment Details
>
> DSpace-CRIS Version: 2025.02.00
> Ubuntu Server
> PostgreSQL 16
> Tomcat 10
> Solr 9.10.0
> Angular UI running on port 4000
> Problem Description
> When submitting an item to a Publication collection, the submission form
> loads correctly and metadata can be entered. However:
>
> Uploading a file displays the error:
> "Upload failed"
> Clicking "Save" or "Deposit" displays:
> "There was an unexpected error when saving the item. Refresh the page and
> try again."
> The item metadata is partially stored in the database, but the item is
> never archived.
> Additional Information
>
> Tomcat starts successfully without visible errors.
> REST API returns HTTP 200.
> Solr cores are active.
> Metadata values are stored successfully.
> Submission fails during the final save/deposit stage.
> The UI repeatedly shows "Upload failed" and "Unexpected error when saving
> the item".
> Could anyone advise:
>
> What could cause items to be created but not assigned to an owning
> collection?
> Which logs should be enabled to capture the exact submission/deposit
> exception?
> Are there known issues in DSpace-CRIS 2025.02.00 related to Publication
> submission workflows or UploadStep processing?
> Any guidance would be greatly appreciated.
>
> Thank you.
>
> Best regards,
>
> Rakhi Dhibar
> Research Scholar, Library and Information Science
>
> Rabindra Bharati University, Kolkata-700050, West Bengal
>
>
> --
> All messages to this mailing list should adhere to the Code of Conduct:
> https://lyrasis.org/code-of-conduct/
> ---
> 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 visit
> https://groups.google.com/d/msgid/dspace-tech/d791e18e-f01a-4990-9408-298a223972d5n%40googlegroups.com
> <https://groups.google.com/d/msgid/dspace-tech/d791e18e-f01a-4990-9408-298a223972d5n%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
--
All messages to this mailing list should adhere to the Code of Conduct:
https://lyrasis.org/code-of-conduct/
---
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 visit
https://groups.google.com/d/msgid/dspace-tech/CA%2BLKazrrr5dauMirNuWERUEULRcpken%3DBV05TzBVZQH7YcNBiw%40mail.gmail.com.
