Migrate 4.5.48 to V5.3.44-C68

Self-Hosted | v4/Legacy
#1

Good Day.

I am trying to Migrate from V4 to V5.
When I click on the migrate option - I FQDN is currently unable to handle this request. HTTP ERROR 500
In the logs on the source I dont see anything exciting - last line is "Production.INFO: get invoices → 1527 [] []

I am not sure where to go from there…can someone please help ?

Thanks
Johan

#2

Hi,

Do you see any errors in the v4 logs?

#3

Hi Hillel,

Nope - If only there were one line to give me an idea whats going on in some log…but not even that.

#4

@david do you have any suggestions?

#5

So i deleted the old logs and below is what i got - just deleted the domain name and IP

[2022-01-24T12:53:47.761264+00:00] production.ERROR: GuzzleHttp\Exception\ClientException [404] : /home/user/public_html/ninja/vendor/guzzlehttp/guzzle/src/Exception/RequestException.php [Line 113] => Client error: POST https://domain/invoice/api/v1/login?include=token resulted in a 404 Not Found response: {“message”:“Method not supported for this route”} {“context”:“PHP”,“user_id”:1,“account_id”:1,“user_name”:“NAME LASTNAME”,“method”:“POST”,“user_agent”:“Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/94.0.4606.71 Safari/537.36”,“locale”:“en”,“ip”:“IP.ADDRESS”,“count”:18,“is_console”:“no”,“is_api”:“no”,“db_server”:“mysql”,“url”:“migration/auth”} []
[2022-01-24T12:53:47.761579+00:00] production.ERROR: [stacktrace] 2022-01-24 12:53:47 Client error: POST https://domain/invoice/api/v1/login?include=token resulted in a 404 Not Found response: {“message”:“Method not supported for this route”} :

#6

@Kodlan

Do you have v5 installed in a folder? Is it possible to move it out of the folder and into its own subdomain?

#7

Just tried on a subdomain - same problem.

#8

I Spun up a VM and installed Ninja 5 and trying the same migration - and getting the same POST error with 404 Not Found…sounds like an API issue.

#9

Any assistance anyone?

#10

@Kodian

You’ll want to make sure your API endpoint is the correct path, to test, in a browser navigate to::

https://domain/api/v1/ping

Also, are you able to log into your v5 installation and navigate through the application ok?

#11

Hi David,

Yes I can navigate 100% fine when using V5 - just need to get my data across.

When i test the API i get the below results:

{“message”:“Invalid token”,“errors”:{}}

#12

@Kodlan

When you were using the subdomain, did you remove the /invoice folder? ie

https://subdomain/api/v1/ping

#13

Correct yes

I have 2 installs currently - one on a VM in just the root of /var/www/html and then a secondary on my webhost on the account subdomain folder.
Both I added the /api/v1/ping on it and both give me the same invalid token result.

#14

Any suggestions on this maybe ?

#15

@Kodlan,

To confirm, on your v5 installation, you have a user with identical email addresses across both systems?

#16

Hi David,
Yes I followed the procedure 100% with the installation.
The one installation is a manual deployment from the zip file and the other is installed via softaculous.

#17

Is there anything like Modsecurity on the server?

#18

Well its 2 different servers - so i am not sure. How do i check ?

#19

The Cpanel server has modsecurity - but the Linux VM doesnt have.

#20

I managed to resolve this issue.