Issues deploying application to test server #802

11 Answer(s)

• 

  0

  gterdem created 4 years ago

  Senior .NET Developer

  Hello @scott7106,

  It seems like a problem with data protection key persistency.

  Can you try persisting data protection keys to file system or redis (if you have already) in your HostModule service configuration? For file persistency something like;

  context.Services.AddDataProtection().PersistKeysToFileSystem(new System.IO.DirectoryInfo(@"/var/my-af-keys/"));

  for windows use a directory like c:/my-af-keys/ etc.

  Save Cancel
• 

  0

  scott7106 created 4 years ago

  The issue with the persisted keys does not occur when the API is the root application of a website. I backed up and decided to attempt combining the applications so that the API is at the root and the angular client is deployed as a subfolder within the API.

  • HttpApi.Host\client

  In the Startup.cs file of the HttpApi.Host project, I added the following code to the ConfigureServices method:

  services.AddSpaStaticFiles(configuration =>
  {
      configuration.RootPath = "client";
  });
  

  In the Configure method, I added the following:

  app.UseSpaStaticFiles(new StaticFileOptions
  {
      FileProvider = new PhysicalFileProvider(
          Path.Combine(env.ContentRootPath, "client")),
          RequestPath = "/client"
  });
  
  app.UseSpa(spa =>
  {
      spa.Options.SourcePath = "client";
  });
  

  I created a local environment in Angular with the URI settings needed for this configuration, ran ng build for the new environment with a base-href value of /client/ and then used xcopy to place resulting dist files in my API project.

  With this configuration, I can access both the client and the API locally. However, while the login/logout process works and the GET methods from the API work for the client, as soon as I attempt to post something from the client, I get an error which is not sent by the server and the following entry in the log files. [ERR] The required antiforgery header value "RequestVerificationToken" is not present.

  Save Cancel
• 

  0

  bunyamin created 4 years ago

  Hello,

  It looks like your problem could be related to the case explained in the note within this docs

  If you serve your apis from the root, just set url to empty as follows:

  export const environment = {
    production: true,
    // ....
    apis: {
      default: {
        url: '', // <- use the context root here
       // ...
      },
    },
  } as Config.Environment;
  
  

  Would you try this?

  Save Cancel
• 

  0

  MILLENNIUM created 3 years ago

  Dears, Any update on this? we cannot publish any abp project, event if it is autogenerated by suite!

  Save Cancel
• 

  0

  bunyamin created 3 years ago

  Hello @MILLENNIUM,

  Could you post your environment.ts and environment.prod.ts here? This error is usually about misconfiguration.

  Save Cancel
• 

  0

  scott7106 created 3 years ago

  Hello @MILLENNIUM, We have not solved the issue with deploying this as a single website with the angular client as a sub folder. We have been successful deploying them as 2 separate web applications.

  Here is an exampe of the environment.ts file. This is the local setup, we replace the localhost with a public DNS for our test/production sites.

  import { Environment } from '@abp/ng.core';
  
  const baseUrl = 'https://localhost:44316/client';
  
  export const environment = {
    production: false,
    application: {
      baseUrl,
      name: 'Portal',
    },
    oAuthConfig: {
      issuer: 'https://localhost:44316',
      redirectUri: baseUrl,
      clientId: 'Portal_App',
      responseType: 'code',
      scope: 'offline_access openid profile email phone Portal',
    },
    apis: {
      default: {
        url: '',
        rootNamespace: 'OtisEd.Portal',
      },
    },
  } as Environment;
  

  Save Cancel
• 

  0

  bunyamin created 3 years ago

  Hello scott,

  Could you post an example of your request made from browser to the production site with request and response (headers as well)?

  We use a similar setup for our demo and it works. You can check it out here

  Save Cancel
• 

  0

  MILLENNIUM created 3 years ago

  Dears, I think the issue was because I was publishing the system with microservices to localhost, and they was an exception because of use self-signed certificate on my local server, I managed to solve the issue by changing the following code:

  context.Services.AddAuthentication() .AddJwtBearer(options => { options.Authority = configuration["AuthServer:Authority"]; options.RequireHttpsMetadata = Convert.ToBoolean(configuration["AuthServer:RequireHttpsMetadata"]); ; options.Audience = "WorkflowDemo"; options.BackchannelHttpHandler = new HttpClientHandler() { ServerCertificateCustomValidationCallback = HttpClientHandler.DangerousAcceptAnyServerCertificateValidator }; });

  Save Cancel
• 

  0

  bunyamin created 3 years ago

  Hello @MILLENNIUM,

  I'm glad you were able to solve your problem.

  @scott, could your problem also be related to some other configuration?

  Save Cancel
• 

  0

  scott7106 created 3 years ago

  @bunyamin, thank you for the assistance. We were able to deploy our application successfully as a single application in Azure. We may still have issues deploying it behind an SSL terminated load balancer, but that has been deferred to a later date.

  Save Cancel
• 

  0

  bunyamin created 3 years ago

  I'm glad your problem is solved. Closing this issue,

  Have a nice day.

  Save Cancel