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

Not able to connect to different domain name APIM #82

Closed
anjusharma17 opened this issue Jun 17, 2019 · 8 comments
Closed

Not able to connect to different domain name APIM #82

anjusharma17 opened this issue Jun 17, 2019 · 8 comments
Assignees

Comments

@anjusharma17
Copy link

Hi, we are not able to connect to different domain name than azure-api.net. And getting ETIMEDOUT error.

ETimeOut Error

I have followed all the config steps, let me know if need to do some other changes as well.

@azaslonov
Copy link
Member

Hi Anju,
On your screenshot, I see that you still trying to call [service].management.azure-api.net. I guess you wanted to specify your custom hostname for management endpoint?

@azaslonov azaslonov self-assigned this Jun 17, 2019
@anjusharma17
Copy link
Author

Hi Alexander,

From where we can find out the management_endpoint for custom domain, can you please share the updated links?

In the generate.bat file, its is given that set management_endpoint="< service name >.management.azure-api.net"
So for custom domain, it could not be xyz.management.azure-api.net as per your response, where xyz is the service name.
Thus I set the management_endpoint="apim-portal-nonprod.dname.com", also tried with "apim-portal-nonprod.management.dname.com", but did not worked.

custom domain1
The above error is thrown at the following code -> resolve(JSON.parse(data)), in generate.js file.

custom domain2

portal

Please suggest from where we can find out the management endpoint for custom domain?

@azaslonov
Copy link
Member

Hi Anju, the hostname for your management endpoint should be exactly as you defined it in Custom domains section:

image

image

Just in case, if you didn't setup a custom domain for management API, that means your default <service>.management.azure-api.net timed out by a different reason (i.e. VNET configuration). I'll be able to check that if you send me your service name to alzaslon@microsoft.com

@anjusharma17
Copy link
Author

Thanks Alexander, it is working now

@anjusharma17
Copy link
Author

Hello Alexander, on local it worked
From azure Portal, facing two issues further to this:

  1. Whenever we are clicking on New Developer Portal(Preview) the link is not working. However, some days back it was working.

Portal not working

  1. The same kind of issue persist, when we sign up from our APIM, which we have published into our storage account. We get one sign up link to confirm in the email account. The same error screen appears when we try to click on confirmation link.

Error: This site can’t be reached xyz.developer.azure-api.net’s server IP address could not be found.

Let us know how to handle this for custom domain or are we missing any configuration for this?
It is a custom domain APIM, but i am not sure why the error related to azure-api.net is coming.

@azaslonov
Copy link
Member

Anju, it seems like I'll need APIM service name to help you. Please email me at alzaslon@microsoft.com.

@mikebudzynski mikebudzynski added the Response needed Issues, which require a response from the author. label Jun 21, 2019
@anjusharma17
Copy link
Author

Hi Alexander, i have mailed you the required information. Please check.

@mikebudzynski mikebudzynski removed the Response needed Issues, which require a response from the author. label Jun 21, 2019
@azaslonov
Copy link
Member

Hi Anju,
Looking at your service it seems to be VNET-related issue. We'll update respective documentation to help you resolve it. Please use this item for tracking it: #97

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants