It is still trying to access https://localhost:8080 but if you are running the pdf server elsewhere, you need to reconfigure pdfExportFeature to access the url/port where the server is running.
As to npm errors, try to remove node_modules, package-lock.json, run npm cache clean --force and then install and runt it again.
It looks that something is wrong while npm tries to install hummus which is required for the export server. We would recommend to fix the npm error first and then to check the complete log.
Hello.
It appears that export server doesn't work for you due to npm failing to install packages. I'd recommend to do a regular npm i and then check complete log to find the cause. If server is up and running, you should verify URL. Your JS application should point to the correct export server address. If address is ok, I'd recommend to run server in verbose mode and check log inside the server directory:
I have run the "node ./src/server.js --level=verbose" command and it gives the error
that the port is already used. Please see the below screenshot. I have killed the port with the command 'sudo kill -9 $(sudo lsof -t -i:8080)', but still get the same error.
So can you please let me know how we can remove this exception?
Query: If on the server the same port is already used by other applications, then how can we manage the pdf export server on the new port.
Thanks
Attachments
address alreay in use.png (19.7 KiB) Viewed 1000 times