Getting host error while creating function in portal

Question

Hello,

I'm trying to create a normal function in function app but I'm getting host error not sure why.

Can you please help me.

It is Linux function app
Lang - Python 3.11

Answer 1

Hi TechnoPy,

Thanks for reaching out to Microsoft Q&A.

The error you're seeing, Failed to create nethttp: Encountered an error (InternalServerError) from host runtime, typically indicates an issue with the function app runtime environment, possibly due to configuration, platform limitations, or a transient issue.

Here are some troubleshooting steps to consider:

Check Function App Settings: Go to the Configuration settings of your Function App to verify that all settings are correctly defined. Missing or misconfigured settings might cause the host runtime to fail.

• Review Application Insights and Logs:
  • If Application Insights is enabled, check the logs for more detailed error messages.
  • In the Log Stream (found in the Function App's Monitoring section), you might find additional details on the issue causing the InternalServerError.
• Check Storage Account Configuration:
  • Ensure that the associated storage account is accessible and configured correctly. Function Apps rely on a storage account to manage runtime state, and any connectivity issue with the storage can lead to errors.
• Verify Resource Availability and Quotas:
  • Confirm that you have not reached any service quotas, such as regional vCPU core limits, especially if this issue started after provisioning or account upgrades. (This could be related to recent quota changes after your trial upgrade).
• Restart the Function App: Sometimes, restarting the Function App clears temporary issues. Use the Restart button on the portal and attempt to create the function again.
• Try Another Region: If possible, try deploying a new Function App in a different region to see if this issue is region-specific, which may indicate a temporary service issue.

If none of these steps resolve the issue, it might be necessary to contact Azure Support, as they can investigate backend logs for more specific root causes.

Please feel free to click the 'Upvote' (Thumbs-up) button and 'Accept as Answer'. This helps the community by allowing others with similar queries to easily find the solution.