# simpleTextQuery error

**URL:** <https://community.crossref.org/t/simpletextquery-error/14116>\
**Category:** Content Registration\
**Tags:** content-registration, bug, deposit\_support, simple\_text\_query\
**Created:** [10 July 2025 18:06 UTC](https://community.crossref.org/t/simpletextquery-error/14116 "2025-07-10T18:06:14Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Luis\_Aviles](https://avatars.discourse-cdn.com/v4/letter/l/f1d935/32.png) [@Luis\_Aviles](https://community.crossref.org/u/Luis_Aviles)\
**Post date:** [10 July 2025 18:06 UTC](https://community.crossref.org/t/simpletextquery-error/14116/1 "2025-07-10T18:06:14Z")

</div>

Dear Colleagues:

I have tried to register the citations of an article by means of _Simple Text Query form_ but when I click on _Deposit_ I get the following error message.

> Cita

# Estado HTTP 500 – Internal Server Error

* * *

**Tipo** Informe de Excepción

**mensaje** Handler processing failed; nested exception is java.lang.Error: HTTPClient Internal Error: unexpected exception ‘HTTPClient.ProtocolNotSuppException: Unsupported protocol ‘https’’

**Descripción** El servidor encontró un error interno que hizo que no pudiera rellenar este requerimiento.

**excepción**

org.springframework.web.util.NestedServletException: Handler processing failed; nested exception is java.lang.Error: HTTPClient Internal Error: unexpected exception ‘HTTPClient.ProtocolNotSuppException: Unsupported protocol ‘https’’ org.springframework.web.servlet.DispatcherServlet.triggerAfterCompletionWithError(DispatcherServlet.java:1260) org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:939) org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:851) org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:953) org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:855) javax.servlet.http.HttpServlet.service(HttpServlet.java:555) org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:829) javax.servlet.http.HttpServlet.service(HttpServlet.java:623) org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:51) org.crossref.common.servlet.RequestCaptureFilter.doFilter(RequestCaptureFilter.java:139)

**causa raíz**

java.lang.Error: HTTPClient Internal Error: unexpected exception ‘HTTPClient.ProtocolNotSuppException: Unsupported protocol ‘https’’ HTTPClient.RedirectionModule.requestHandler(RedirectionModule.java:161) HTTPClient.HTTPConnection.handleRequest(HTTPConnection.java:2622) HTTPClient.HTTPConnection.setupRequest(HTTPConnection.java:2507) HTTPClient.HTTPConnection.Post(HTTPConnection.java:1050) org.crossref.qs.citedbydepositservice.CitedByDepositService.postCitedByDeposit(CitedByDepositService.java:386) org.crossref.qs.citedbydepositservice.CitedByDepositService.submitCitedByDeposit(CitedByDepositService.java:276) org.crossref.qs.simpletextquery.SimpleTextQueryController.handleRequest(SimpleTextQueryController.java:222) org.springframework.web.servlet.mvc.SimpleControllerHandlerAdapter.handle(SimpleControllerHandlerAdapter.java:48) org.crossref.common.spring.servlet.CrossRefDispatcherServlet$1.handle(CrossRefDispatcherServlet.java:140) org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:919) org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:851) org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:953) org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:855) javax.servlet.http.HttpServlet.service(HttpServlet.java:555) org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:829) javax.servlet.http.HttpServlet.service(HttpServlet.java:623) org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:51) org.crossref.common.servlet.RequestCaptureFilter.doFilter(RequestCaptureFilter.java:139)

**nota** La traza completa de la causa de este error se encuentra en los archivos de registro del servidor.

Is this an error due to the update? Do I have to wait before I can register references?

---

<div class="post-metadata">

