Updated 99. FAQ (Frequently Asked Questions) (markdown)

Cesar De la Torre 2017-10-25 17:43:29 -07:00
parent 9c26f48028
commit ad6daca2e7

@ -57,6 +57,7 @@ This is because of npm 5.3.0 on newer versions of nodejs. Downgrade to npm 5.2.0
### When trying to logging from MVC app the following error appears: IDX10803: Unable to obtain configuration from: 'http://10.0.75.1:5105/.well-known/openid-configuration' ### When trying to logging from MVC app the following error appears: IDX10803: Unable to obtain configuration from: 'http://10.0.75.1:5105/.well-known/openid-configuration'
#### Deploying in Windows with Docker for Windows
First open a browser and navigate to `http://10.0.75.1:5105/.well-known/openid-configuration`. You should receive json response. If not, ensure that Identity.API and Docker are running without issues. First open a browser and navigate to `http://10.0.75.1:5105/.well-known/openid-configuration`. You should receive json response. If not, ensure that Identity.API and Docker are running without issues.
If response is received the problem is that the request from a container cannot reach the `10.0.75.1` (which is the IP of the host machine inside the DockerNAT). Be sure that: If response is received the problem is that the request from a container cannot reach the `10.0.75.1` (which is the IP of the host machine inside the DockerNAT). Be sure that:
@ -65,6 +66,18 @@ If response is received the problem is that the request from a container cannot
If this do not solved your problem ensure that the `vpnkit` of the firewall is disabled. For more info refer to @huangmaoyixxx's comment in [issue #295](https://github.com/dotnet-architecture/eShopOnContainers/issues/295) If this do not solved your problem ensure that the `vpnkit` of the firewall is disabled. For more info refer to @huangmaoyixxx's comment in [issue #295](https://github.com/dotnet-architecture/eShopOnContainers/issues/295)
Another possibility is that the ASP.NET Identity database was not generated right or in time by EF Migrations when the app first started because the SQL container was too slow to be ready for the Identity service. You can have a workaround for that by increasing the time of retry with exponential backoff of the EF Contexts within the Identity.API service. Or simply, try re-deploying the app into Docker.
#### Deploying in a Mac with Docker for Mac
In a Mac, youn cannot use the 10.0.75.1 IP, so you need to change that in the `docker-compose.override.yml` file, replace the IdentityUrl environment variable (or any place where the IP 10.0.75.1 is used) with:
```bash
IdentityUrl=http://docker.for.mac.localhost:5105
```
Now, open a browser and navigate to `http://docker.for.mac.localhost:5105/.well-known/openid-configuration`.
You should receive json response. If not, ensure that Identity.API and Docker are running without issues.
### When I try to run the solution in "Docker for Windows" (on the Linux VM) I get the error "Did you mean to run dotnet SDK commands?" ### When I try to run the solution in "Docker for Windows" (on the Linux VM) I get the error "Did you mean to run dotnet SDK commands?"
If you get this error: If you get this error: