Installation failure on Windows 10

[CAPL_INFO]

Hello
I'm running Windows 10 Pro v 21H1 build 19043.1586

Installation of Profound.js according to the instructions @ https://docs.profoundlogic.com/display/ ... requisites fails.

This error message appears when attempting to install node-fiber:


According to https://github.com/laverdet/node-fibers/issues/451, node-fiber doesn't support nodejs v16.

After downgrading to Node.js v14, the installation completes but during install download of Profound static files fails:

Code: Select all

Error: connect ECONNREFUSED 52.219.103.90:80
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1159:16) {
  errno: -4078,
  code: 'ECONNREFUSED',
  syscall: 'connect',
  address: '52.219.103.90',
  port: 80
}
Download ended in error:
Error: connect ECONNREFUSED 52.219.103.90:80
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1159:16) {
  errno: -4078,
  code: 'ECONNREFUSED',
  syscall: 'connect',
  address: '52.219.103.90',
  port: 80
}

Due to that failure, starting the default test application doesn't really give any result:


Trying to start the designer also fails, for the same reason I suspect:

[Scott Klement]

As you mentioned, Profound.js does not yet support Node 16. Profound.js was built around a 3rd-party package called "Fibers" which is not supported in Node 16, so we have to rewrite a huge portion of the application to work differently, it will take some time to rewrite it.

With regards to the 2nd problem -- it needs to download the JavaScript framework that we use in the web browser. For some reason, you received an error downloading it, so you don't have those files on your system.

You should be able to run node updatepui.js from your Profound.js directory to get it to try again.

[CAPL_INFO]

Hey Scott
Thanks for the reply.
I tried that but it didn't work:

I feel like this could be solved by downloading the source files manually and putting them in a htdoc directory in this folder.
I've looked at https://github.com/ProfoundLogic/ in search of those files but I haven't managed to find them.

[Scott Klement]

That is strange, it seems to think that what you have in the 'htdocs' folder is up-to-date, even though parts of it are missing.

I would suggest renaming the 'htdocs' folder to something else (maybe htdocs-old) and then running node updatepui.js -- since it won't be able to find the folder, it should say the version is "Unknown", and allow you to update to the latest version.

If you have custom code within that folder, you'll need to copy it from htdocs-old to htdocs.

[CAPL_INFO]

This is a fresh install, so I have no legacy code to worry about.
However, the htdocs folder doesn't actually get created by the command.

[Scott Klement]

I have never seen this problem before. My best guess is that your PC doesn't have access to the Internet, or perhaps this particular site is blocked by a firewall or similar device.

I would suggest contacting Profound Logic Support for assistance.

[CAPL_INFO]

Hello everyone
I'm closing this, turns out Scott and the PUI support team were correct, this was indeed due to our corporate network filters being overly hostile to nodejs traffic.
I would suggest augmenting the verbosity of the

Code: Select all

updatepui

tool though so the messages produced in that case be less misleading.
I have temporarily solved the issue by running the installer on a Linux device outside of our network, and then manually transplanting the

Code: Select all

htdocs

folder into my corporate windows machine.