- Home
- Forum
- ASP.NET Core - EJ 2
- "Web-service is not listening"
"Web-service is not listening"
Hi,
I am testing PfViewer and have encountered a problem - when I deploy my app to docker container to be run on GCP Cloud Run, I get the message: "Web-service is not listening.." Same app runs OK on local host. I've seen multiple similar posts, but nothing seems to help. I have also followed and used sample that you provide here:
and on localhost it runs very well, but once I upload it to Cloud Run, I get the same error.
What could be the reason for it?
Regards,
Janis
Open the developer tools and share the network tab response as in the screenshot while the "Web service not listening issue" occurred. This details will be helpful for us check in our end.
Please follow the below steps to check the network tab response:
- Open the developer tools.
- Go to Network tab.
- Load the PDF document.
- Click the server action method. In the given screenshot, we checked the Download server action.
- .Go to Response tab.
- Share the response tab error details.
Hi Chinnamunia ,
Not sure, if I did it right, but I got something like this:
"The type initializer for 'Syncfusion.EJ2.PdfViewer.PdfiumNative' threw an exception."
Does this make any sense? Maybe I can share with you web link so you can get all the details you need?
Regards,
Janis
From the given error details, We suspect PDFium dependency is not installed the deployed environment. We have shared the commands to install the pdfium dependency package in the Linux machine and also we have shared docker file below for your reference. Please modify your docker file as in the given file docker file.
|
RUN ln -s /lib/x86_64-linux-gnu/libdl-2.24.so /lib/x86_64-linux-gnu/libdl.so # install System.Drawing native dependencies RUN apt-get update && apt-get install -y --allow-unauthenticated libgdiplus libc6-dev libx11-dev RUN ln -s libgdiplus.so gdiplus.dll |
Docker file: https://www.syncfusion.com/downloads/support/directtrac/general/ze/Dockerfile-1587079776.zip
Kindly try this and let us know, if you have any concerns.
This usually happens on Cloud Run when the container is not listening on the correct port or the service is bound to localhost instead of 0.0.0.0. I faced a similar issue while deploying a small backend used for a home appliance Service project, and updating the app to listen on the port provided by the environment variable fixed it. Also make sure the Docker container exposes the same port that Cloud Run expects.
Hi Heinrich Klaaseen,
Thanks for the details. Please reach out to us if you need any further assistance.
Regards,
Venkada Subramanian D
- 5 Replies
- 4 Participants
-
JD Janis Dzenis
- Apr 19, 2023 03:11 PM UTC
- Mar 11, 2026 05:00 AM UTC