HTTP 302 Found when attempting to perform an upgrade to OSS 3.28.1

I’ve updated our old 2.x OSS server to the latest 2.x version (2.14.19) Also have the new OSS 3.28.1 server running and ready to migrate the data from the old 2.x version. I’m following the instruction for migrating data from 2.x to 3.x. I have the upgrade agent running on the old server and I’m performing the upgrade steps on the new server. On the new server, after I enter the URL, Access Token and Fetch Size I click Next and get the error “HTTP 302 Found.” On both servers the context was changed from /nexus to / so I’m not sure if that has anything to do with it. I’ve searched this forum for “HTTP 302 Found” and did not get a single hit. So now I’m stuck. A 302 is a redirect so not sure why the old server is returning a 302.

On the old host I can see the request:
“GET /service/siesta/migrationagent/status HTTP/1.1” 302 0 0

Any tips on how to solve this problem?

1 Like

I’m going to try uninstalling 3.28.1 and instead install 3.0 to see if I can perform the data migration from an early 3.x version.

Problem solved. I had enabled the module to redirect http-to-https. I disable that module and the target migration server directly accessed the source migration server on port 8081.

1 Like