to get a personalized navigation.
to get a personalized navigation.
Hi
This morning around 08 and yesterday around noon and 18 in the evening we experienced a lot of 502 errors along with connection issues/token expirations on almost all customer companies.
Are you doing any work on your gateway?
This happens on all sorts of actions, both GET, POST and PUT. On integrations that's been running for years.
The 502 error looks like they are happening when there's a lot of load. Even when the actions are retried.
Please check into this as this has severe economical effects on our customers.
Solved! Go to Solution.
Same here ... alot of 502 Proxy error.
Started yesterday with a few, but picked up during the night.
Tested right now 9 requests to /paymentMethods - 2 with success, 7 with 502 error.
We got the same problem here...
Visma, why are your status site status.visma.net reporting everything is Ok when clearly there are active API issues?
We are on it:
this is currently being investigated, further updates will be provided. We're sorry for the inconvenience. https://status.visma.com/incidents/gh9ndhwrmqw5
Update:
The issue has been addressed. This was related to DNS, the issue has been occurred between our proxy servers and endpoint's environment. The problem should now be resolved.
Postmortem will be provided at the status.visma.com
We are sorry for the standstill this may have caused in your integrations.
Please let us know whether you are still facing the problem.
Yes, I get these too
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>502 Proxy Error</title>
</head><body>
<h1>Proxy Error</h1>
<p>The proxy server received an invalid
response from an upstream server.<br />
The proxy server could not handle the request <em><a href="/API/controller/api/v1/customerPayment">GET /API/controller/api/v1/customerPayment</a></em>.<p>
Reason: <strong>DNS lookup failure for: alb.vni.prodaws.visma.com</strong></p></p>
</body></html>
Copyright © 2022 Visma.com. All rights reserved.