**Author:** ![ifarley](https://sea2.discourse-cdn.com/flex020/user_avatar/community.crossref.org/ifarley/32/44_2.png) [@ifarley](https://community.crossref.org/u/ifarley)\
**Post date:** [10 July 2025 18:27 UTC](https://community.crossref.org/t/simpletextquery-error/14116/2 "2025-07-10T18:27:37Z")

</div>

Hi @Luis_Aviles ,

Thanks for flagging this to us. I am getting a slightly different error when I try to deposit the references myself.

 ![Screenshot 2025-07-10 at 1.19.59 PM](https://us1.discourse-cdn.com/flex020/uploads/crossref/original/2X/1/12bb5209adfb00a1d85484cf18202e84290f83f3.png)

Either way, that error is on our end and is likely related to yesterday’s migration work. I have flagged this to our technical team and they are working on a fix.

-Isaac

---

<div class="post-metadata">

**Author:** ![ifarley](https://sea2.discourse-cdn.com/flex020/user_avatar/community.crossref.org/ifarley/32/44_2.png) [@ifarley](https://community.crossref.org/u/ifarley)\
**Post date:** [11 July 2025 16:15 UTC](https://community.crossref.org/t/simpletextquery-error/14116/3 "2025-07-11T16:15:54Z")

</div>

Hello @Luis_Aviles ,

We have deployed a fix for this error. Please do retry your reference submissions and let us know if you continue to encounter errors.

Warm regards,  
Isaac

---

<div class="post-metadata">

**Author:** ![Luis\_Aviles](https://avatars.discourse-cdn.com/v4/letter/l/f1d935/32.png) [@Luis\_Aviles](https://community.crossref.org/u/Luis_Aviles)\
**Post date:** [11 July 2025 21:00 UTC](https://community.crossref.org/t/simpletextquery-error/14116/4 "2025-07-11T21:00:18Z")

</div>

Hi Isaac,

I was able to register the references without any problem, thank you very much for your support.

However I have noticed another drawback after the upgrade. I am not receiving the notification emails about DOI registration and references. Attached image of the emails that were received before the update.

 ![image](https://us1.discourse-cdn.com/flex020/uploads/crossref/original/2X/a/a8df96432f8477c2a3e196fb84e76b408beee20c.png)  
 ![image](https://us1.discourse-cdn.com/flex020/uploads/crossref/original/2X/b/ba0918da63f19ece97ea4b73948f3a23cc569dd3.png)

Can a new report be submitted or is this function no more in use?

---

<div class="post-metadata">

**Author:** ![ifarley](https://sea2.discourse-cdn.com/flex020/user_avatar/community.crossref.org/ifarley/32/44_2.png) [@ifarley](https://community.crossref.org/u/ifarley)\
**Post date:** [11 July 2025 21:14 UTC](https://community.crossref.org/t/simpletextquery-error/14116/5 "2025-07-11T21:14:23Z")

</div>

Hello @Luis_Aviles ,

We deployed a fix earlier today for those notification emails. We believe that those notifications have been restored, but, unfortunately, there is quite a backlog within the system for all of the submissions that were backlogged there. Our internal logs do suggest that notifications are indeed being sent, but delivery is still delayed. We suspect that the system will catch up over the weekend, but we continue to monitor, as the incident on our status page states: [Crossref Status - Errors present in Metadata Manager and Simple Text Query from registrations, undelivered notification emails after registration](https://status.crossref.org/incidents/scr3rtr8f4pm)

In the meantime, if you didn’t receive a submission log email, you can use the admin tool to search for submission logs for past deposits:

1. Log in to the [admin tool](https://doi.crossref.org/) using your [account credentials](https://www.crossref.org/documentation/member-setup/account-credentials/)
2. Click the _Submissions_ tab, then the _Administration_ sub-tab
3. Click _Search_ at the bottom of the screen, and you’ll see a list of all past deposits for your account, from newest to oldest.
4. Click on the _Submission ID_ number to the left of any deposit to access the _Submission details_, including the submission log for that deposit, or click on the _file_ icon to view the file that was submitted.

Warm regards,  
Isaac
