Hi. This has now been resolved. It needed nvm to be configured to use V18 of node and pm2 updating to run from mv18 not v16

Error after upgrading to 4.0.0 - Error 502 Bad Gateway.
I am running jsreport on an EC2 instance in AWS, but after upgrading JSReport to 4.0.0 I just get Error 502 Bad Gateway.

Hi @bjrmatos we are looking to go back to 08062022. The only thing we did, was upgrade JSReport from 3.1.1 to 3.6.2 on 16/06/2022.

Our original problem isn't with the version data, it is the missing files that we want to get back from the version history

@bjrmatos we did not edit anything directly in the data folder. We only use jsreport studio. We were about to go live with 30 reports in our software when this issue occurred so we are not happy to lose everything. I think to move forward we will be looking for another report provider.

@jan_blaha have you managed to take a look with the data I sent?

Hi

I have emailed you the data.

Thank you

Hi,

We are attempting to revert some commits using the our admin user but it asks us to login. When we login using the admin user it says unauthorised.

We are using version 3.6.2 hosted on an AWS EC2 instance.

Any ideas?

Many thanks

Richard