V3 Node server will not start

[dinostop]

I’m not a programmer so I have no idea about this.  It does work fine on V2 when I install it on that platform.

yes I did delete completely from v2 prior to installing under v3

[simplextech]

14 hours ago, bpwwer said:

I don't think running version 3.1.2 would cause this, but I've also never tried any node.js node servers on it yet.

I'm not running 3.1.2 yet but I did a clean install on my dev box and I did not have this error/problem.  

[dinostop]

Any idea how to go back to an earlier version that is not the test version of the system?

[bpwwer]

2 hours ago, dinostop said:

Any idea how to go back to an earlier version that is not the test version of the system?

Not yet.  It seems like the packaging system doesn't like to downgrade stuff.  I'm trying to get the production version back in the package repository.

There is a know issue where you can't install some of the free node servers with 3.1.2, that's a problem with the node server entries in the store so not related to what you're experiencing. 

There are a couple of fixes in 3.1.2 but most of the changes effect developers only.

[dinostop]

And as far as you know the ST-Heat will not work in the 3.1.2 version.

[dinostop]

@simplextech

@bpwwer

Any status on this?  I am still not able to use the ST_Nuheat node_server that I paid $50.00 for and I just did a Polyglot update and still have frontend version 3.1.2

[Michel Kohanim]

@dinostop,

I am so very sorry to hear. Please note we can give you a refund if this is not working.

With kind regards,
Michel

[dinostop]

@Michel Kohanim

I think the issue is that my front end version of V3 is a tester version and I need to get it to go back to the previous non tester version.  Not sure how it ended up on my Polisy unless I accidentally clicked on use beta version at some point.

[bpwwer]

I was able to reproduce the problem with ST-Nuheat on that test version.  It is an issue with that specific version of PG3 that has been fixed in the latest test version. 

I know how to update the various packages using the pkg command line, but I'm not sure that's a good idea anymore.

I suggest you do an update packages from the IoP configuration page in the admin console and see if that gets you a new version.  ideally, it will move you back to the latest production version 3.0.63.

 

[dinostop]

@bpwwer

i attempted a couple times to update all packages and no luck.  Version is still the same and that Node server still won’t connect.

[bpwwer]

Ok, I'm going to try and do a new release of PG3 by the end of the week.  This will be version 3.1.6.  Since it will be a new release with a new version, the package update should pick it up.   I'll do some testing to verify that before I actually announce it.