Share via

An attempt was made to access a socket in a way forbidden by its access permissions

  • Article

Question

Thursday, September 19, 2019 11:01 AM

Hi,

So I have this API running on Azure in a virtual network, exposed via a APIM but it suddenly stopped working (internal server error). Looking into the trace the following error message is shown:

[Unable to connect to the remote server","Error occured while calling backend service.","An attempt was made to access a socket in a way forbidden by its access permissions 10.240.0.6:8080"]

The IP address is the service's IP in the virtual network.

If I SSH in a pod in the same virtual network I can still curl that address correctly, so I think the problem lies somewhere in the settings of the APIM, but I can't find anything that seems wrong (althought that could be due to my inexperience)

Any tips I can look into or do you need more information?

Cheers

All replies (1)

Thursday, September 19, 2019 12:44 PM âś…Answered

Found the problem: Due to a failed update to the APIM, the virtual network was removed from it. Re-adding the virtual network solved the problem.