Z
Zerops3mo ago
Swag

The problem happened again

idk why i can't access the api
14 Replies
Swag
SwagOP3mo ago
GitHub
testdeploy/testbackend at main · jasserhouimli/testdeploy
Contribute to jasserhouimli/testdeploy development by creating an account on GitHub.
Jan Saidl
Jan Saidl3mo ago
Hi @Swag , your application is accessible on the domain, but it returns HTTP status 404. The problem is most likely in your application's code.
Swag
SwagOP3mo ago
it works fine on the localhost , i reported the same issue few days ago and it has been solved by removing the http redirections and worked fine i got the same issue now and idk how to resolve it
Jan Saidl
Jan Saidl3mo ago
try to enable logging
"LogLevel": {
"Default": "Debug",
"Microsoft.AspNetCore": "Debug"
}
"LogLevel": {
"Default": "Debug",
"Microsoft.AspNetCore": "Debug"
}
and examine the container logs, which should show where the problem might be. Try to call curl -v http://localhost:5000 if your application response is correct.
Swag
SwagOP3mo ago
Jan Saidl
Jan Saidl3mo ago
looks like there is not matching endpoint to replay
2025-10-05T14:16:52.699Z Request starting HTTP/1.1 GET http://dotnet-1a1c-5000.prg1.zerops.app/ - - -
2025-10-05T14:16:52.716Z dbug: Microsoft.AspNetCore.Routing.Matching.DfaMatcher[1000]
2025-10-05T14:16:52.716Z No candidates found for the request path '/'
2025-10-05T14:16:52.743Z Request finished HTTP/1.1 GET http://dotnet-1a1c-5000.prg1.zerops.app/ - 404 0 - 36.7559ms
2025-10-05T14:16:52.744Z info: Microsoft.AspNetCore.Hosting.Diagnostics[16]2
2025-10-05T14:16:52.699Z Request starting HTTP/1.1 GET http://dotnet-1a1c-5000.prg1.zerops.app/ - - -
2025-10-05T14:16:52.716Z dbug: Microsoft.AspNetCore.Routing.Matching.DfaMatcher[1000]
2025-10-05T14:16:52.716Z No candidates found for the request path '/'
2025-10-05T14:16:52.743Z Request finished HTTP/1.1 GET http://dotnet-1a1c-5000.prg1.zerops.app/ - 404 0 - 36.7559ms
2025-10-05T14:16:52.744Z info: Microsoft.AspNetCore.Hosting.Diagnostics[16]2
Swag
SwagOP3mo ago
its fixed but how i can static files 025-10-05T14:28:37.635Zdbug: Microsoft.AspNetCore.SignalR.Internal.DefaultHubProtocolResolver[1] 2025-10-05T14:28:37.635Z Registered SignalR Protocol: json, implemented by Microsoft.AspNetCore.SignalR.Protocol.JsonHubProtocol. 2025-10-05T14:28:37.678Z warn: Microsoft.AspNetCore.StaticFiles.StaticFileMiddleware[16] 2025-10-05T14:28:37.678Z The WebRootPath was not found: /var/www/wwwroot. Static files may be unavailable. 2025-10-05T14:28:37.684Z dbug: Microsoft.Extensions.Hosting.Internal.Host[1] 2025-10-05T14:28:37.684Z Hosting starting 2025-10-05T14:28:37.700Z warn: Microsoft.AspNetCore.StaticFiles.StaticFileMiddleware[16] 2025-10-05T14:28:37.700Z The WebRootPath was not found: /var/www/wwwroot. Static files may be unavailable.
Aleš
Aleš3mo ago
you need to have your files in /var/www/wwwroot, which you probably don't, have you deployed them (build.deployFiles in zerops.yml)?
Aleš
Aleš3mo ago
The only artifact you are passing from the build container to the runtime container is contents of the app/ folder - https://github.com/jasserhouimli/testdeploy/blob/main/zerops.yml#L19 so if you want to pass wwwroot as well, it needs to be defined here so unless your build automatically adds it to the app folder, you have to add the path to it manually.. you can use the built in file browser (right under runtime log) to see what actually ended up in the runtime container
Swag
SwagOP3mo ago
example to add the wwwroot defined in the github repo inside the testbackend folder i add wwwroot ?
Aleš
Aleš3mo ago
https://docs.zerops.io/zerops-yaml/specification#deployfiles- you add path to the folder relative to your zerops.yml
Aleš
Aleš3mo ago
can use ~ to mark from which point it should deploy
No description
Michal Saloň
Michal Saloň3mo ago
The resulting zerops.yml part would probably look like this, but look at the documentation Ales linked above.
build:
deployFiles:
- app/~
- testbackend/~/wwwroot
build:
deployFiles:
- app/~
- testbackend/~/wwwroot

Did you find this page helpful?