I tried it the way you said and the error is still the same. I changed the version of the docker image to 24.9.0, I also made sure that the version number of asposepdfcloud is 24.9.0, I even changed the port number of the bindings to 5000 in your example, but it still doesn’t work. I checked the docker logs and there are only the following lines:
warn: Microsoft.AspNetCore.DataProtection.Repositories.FileSystemXmlRepository[60]
Storing keys in a directory '/root/.aspnet/DataProtection-Keys' that may not be persisted outside of the container. Protected data will be unavailable when container is destroyed.
warn: Microsoft.AspNetCore.DataProtection.KeyManagement.XmlKeyManager[35]
No XML encryptor configured. Key {0cad6a99-58eb-4da8-b7a9-bda3baf5a75e} may be persisted to storage in unencrypted form.
warn: Microsoft.AspNetCore.Server.Kestrel[0]
Overriding address(es) 'http://+:80'. Binding to endpoints defined via IConfiguration and/or UseKestrel() instead.
warn: Microsoft.AspNetCore.HttpsPolicy.HttpsRedirectionMiddleware[3]
Failed to determine the https port for redirect.
Is there any way I can output more debuggable logs?
@aizpy
it looks like your request is not being processed using the aspose-cloud docker image. Do you have any other services running in parallel with aspose-cloud? If you have more than one network card, check the ip address that the docker container uses.
-> sudo docker container list
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS
NAMES
287e3eae6399 aspose/pdf-cloud:24.9.0 "/bin/sh -c ./Aspose…" 12 hours ago Up About a minute 0.0.0.0:5000->5000/tcp, :::5000->5000/tcp AsposePdfCloud
@aizpy
We have noticed the reported issues and logged the following tickets in our issue tracking system for further investigation and rectification. We will notify you as soon as these issues are resolved.
PDFCLOUD-4489: Self Hosing - Object reference not set to an instance of an object
@aizpy
The bug has been investigated and tested. Try to run the aspose/pdf-cloud:24.9.0 image with the --env ASPNETCORE_ENVIRONMENT=Development parameter to display AspNetCore informational messages.
If you don’t see information messages in the docker log command, please share the command to start the container.
Not sure if this is resolved, but I had similar problem and it turns out that the docker volumes are not mounted correctly. Once the volumes are setup correctly, the problem disappeared.