Thread Details
  • State Verified Answer
  • Replies 3 replies
  • Subscribers 354 subscribers
  • Views 2709 views
  • Users 0 members are here
Forum Actions
Related

Doc Merge not working / cURL Error 3 / 500 Server Error

Martin Neitzke

Hi Devs,

We are currently trying to implement the Doc Merge feature on our on-site instance. When generating a document we get a 500 error on the GUI and in the log (debugging level) the following is thrown:

Tue Mar  5 13:27:17 2024 [2911543][d90f4525-9607-b173-8622-5667ed386d40][DEBUG] Document Merge: client: http: >>>>>>>>
POST /merge HTTP/1.1
Host: 
Content-Length: 651
User-Agent: GuzzleHttp/6.5.5 curl/7.68.0 PHP/8.2.14
Content-Type: application/json

{"mergeType":"convert","use_revision":true,"file_name":"Expert JV 2024","document_id":"9d084cd6-d79c-11ee-a31e-005056833a93","record_id":"da48e8c6-d6fc-11ee-8ba0-005056833a93","record_module":"prg_Programs","mergeRequestId":"b4301856-daeb-11ee-b84e-005056833a93","parent_id":null,"parent_module":null,"max_relate_records_retrieve":20,"metadata_hash":"aad9dc5b0328e97a69a530e92ad357ff","user_prefs_hash":"ea1450bbdcc6a555ee7c5bf4aeecddfd","token":{"access_token":"30547207-6586-4fa5-b826-060ac93910ce","expires_in":3600,"token_type":"bearer","scope":null},"instance_url":"https:\/\/[OURSYSTEM].[OURDOMAIN].de","unique_key":"d78123897ecce777f74af51d2da26ce2"}
<<<<<<<<

--------
cURL error 3:  (see https://curl.haxx.se/libcurl/c/libcurl-errors.html)
Tue Mar  5 13:27:17 2024 [2911543][d90f4525-9607-b173-8622-5667ed386d40][DEBUG] Hook called: ::handle_exception
Tue Mar  5 13:27:17 2024 [2911543][d90f4525-9607-b173-8622-5667ed386d40][ERROR] An exception happened: ( 500: unknown_error)cURL error 3:  (see https://curl.haxx.se/libcurl/c/libcurl-errors.html)

[OURSYSTEM] & [OURSDOMAIN] are placeholder 
SugarCRM ENT 12.0.4 On-Premise
PHP 8.2.14

My current suspicion is that the interaction between GuzzleHttp curl and PHP is generating this error.

The question is: Does anyone have experience with the separate update of the libraries?

Do you have any other opinions or experiences on this subject?

Kind regards.

Martin

AVM GmbH
IT Applications

Parents
  • +1

    We had issues with DocMerge earlier today, when trying it on a new dev server using a copy of a production site.

    We had to make the dev site a real domain.

    We had been "hiding" the dev site from the internet by adding it to our hosts files instead of as a DNS entry.

    But presumably DocMerge servers need to know the IP address of the site to send back to and Sugar sends it the site_url

    We needed to add the IP addresses of the DocMerge servers to our filewall (port 80) and IIS IP restriction module.

    (we set the default doc merge server to eu-west-2 which is London)

    We set the site_url to the dev site, and changed the unique_key.

Reply
  • +1

    We had issues with DocMerge earlier today, when trying it on a new dev server using a copy of a production site.

    We had to make the dev site a real domain.

    We had been "hiding" the dev site from the internet by adding it to our hosts files instead of as a DNS entry.

    But presumably DocMerge servers need to know the IP address of the site to send back to and Sugar sends it the site_url

    We needed to add the IP addresses of the DocMerge servers to our filewall (port 80) and IIS IP restriction module.

    (we set the default doc merge server to eu-west-2 which is London)

    We set the site_url to the dev site, and changed the unique_key.

Children