Response "message":"We're sorry, but something went wrong."
A
Adarsh Sukumaran
started a topic
about 3 years ago
Hi,
Everything was working fine. But suddenly i started getting this response "message":"We're sorry, but something went wrong.". Where would be the problem and how it can be figured out. Please suggest a solution if anyone has faced this issue.
This is the complete form of error:
Error, HTTP Status Code : 500
Headers are HTTP/1.1 500 Internal Server Error
Cache-Control: no-cache, no-store, max-age=0, must-revalidate
Content-Type: application/json; charset=utf-8
Date: Fri, 25 Nov 2016 07:08:28 GMT
Expires: Wed, 13 Oct 2010 00:00:00 UTC
Pragma: no-cache
Set-Cookie: _x_w=19; path=/
Status: 500 Internal Server Error
X-Freshdesk-API-Version: latest=v2; requested=v2
X-Rack-Cache: invalidate, pass
X-RateLimit-Remaining: 4998
X-RateLimit-Total: 5000
X-RateLimit-Used-CurrentRequest: 1
X-Request-Id: 8502dc9a964ad29b7568abb0e788398c
Content-Length: 52
Connection: keep-aliveResponse are {"message":"We're sorry, but something went wrong."}
Thanks in advance.
1 person has this problem
Rohit Eddy
said
almost 3 years ago
Can you please let us know in which scenario or while using which feature does this error occur?
Adarsh Sukumaran
Hi,
Everything was working fine. But suddenly i started getting this response "message":"We're sorry, but something went wrong.". Where would be the problem and how it can be figured out. Please suggest a solution if anyone has faced this issue.
This is the complete form of error:
Error, HTTP Status Code : 500 Headers are HTTP/1.1 500 Internal Server Error Cache-Control: no-cache, no-store, max-age=0, must-revalidate Content-Type: application/json; charset=utf-8 Date: Fri, 25 Nov 2016 07:08:28 GMT Expires: Wed, 13 Oct 2010 00:00:00 UTC Pragma: no-cache Set-Cookie: _x_w=19; path=/ Status: 500 Internal Server Error X-Freshdesk-API-Version: latest=v2; requested=v2 X-Rack-Cache: invalidate, pass X-RateLimit-Remaining: 4998 X-RateLimit-Total: 5000 X-RateLimit-Used-CurrentRequest: 1 X-Request-Id: 8502dc9a964ad29b7568abb0e788398c Content-Length: 52 Connection: keep-aliveResponse are {"message":"We're sorry, but something went wrong."}
Thanks in advance.
1 person has this problem