I am trying to migrate from a v4 installation on one server to another running v5 using docker-compose. The initial setup of v5 works well, but after starting the migration on my v4 instance I get locked out of the v5 server because of the following error on the login page:
I have let some time pass and today I updated my v4 instance to 4.5.21 and set up a new v5 instance running 5.0.25 and the good news is the error does not occure anymore. I get no error but after I start the migration there seems to be nothing happening afterwards.
What should I do? Migrate manually?
Edit: I got this from the nginx logs:
POST /api/v1/migration/start/VolejRejNm HTTP/1.1" 404 58 “-” “unirest-php/2.0”
Could it be a problem that I am migrating to a docker instance?
I guess secret is not the password but the optional one below the url on the login form. I left it empty before and I am not aware of setting one by running the artisan commands. Any idea?
@david the only thing close I have defined is APP_KEY and I thought I need that one. I have tried to echo $API_SECRET in the docker container and it returns nothing.
I deleted the containers and data, started over to be sure, restarted the queue and ran optimize and now I get the 404 again…
Can you try updating your V4 (msater branch) and V5 (v5-develop branch) code to the latest from GitHub please. There are fixes in there for most of these issue.
Thanks @david. It helped indeed. The migration started, but in my case it failed when (or after) importing tasks.
Also, I cannot log into v5 anymore (401 error: these credentials do not match our records).
I’ll need to setup a test environment to try and recreate this. I think it may be because the project has been deleted, but i’m not 100% sure. I’ll update here when i solve this one.