Follow-up to DNS resolution fails inside app (part 3). The error is back since yesterday:
Get "https://ola.prod.code.seat.cloud.vwgroup.com/v2/users/.../garage/vehicles": dial tcp: lookup ola.prod.code.seat.cloud.vwgroup.com on [fdaa::3]:53: server misbehaving
We didn’t do any changes on application side, re-deploying has not fixed the issue.
looking at this, thanks for the report!
@andig I poked at the DNS server and I don’t see errors from your app anymore - is it working again?
It was there this morning after re-deploy (more than once) but not ATM. I’ll update here if I see it again. Thank you for the super quick response!
It has happened again, about an hour ago:
"UNKNOWN:Error received from peer {grpc_message:"cannot create vehicle type 'cupra': cannot get vehicles: Get "https://ola.prod.code.seat.cloud.vwgroup.com/v2/users/xxuseridxx/garage/vehicles\": dial tcp: lookup ola.prod.code.seat.cloud.vwgroup.com on [fdaa::3]:53: server misbehaving", grpc_status:2, created_time:"2025-02-01T20:54:14.316488534+01:00"}"
I’m also seing this in the log which is unexpected:
2025-02-01T20:02:02Z proxy[e784961b297338] ams [error][PP02] could not proxy TCP data to/from instance: failed to copy (direction=server->client, op=shutdown_write, error=Transport endpoint is not connected (os error 107))
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.