SSH CONN CLOSE Error on Azure App Service

Question

SSH CONN CLOSE Error on Azure App Service

Tomas Mijat 5

I am unable to connect to SSH, and I am unable to connect to the app service.

The container logs just say that the "Conatiner [containerName] for site [siteName] has exited, failing site start". It then processed to an error saying that "Container [containerName] didn't respond to HTTP pings on port: 8080, failing site start. See container logs for debugging."

There is no additional debug and on the containers and deployment actions were successful which which has a build step. The only additional change that was made was to add "clean: true" to the "uses: azure/webapps-deploy@v3" command as per the release notes.
https://github.com/Azure/webapps-deploy/releases/tag/v3.0.0

I have tried restarting the service in an attempt to ssh and run the build command but no success.

ajkuma 28,036 Reputation points Microsoft Employee Moderator

2024-11-15T19:42:25.1966667+00:00

Tomas Mijat, To isolate the issue, you may try the following steps:

Kindly ensure/ update the application code to listen correct port.
Applications deployed to App Service Linux should not be attempting to bind to localhost or 127.0.0.1.

If you’re running a (custom container) with Web App for Containers, use WEBSITES_PORT. Ensure that this is set to the port that’s also exposed in your Dockerfile through the EXPOSE instruction Vs On App Service Linux, using (Blessed Images) - use PORT, which directly influences the container port of the docker run command. See: Whats-the-difference-between-PORT-and-WEBSITES_PORT/index.html

By default, if your container does not respond after 230 seconds, it will time out. (This time out can be increased by with the WEBSITES_CONTAINER_START_TIME_LIMIT app setting.) (up to a maximum of 1800)

Kindly let us know how it goes, I'll follow-up with you further.
Tomas Mijat 5 Reputation points

2024-11-16T07:03:07.22+00:00

Hi Ajkuma,

That is how the application was set up. i.e. the start command was set to listen to the $PORT variable. I did some digging and found that in the \etc\profile file the PORT variable on App Service was set to 8181 but the container was checking port 8080 for activity before shutting down the container. For a different app service for the same code base (prod instance) the App Service on Azure in the same /etc/profile file has the $PORT variable set to 8080.

Because of this the CI/CD pipeline was much harder to manage and we stopped the automatic deployment from GitHub as we also found that after the deployment using azure/webapps-deploy@v3, source files were not in sync i.e. some source code files did not have the updated code despite the deployment status being successful. I had to use FTP to migrate the files across and manage the wwwroot folder.

Would you be able to shed some light on why the PORT variable is different between these 2 app services? Additionally, is there a way with azure/webapps-deploy@v2 (v3 seems to have a number of unresolved breaking issues from the GitHub repo) where all the existing files are removed before the new files are migrated? Currently we zip all the files after GitHub build & test steps are run and then unzip them on the App Service, but it does not seem to be working as some files are not up to date on Azure.

1 answer

Your answer

ajkuma 28,036 Reputation points Microsoft Employee Moderator

2024-11-15T19:42:25.1966667+00:00

Tomas Mijat, To isolate the issue, you may try the following steps:

Kindly ensure/ update the application code to listen correct port.
Applications deployed to App Service Linux should not be attempting to bind to localhost or 127.0.0.1.

If you’re running a (custom container) with Web App for Containers, use WEBSITES_PORT. Ensure that this is set to the port that’s also exposed in your Dockerfile through the EXPOSE instruction Vs On App Service Linux, using (Blessed Images) - use PORT, which directly influences the container port of the docker run command. See: Whats-the-difference-between-PORT-and-WEBSITES_PORT/index.html

By default, if your container does not respond after 230 seconds, it will time out. (This time out can be increased by with the WEBSITES_CONTAINER_START_TIME_LIMIT app setting.) (up to a maximum of 1800)

Kindly let us know how it goes, I'll follow-up with you further.
Tomas Mijat 5 Reputation points

2024-11-16T07:03:07.22+00:00

Hi Ajkuma,

That is how the application was set up. i.e. the start command was set to listen to the $PORT variable. I did some digging and found that in the \etc\profile file the PORT variable on App Service was set to 8181 but the container was checking port 8080 for activity before shutting down the container. For a different app service for the same code base (prod instance) the App Service on Azure in the same /etc/profile file has the $PORT variable set to 8080.

Because of this the CI/CD pipeline was much harder to manage and we stopped the automatic deployment from GitHub as we also found that after the deployment using azure/webapps-deploy@v3, source files were not in sync i.e. some source code files did not have the updated code despite the deployment status being successful. I had to use FTP to migrate the files across and manage the wwwroot folder.

Would you be able to shed some light on why the PORT variable is different between these 2 app services? Additionally, is there a way with azure/webapps-deploy@v2 (v3 seems to have a number of unresolved breaking issues from the GitHub repo) where all the existing files are removed before the new files are migrated? Currently we zip all the files after GitHub build & test steps are run and then unzip them on the App Service, but it does not seem to be working as some files are not up to date on Azure.

Answer 1

The difference in the PORT variable between your two app services could be due to several reasons. Azure App Service typically listens on port 80 for HTTP traffic and port 443 for HTTPS traffic by default. However, for custom containers, the port can be specified using the WEBSITES_PORT environment variable. If this variable is not set, Azure App Service attempts automatic port detection, which might explain why one instance is set to 8181 and another to 8080.

You may explicitly set the WEBSITES_PORT environment variable in your Azure App Service configuration. This can be done using the Azure Portal or the Azure CLI. For example, using the Azure CLI, you can set the port like this:

az webapp config appsettings set --resource-group <resource-group-name> --name <app-name> --settings WEBSITES_PORT=8080

Kindly review the config - Use this option to delete files on the Azure App Service that have no matching files in the App Service package or folder.

RemoveAdditionalFilesFlag - Remove additional files at destination boolean. Optional. Use when UseWebDeploy == true && WebAppKind != linux && WebAppKind != applinux && WebAppKind != "". Default value: false.

Note: This will also remove all files related to any extension installed on this Azure App Service. To prevent this, select the Exclude files from App_Data folder checkbox.

Tomas Mijat 5 Reputation points

2024-11-28T06:20:08.0033333+00:00

Hi, For this comment here,

Kindly review the config - Use this option to delete files on the Azure App Service that have no matching files in the App Service package or folder. RemoveAdditionalFilesFlag - Remove additional files at destination boolean. Optional. Use when UseWebDeploy == true && WebAppKind != linux && WebAppKind != applinux && WebAppKind != "". Default value: false. Note: This will also remove all files related to any extension installed on this Azure App Service. To prevent this, select the Exclude files from App_Data folder checkbox.

Where can I find the documentation for this? Is this part of the azure/webapps-deploy@v2 documentation, Azure CLI or Azure Portal?

Appreciate the feedback.
ajkuma 28,036 Reputation points Microsoft Employee Moderator

2024-11-28T14:21:06.97+00:00

You may check these referenced docs for DevOps.

AzureRmWebAppDeployment@4 - Azure App Service deploy v4 task

AzureRmWebAppDeployment@2 - Azure App Service Deploy v2 task

Share via

SSH CONN CLOSE Error on Azure App Service

1 answer

Your answer