Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Azure WebApp Slots bug #291

Closed
micyb1 opened this issue Jan 23, 2019 · 3 comments
Closed

Azure WebApp Slots bug #291

micyb1 opened this issue Jan 23, 2019 · 3 comments
Assignees
Labels

Comments

@micyb1
Copy link

micyb1 commented Jan 23, 2019

Hi.
I have tried to install certificate on slot in webapp (in main app, everything is works fine).
I am in extension and when I choose custom domain and put my e-mail address and click Request and Install Certificate after few second I have an error:

I am on site: https://webapp-portal-web-01.scm.azurewebsites.net/letsencrypt/Home/Install

Server Error in '/letsencrypt' Application.


The remote name could not be resolved: 'webapp-portal-web-01-webapp-portal-web-02.scm.azurewebsites.net'
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Net.WebException: The remote name could not be resolved: 'webapp-portal-web-01-webapp-portal-web-02.scm.azurewebsites.net'

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

My main site name is: webapp-portal-web-01, slot name is webapp-portal-web-02
DNS for main is: webapp-portal-web-01.azurewebsites.net and for slot is webapp-portal-web-01-webapp-por.azurewebsites.net

I don't know why extension wants something from dns address that is combination of main and slot app name.

@sjkp sjkp self-assigned this Jan 23, 2019
@sjkp sjkp added the bug label Jan 23, 2019
@sjkp
Copy link
Owner

sjkp commented Jan 23, 2019

Looks like a bug, I don't personally use slots and it haven't been tested by me for a while.

@micyb1
Copy link
Author

micyb1 commented Jan 24, 2019

Ok, I know where is the problem.
Extension always use dns name in format: mainappname-slotappname.azurewebsites.net
But if your main app name and slot name is too long, azure cut dns name.
Extension should get DNS name of slot app from configuration. DNS label can be up to 63 characters

sjkp added a commit that referenced this issue Feb 10, 2019
@sjkp
Copy link
Owner

sjkp commented Feb 10, 2019

This is fixed in 0.9.3. @micyb1 thanks for the accurate error report 👍

@sjkp sjkp closed this as completed Feb 10, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants