Fetch error FABRIC_E_TIMEOUT for SwaggerUI/swagger.json
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
I am developing an Azure Service Fabric Service, in which I have used Swashbuckle.AspNetCore to build API List. I am using the following code in my Startup.cs file
In ConfigureServices(IServiceCollection services)
services.AddSwaggerGen(c =>
{
c.SwaggerDoc("Backend", new Info { Title = "My Backend", Version = "v1.0" });
});`
And in Configure(IApplicationBuilder app, IHostingEnvironment env)
` app.UseSwagger(c => c.PreSerializeFilters
.Add((swagger, httpReq) => swagger.Host = httpReq.Host.Value));
app.UseSwaggerUI(c => c.SwaggerEndpoint("/MyApp.Fabric/MyApp.Backend/swagger/Backend/swagger.json",
"Backend"));`
Here, because I am developing SF service, I have used reverse proxy with swagger endpoint configuration. Now the same thing is working with my other services except one. I have the same code and same version of Swashbuckle.AspNetCore nuget used in all of my services that is 3.0.0
When I try to access the SwaggerUI for this service, I am getting the following error
Can anyone please help me on this ? I have been trying but could not get any suitable solution..
.net-core swagger azure-service-fabric swagger-2.0 swashbuckle
add a comment |
I am developing an Azure Service Fabric Service, in which I have used Swashbuckle.AspNetCore to build API List. I am using the following code in my Startup.cs file
In ConfigureServices(IServiceCollection services)
services.AddSwaggerGen(c =>
{
c.SwaggerDoc("Backend", new Info { Title = "My Backend", Version = "v1.0" });
});`
And in Configure(IApplicationBuilder app, IHostingEnvironment env)
` app.UseSwagger(c => c.PreSerializeFilters
.Add((swagger, httpReq) => swagger.Host = httpReq.Host.Value));
app.UseSwaggerUI(c => c.SwaggerEndpoint("/MyApp.Fabric/MyApp.Backend/swagger/Backend/swagger.json",
"Backend"));`
Here, because I am developing SF service, I have used reverse proxy with swagger endpoint configuration. Now the same thing is working with my other services except one. I have the same code and same version of Swashbuckle.AspNetCore nuget used in all of my services that is 3.0.0
When I try to access the SwaggerUI for this service, I am getting the following error
Can anyone please help me on this ? I have been trying but could not get any suitable solution..
.net-core swagger azure-service-fabric swagger-2.0 swashbuckle
This is clearly an access issue, make sure you can manually access that endpoint you have configured
– Helder Sepulveda
Sep 2 '18 at 15:21
No, I can not access this endpoint manually.
– starklord
Sep 3 '18 at 5:44
According to the error information, it indicate that can't load api definition. You could refer to this document blog to config swagger in the service fabric project.
– Tom Sun
Sep 3 '18 at 9:09
IF the swagger configuration is the same as your other services, and those are OK, this smells like something in Azure, maybe a routing issue on the proxy?
– Helder Sepulveda
Sep 3 '18 at 13:20
add a comment |
I am developing an Azure Service Fabric Service, in which I have used Swashbuckle.AspNetCore to build API List. I am using the following code in my Startup.cs file
In ConfigureServices(IServiceCollection services)
services.AddSwaggerGen(c =>
{
c.SwaggerDoc("Backend", new Info { Title = "My Backend", Version = "v1.0" });
});`
And in Configure(IApplicationBuilder app, IHostingEnvironment env)
` app.UseSwagger(c => c.PreSerializeFilters
.Add((swagger, httpReq) => swagger.Host = httpReq.Host.Value));
app.UseSwaggerUI(c => c.SwaggerEndpoint("/MyApp.Fabric/MyApp.Backend/swagger/Backend/swagger.json",
"Backend"));`
Here, because I am developing SF service, I have used reverse proxy with swagger endpoint configuration. Now the same thing is working with my other services except one. I have the same code and same version of Swashbuckle.AspNetCore nuget used in all of my services that is 3.0.0
When I try to access the SwaggerUI for this service, I am getting the following error
Can anyone please help me on this ? I have been trying but could not get any suitable solution..
.net-core swagger azure-service-fabric swagger-2.0 swashbuckle
I am developing an Azure Service Fabric Service, in which I have used Swashbuckle.AspNetCore to build API List. I am using the following code in my Startup.cs file
In ConfigureServices(IServiceCollection services)
services.AddSwaggerGen(c =>
{
c.SwaggerDoc("Backend", new Info { Title = "My Backend", Version = "v1.0" });
});`
And in Configure(IApplicationBuilder app, IHostingEnvironment env)
` app.UseSwagger(c => c.PreSerializeFilters
.Add((swagger, httpReq) => swagger.Host = httpReq.Host.Value));
app.UseSwaggerUI(c => c.SwaggerEndpoint("/MyApp.Fabric/MyApp.Backend/swagger/Backend/swagger.json",
"Backend"));`
Here, because I am developing SF service, I have used reverse proxy with swagger endpoint configuration. Now the same thing is working with my other services except one. I have the same code and same version of Swashbuckle.AspNetCore nuget used in all of my services that is 3.0.0
When I try to access the SwaggerUI for this service, I am getting the following error
Can anyone please help me on this ? I have been trying but could not get any suitable solution..
.net-core swagger azure-service-fabric swagger-2.0 swashbuckle
.net-core swagger azure-service-fabric swagger-2.0 swashbuckle
edited Sep 1 '18 at 9:33
starklord
asked Sep 1 '18 at 7:54
starklordstarklord
1011211
1011211
This is clearly an access issue, make sure you can manually access that endpoint you have configured
– Helder Sepulveda
Sep 2 '18 at 15:21
No, I can not access this endpoint manually.
– starklord
Sep 3 '18 at 5:44
According to the error information, it indicate that can't load api definition. You could refer to this document blog to config swagger in the service fabric project.
– Tom Sun
Sep 3 '18 at 9:09
IF the swagger configuration is the same as your other services, and those are OK, this smells like something in Azure, maybe a routing issue on the proxy?
– Helder Sepulveda
Sep 3 '18 at 13:20
add a comment |
This is clearly an access issue, make sure you can manually access that endpoint you have configured
– Helder Sepulveda
Sep 2 '18 at 15:21
No, I can not access this endpoint manually.
– starklord
Sep 3 '18 at 5:44
According to the error information, it indicate that can't load api definition. You could refer to this document blog to config swagger in the service fabric project.
– Tom Sun
Sep 3 '18 at 9:09
IF the swagger configuration is the same as your other services, and those are OK, this smells like something in Azure, maybe a routing issue on the proxy?
– Helder Sepulveda
Sep 3 '18 at 13:20
This is clearly an access issue, make sure you can manually access that endpoint you have configured
– Helder Sepulveda
Sep 2 '18 at 15:21
This is clearly an access issue, make sure you can manually access that endpoint you have configured
– Helder Sepulveda
Sep 2 '18 at 15:21
No, I can not access this endpoint manually.
– starklord
Sep 3 '18 at 5:44
No, I can not access this endpoint manually.
– starklord
Sep 3 '18 at 5:44
According to the error information, it indicate that can't load api definition. You could refer to this document blog to config swagger in the service fabric project.
– Tom Sun
Sep 3 '18 at 9:09
According to the error information, it indicate that can't load api definition. You could refer to this document blog to config swagger in the service fabric project.
– Tom Sun
Sep 3 '18 at 9:09
IF the swagger configuration is the same as your other services, and those are OK, this smells like something in Azure, maybe a routing issue on the proxy?
– Helder Sepulveda
Sep 3 '18 at 13:20
IF the swagger configuration is the same as your other services, and those are OK, this smells like something in Azure, maybe a routing issue on the proxy?
– Helder Sepulveda
Sep 3 '18 at 13:20
add a comment |
1 Answer
1
active
oldest
votes
On my case, when I dig the problem in more depth, I found in my APIs, there are some objects used which don't have any namespaces assigned. And somehow the runtime could not resolve the definitions for those objects which leads to a failure to load API definitions.
@Tom Sun, if you could post your comment as an answer, I will be able to mark it as answer. Thank you.
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f52126107%2ffetch-error-fabric-e-timeout-for-swaggerui-swagger-json%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
On my case, when I dig the problem in more depth, I found in my APIs, there are some objects used which don't have any namespaces assigned. And somehow the runtime could not resolve the definitions for those objects which leads to a failure to load API definitions.
@Tom Sun, if you could post your comment as an answer, I will be able to mark it as answer. Thank you.
add a comment |
On my case, when I dig the problem in more depth, I found in my APIs, there are some objects used which don't have any namespaces assigned. And somehow the runtime could not resolve the definitions for those objects which leads to a failure to load API definitions.
@Tom Sun, if you could post your comment as an answer, I will be able to mark it as answer. Thank you.
add a comment |
On my case, when I dig the problem in more depth, I found in my APIs, there are some objects used which don't have any namespaces assigned. And somehow the runtime could not resolve the definitions for those objects which leads to a failure to load API definitions.
@Tom Sun, if you could post your comment as an answer, I will be able to mark it as answer. Thank you.
On my case, when I dig the problem in more depth, I found in my APIs, there are some objects used which don't have any namespaces assigned. And somehow the runtime could not resolve the definitions for those objects which leads to a failure to load API definitions.
@Tom Sun, if you could post your comment as an answer, I will be able to mark it as answer. Thank you.
answered Nov 24 '18 at 7:03
starklordstarklord
1011211
1011211
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f52126107%2ffetch-error-fabric-e-timeout-for-swaggerui-swagger-json%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
This is clearly an access issue, make sure you can manually access that endpoint you have configured
– Helder Sepulveda
Sep 2 '18 at 15:21
No, I can not access this endpoint manually.
– starklord
Sep 3 '18 at 5:44
According to the error information, it indicate that can't load api definition. You could refer to this document blog to config swagger in the service fabric project.
– Tom Sun
Sep 3 '18 at 9:09
IF the swagger configuration is the same as your other services, and those are OK, this smells like something in Azure, maybe a routing issue on the proxy?
– Helder Sepulveda
Sep 3 '18 at 13:20