Migration from v4.5.50 to v5 - 500 | Server Error

Self-Hosted | v4/Legacy
1

Hello,
I have upgraded to v.4.5.50 prior to v5 migration.

I set the owner email addresses and passwords to the same values. Disabled 2FA and started the migration process. After entering username and password, it ended in 500 Server Error.

I have no problem logging into v4.5.50 and v.5 instances using the same owner login credentials (no 2FA).

email value in env file in v5 docker folder is same as the owner email (and password) for the following lines;
IN_USER_EMAIL=
IN_PASSWORD=

v4.5.50 env file has
API_SECRET=password
which I don’t know has any impact on this issue.

v5 docker env file does not have the same line.

I tried running following command (with correct parameters)

curl -X POST ‘http://ninja.test:8000/api/v1/login’
-H “Content-Type:application/json”
-d ‘{“email":"[email protected]”,“password”:“password”}’
-H “X-API-SECRET:password”
-H “X-Requested-With: XMLHttpRequest”;

which resulted in

curl: (60) SSL certificate problem: unable to get local issuer certificate
More details here: curl - SSL CA Certificates

curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.

this is strange because I am able to access both instances over https and both are behind nginx proxies. (v5 runs on http but is behind https proxy nonetheless)

Thank you

ck

2

Hi,

I suggest checking storage/logs for details about the 500 error

3

I figured it out. Inside the v5 docker env file, the URL was set to http. Since both v4.5.50 and v5 instances reside on the same subnet, I used the http URL during the migration process which worked OK.

Thank you

ck

1 Like