5. Februar 2021 at 15:44 #10836AnsweredMartin DvorskyParticipant
I am trying to perform migration from OTRS Community to OTOBO using Docker.
I used migration guide from your docs, but got stuck on step 4. After I navigate to http://OTOBO-IP/otobo/migration.pl, I see migration instructions, but no Next button or anything else (see screenshot). What could be the problem?
9. Februar 2021 at 12:32 #10846Yannick WysockiParticipant
I’ve had the exact same problem when trying the migration for the first time.
As I was Troubleshooting and comparing source with target system, I realized that my OTRS source system has had a certificate for SSL/TLS installed and my target OTOBO system in docker didn’t have one yet.
So, I implemented the certificate for SSL/TLS (steps found in OTOBO installation manual for docker)….. and sure enough, I suddenly was shown a „Next“ button when opening the migration page via HTTPS protocol.
I hope this helps you :)
Have a great day!!
- This reply was modified 8 months, 2 weeks ago by Yannick Wysocki.
11. Februar 2021 at 9:37 #10855
thank you for your reply.
However, we don’t use SSL/TLS or Nginx reverse proxy neither in source OTRS system, nor in destination Otobo system. We use dedicated reverse proxy server which handles SSL/TLS, but while migrating we accessed Otobo migration page directly, not via reverse proxy server.
Thank you anyway, I will try to look into this more.
11. Februar 2021 at 9:46 #10856Sven OesterlingKeymaster
I think we have a bug there, which is specific to docker (or rather psgi) and http. I have not fully confirmed it – please wait till next week, I will then send an update.
Best regards, Sven
15. Februar 2021 at 13:56 #10880Sven OesterlingKeymaster
we fixed a bug, where this could occur with psgi and http. Please try if it works after updating to OTOBO 10.0.8.
Best regards, Sven
17. Februar 2021 at 13:40 #10899
thank you for these great news. I will try it as soon as possible and let you know if it’s fixed.
17. März 2021 at 22:10 #11096
Hi Sven and others,
sorry it took me the entire month to try it out, but I was very busy with other stuff.
Anyways, I updated Otobo to the latest version and migration page now works as it should. Thanks for the fix.
However, after the migration I can’t login into agent and customer portal. In agent portal the login button is grayed out and any link or button is unresponsive even in customer portal. I see these errors in browser console:
CommonJS_bd6f5fc717040faaa2b99b5f55ffb0df.js:1 Uncaught ReferenceError: jQuery is not defined
(anonymous) @ CommonJS_bd6f5fc717040faaa2b99b5f55ffb0df.js:1
TranslationJS_en_fc4f72148666e5884731dafbb9978b49.js:2 Uncaught TypeError: Cannot read property ‚Load‘ of undefined
(anonymous) @ TranslationJS_en_fc4f72148666e5884731dafbb9978b49.js:2
TemplateJS_d58ce399efffe18b0b40718d620fc7ca.js:2 Uncaught TypeError: Cannot read property ‚Load‘ of undefined
(anonymous) @ TemplateJS_d58ce399efffe18b0b40718d620fc7ca.js:2
ModuleJS_e2df7a35d5b1e982bb1f3d937d057d47.js:1 Uncaught TypeError: Cannot read property ‚CheckDependency‘ of undefined
(anonymous) @ ModuleJS_e2df7a35d5b1e982bb1f3d937d057d47.js:1
(anonymous) @ ModuleJS_e2df7a35d5b1e982bb1f3d937d057d47.js:8
customer.pl:387 Uncaught TypeError: Cannot read property ‚ExecuteInit‘ of undefined
(anonymous) @ customer.pl:387
customer.pl:407 Uncaught TypeError: Core.App.Ready is not a function
(anonymous) @ customer.pl:407
customer.pl:419 Uncaught TypeError: Core.App.Ready is not a function
(anonymous) @ customer.pl:419
Of course I tried incognito mode, deleting cookies, trying different browser, restarting Otobo host etc…
Migration itself went pretty smoothly, except on 4/5 step it showed well known popup saying I was disconnected from the server and if I wanted to stay on page or reload, and that was the end of the migration. Maybe it imported disabled SecureMode config from OTRS, so making the migration page unavailable and kicking me out? Idk, just guessing.
Any ideas what could be the problem? Thank you for your help.
18. März 2021 at 7:58 #11098Best AnswerSven OesterlingKeymaster
this is very likely because of an old jquery version being referenced in a SysConfig setting. Normally this should be adapted automatically, but maybe there was a problem with deploying the SysConfig settings, or you had changes in your OTRS settings, I’m not 100% sure what causes this, but I have encountered it before. From the command line please try the following:
bin/otobo.Console.pl Admin::Config::Update --setting-name 'Loader::Agent::CommonJS###000-Framework' --reset
This should fix it. You should then have a look at that setting in your SysConfig on the OTRS, just to check, whether you made manual changes to it (there would be a grey stripe on the side of this setting). If that is the case, you would have to reintroduce them on the OTOBO system per hand.
Best regards, Sven
18. März 2021 at 16:55 #11109
thank you very much for the help. You were right, I had this setting modified in the original OTRS SysConfig, even though I have no idea when or why I did it.
Anyway, agent and customer interfaces are working as they should. Only a few tweaks to do on my side and migration is complete. I have a few more unrelated questions, but I will create separate threads for them.
Thank you again, I am glad I have chosen Otobo with this great support staff.
- You must be logged in to reply to this topic.