26
Views
8
Comments
[Ultimate PDF] 405 methos not allowed
ultimate-pdf
Reactive icon
Forge asset by Leonardo Fernandes
Application Type
Reactive

Hi ,

We are facing 405 method not allowed issue in production for some forge component .

E.g :  1.  Ultimate pdf

          2. Add Watermark on pdf


Please find the attached screen shot for your references.




Thanks  in advance !!!

2023-03-13 10-26-05
Sriyamini

Hi @Digvijay Tambe ,

Are these components working fine in DEV and Test environment? Is the issue occurring only in production

Thanks, 

Sriyamini J

UserImage.jpg
Digvijay Tambe

Hi @Sriyamini ,

Yes these component is working fine in dev and test environment. Only we are facing issue in production.


Thanks,

Digvijay Tambe

2021-11-12 04-59-31
Manikandan Sambasivam

Hi,

Please share the detailed integration log from the service center

UserImage.jpg
Digvijay Tambe

Hi @Manikandan Sambasivam ,

There is no any log in integration .I have shared one screen shot from the error log .we are using ultimate pdf forge component.


Thanks,

Digvijay Tambe

UserImage.jpg
Digvijay Tambe

Hi ,


we are adding temporary port 80 listener  rule in between ALB and  NLB it's working fine, but port 80 is not allowed in our organization because port 80 is not secure port. 


Thanks,

Digvijay Tambe

2026-02-16 05-51-10
Sahana K

Hi,
1.Check if the API endpoint in Production allows POST requests.
Some endpoints may have method restrictions in Production.
2.Firewalls or security settings might be blocking requests from the application. 
3.In OutSystems Service Center, go to Monitoring → Errors to get more details. 
4.Manually send a POST request to this endpoint using Postman.


Thanks,
sahana

2020-02-22 10-02-04
Allan Kedari

Hi @Digvijay Tambe

Since port 80 is insecure, I recommend switching to port 443 (HTTPS) for secure communication.

  • Add an HTTPS listener on your ALB with an SSL/TLS certificate.
  • Update your Target Group to use TCP/SSL for encrypted traffic.
  • Optionally, configure a rule in ALB to redirect HTTP to HTTPS.

This approach ensures secure and encrypted data transfer.

Best regards,

Allan Kedari

2019-07-08 11-04-35
Leonardo Fernandes
 
MVP

Hi Digvijay.

The error you posted is a client-side error, so it's likely not at all related to Ultimate PDF.

Based on the name of the action you're calling (AddTextWatermarkInPDF_Memory), you're probably transferring the PDF to the server in order to add the watermark. The error may be caused by a payload that is too large (although an HTTP 413 error would be more appropriate in that case).

In any case, you should check that action and what it does, and test whether the error is correlated to large files, or if it always happens no matter the payload size.

Community GuidelinesBe kind and respectful, give credit to the original source of content, and search for duplicates before posting.