We have clients in the middle east who are currently hosted in Europe. This causes high latency which would be solved by hosting in UAE.1 vote
It can be extremely frustrating when an isolated ASE fails to deploy if the only error log says "The resource provision operation did not complete within the allowed timeout period. "
There are a number of forum threads, blogs, etc. that discuss what to possibly check when this error is thrown.
I think it could just do better. If there are requirements to communicate with some management IP during creation and it can't then that should be in the error log.1 vote
Log event that service plan can not handle all web apps instead killing biggest app in a loop without proper information
After spending 8+ hours debugging why Linux Web app is restarting (case: 119061321000317) I would like you to fix logging for web app plan - if Service plan cannot accomodate web apps contained in a plan - please log that health check killed biggest app in a plan and not logging "unhelthy" state.1 vote
After Domain Transfer to Azure App Service Domain, there should be a way to check the Status of the transfer.
After Domain Transfer to Azure App Service Domain, there should be a way to check the Status of the transfer.1 vote
I want to have the FTP to use Azure AD authentication rather than using the other 2 methods available now (App, User Credentials).1 vote
We've faced a issue of random high CPU in App Service Plan (S1), Azure support says that it is due to internal monitoring. But my suggestion is why to keep app service plan on such low resources that internal monitoring services suck the CPU / Memory resources.
In Short - Microsoft should make the azure internal services to use minimum resources / increase resources for small app service plans such as S1.1 vote
I trying to change the ASE Front End size from Azure portal using CSP Subscription, but Pricing Tier is blank and can not be selected.
I know that it is possible to respond using REST API, Azure PowerShell, etc.
Can I setting on Azure portal in the future ?
Best regards.1 vote
We can see that there are multiple bugs in App Service Environment - Issues with "VIP type" for Network:
- When we select Internal; There is no validation of Domain Name
- When we select External; it does not provide the IP Address range
- Same issue is observed with new and existing Network1 vote
As Wep App for Container works with a front proxy and as the https traffic incoming on port 443 is redirect as http on port 80, the HTTP Header X-Forwarded-Port should be define as it is on AWS (https://docs.aws.amazon.com/elasticloadbalancing/latest/classic/x-forwarded-headers.html)
As of today, the header is missing and that breaks libs like phpCAS checking for this header through $_SERVER['HTTP_X_FORWARDED_PORT'] to get the current "external" url.1 vote
Currently only Tomcat 8.5, 9.0, Java SE, WildFly 14 (all running JRE 8), are available as linux supported runtimes:
Why Apache TomEE (TomEE plume 7.1.0) is note available since it's java 8 compatible?1 vote
- Don't see your idea?