[GH-ISSUE #19] 🐞 Bug: cross migration #14

Closed
opened 2026-03-02 15:47:12 +03:00 by kerem · 4 comments
Owner

Originally created by @PhiGi87 on GitHub (Jan 29, 2026).
Original GitHub issue: https://github.com/PegaProx/project-pegaprox/issues/19

Good morning,

unfortunately something still isn’t working with the cross migration. The disk is migrated successfully to the second cluster, but—if I understand it correctly—when the RAM is supposed to be synced, the tunnel cannot be re-established because the authorization fails.

Look here in the log: https://pastebin.com/EA5gPumt

Thank you for your work.

Originally created by @PhiGi87 on GitHub (Jan 29, 2026). Original GitHub issue: https://github.com/PegaProx/project-pegaprox/issues/19 Good morning, unfortunately something still isn’t working with the cross migration. The disk is migrated successfully to the second cluster, but—if I understand it correctly—when the RAM is supposed to be synced, the tunnel cannot be re-established because the authorization fails. Look here in the log: [https://pastebin.com/EA5gPumt](https://pastebin.com/EA5gPumt) Thank you for your work.
kerem 2026-03-02 15:47:12 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@MrMasterbay commented on GitHub (Jan 30, 2026):

Heyha @PhiGi87 ,

We've checked this out and we've modified there our delay. @mkellermann97 configured this already and this should work with our newer version then.

Best Regards,
Nico

<!-- gh-comment-id:3824768454 --> @MrMasterbay commented on GitHub (Jan 30, 2026): Heyha @PhiGi87 , We've checked this out and we've modified there our delay. @mkellermann97 configured this already and this should work with our newer version then. Best Regards, Nico
Author
Owner

@mkellermann97 commented on GitHub (Jan 30, 2026):

Hi @PhiGi87,
As Nico mentioned above, we've adjusted the timeout limit. It should work without any issues now.
Regards,
Marcus

<!-- gh-comment-id:3824942806 --> @mkellermann97 commented on GitHub (Jan 30, 2026): Hi @PhiGi87, As Nico mentioned above, we've adjusted the timeout limit. It should work without any issues now. Regards, Marcus
Author
Owner

@PhiGi87 commented on GitHub (Feb 1, 2026):

Even after the update, I still have the exact same problem :-/

<!-- gh-comment-id:3830811790 --> @PhiGi87 commented on GitHub (Feb 1, 2026): Even after the update, I still have the exact same problem :-/
Author
Owner

@mkellermann97 commented on GitHub (Feb 1, 2026):

Hi @PhiGi87 ,

please send us a detailed log and maybe even a screenshare to support@pegaprox.com .
Please note due high demand currently we are currently slow with replying.
Regards,
Marcus

<!-- gh-comment-id:3831081164 --> @mkellermann97 commented on GitHub (Feb 1, 2026): Hi @PhiGi87 , please send us a detailed log and maybe even a screenshare to support@pegaprox.com . Please note due high demand currently we are currently slow with replying. Regards, Marcus
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/project-pegaprox-PegaProx#14
No description provided.