The underlying connection was closed: An unexpected error occurred on a receive / Send

Clearance and Reporting
1

Hello ZATCA Team,

Today we started facing issue while clearance and reporting with an error “The underlying connection was closed: An unexpected error occurred on a receive / Send”

Can someone confirm if they have similar issue?

2

@idaoud please fix it

3

we have the same issue, but I noticed it happens only with simplified invoices

4

we have issue

Message : cURL error 56: OpenSSL SSL_read: Connection reset by peer, errno 104 (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://gw-fatoora.zatca.gov.sa/e-invoicing/core/invoices/clearance/single
5

Dears @salman , @mekhlafy , @ahmadOsama , @azeem.chisty

Thanks for reaching out,

Kindly check the below announcement, and confirm if you are still facing the same response.
Important Breaking Change (decommissioning gw-apic-gov.gazt.gov.sa) - Announcements - Fatoora Developer Community

Thanks,
Ibrahem Daoud.

6

we’re using this endpoint https://gw-fatoora.zatca.gov.sa/e-invoicing/core

7

Dear @idaoud ,

We have been using the gw-fatoora.zatca.gov.sa, issue started today afternoon.

8

Dear @idaoud
we are using https://gw-fatoora.zatca.gov.sa/

9

When the invoice is simplified only the issue is happening and we don’t get a response. but if the invoice is tax invoice is success

10

@All

Thanks for your reply.

Please note that our team is currently working on it, will let you know once it resolve will reach out to you, Main while Kindly re-submit your invoices .

Thanks for your understanding.

Ibrahem Daoud.

2 Likes
11

Appreciate your turn around

12

@idaoud

Looks good now

Thanks for the support

1 Like
13

Customers are still reporting the issue, could you please confirm.

14

Our clients also reporting this issue. please take actions.

15

We also have the same issue but can “assure” you guys that this issue is happening since long time. We are just marking the document as FAILED and allowing the user to re-report it. But I agree that it is causing the frustration…

Based on the network error, it seems it is happening when the underlying ZATCA service is deployed (like new version rolled), in this case the “current” requests should be processed and only then obsolete servers should be discarded. It seems that the timeout is quiet short and therefore the connection is getting dropped.

I do not know the infrastructure of ZATCA, but if it is Kubernetes or any other “containers” which are spawned and then halted - then it is the most probable reason.

Please note that we have the same error for both: invoices and simplified invoices.

Also we have a lot of “timeout” issues

Connection to gw-fatoora.zatca.gov.sa timed out. (connect timeout=10)

I know that timeout is quiet small (10 seconds) but we cannot afford our workers to wait for longer due to the volume.