Troubleshooting Gateway Timeout error 504 when provisioning DevTest Lab VM

Michael Meier 0 Reputation points
2023-12-12T23:19:32.4666667+00:00

When provisioning a DevTest Lab VM, I receive the following error frequently:

Error code: GatewayTimeout

Message: The gateway did not receive a response from 'Microsoft.DevTestLab' within the specified time period.

Sometimes it takes 2 more attempts (retries) to successfully provision a VM. This is becoming a major problem and I am looking for a permanent solution. Can anyone offer assistance in troubleshooting this issue?

Azure DevTest Labs
Azure DevTest Labs
An Azure service that is used for provisioning development and test environments.
256 questions
{count} votes

1 answer

Sort by: Most helpful
  1. vipullag-MSFT 24,196 Reputation points Microsoft Employee
    2024-02-13T05:50:53.1366667+00:00

    Hello Michael Meier

    Welcome to Microsoft Q&A Platform, thanks for posting your query here.

    The GatewayTimeout error occurs when the gateway does not receive a response from the backend within the specified time period. This can happen due to a variety of reasons, such as network connectivity issues, high load on the backend, or issues with the DevTest Lab service itself.

    To troubleshoot this issue, you can try the following steps:

    -Check the status of the DevTest Lab service in the Azure portal. If the service is experiencing issues, it may be causing the GatewayTimeout error. You can also check the Azure status page to see if there are any known issues with the service.

    -Check the network connectivity between the DevTest Lab and the backend pool. If there is a network issue, resolve it and try provisioning the VM again.

    -Check the size of the VM that you are trying to provision. If the VM size is too large, try provisioning a smaller VM size.

    -Increase the timeout value for the gateway. You can do this by modifying the Backend Setting for the DevTest Lab service.

    -Try provisioning the VM during off-peak hours when there is less load on the backend.

    If none of these steps resolve the issue, you can submit a support ticket to Microsoft for further assistance as mentioned in the previous comment. I hope this helps!