History

1. Investigating12/09/2026, 11:54

   Since 10 September our control server reaches Node 2 only via Node 3, because a filter at the data centre provider drops the direct connection.

   What this means for you: nothing. Everything works; the detour is one extra hop inside the same data centre.

   We are waiting for the provider's answer and will remove the detour as soon as the direct path is clear again.

1. Resolved13/09/2026, 16:00

   Resolved: signing in on citexnode.com works again, with Discord, Google and with e-mail, password and the code from the app.

All 5 updates

1. Resolved12/09/2026, 11:52

   Resolved. Node 2 has been fully connected to our control plane again since 10 September, 15:51: start, stop, console, file manager, backups and the usage display all work. Your servers and bots kept running throughout.

   What happens next: the connection still takes a detour through Node 3 in the same data centre. Nothing changes for you and encryption stays end to end.

   The actual cause, a filter inside the data centre provider's network between our control server and Node 2, is reported there as a ticket and not yet fixed. We track the removal of the detour as a separate incident so nothing stays open here that is already working.

All 4 updates

1. Resolved30/08/2026, 13:48

   Resolved. The fix is deployed and verified. Please reload once with Ctrl+F5 so your browser picks up the new version.

   A check in the build now covers this case so it cannot come back unnoticed.

All 3 updates

1. Resolved23/08/2026, 17:00

   Resolved. E-mail delivery is working.

   The provider opened port 25 and set the reverse DNS record. Delivery tested to Gmail, GMX, iCloud, mail.com and freenet, each encrypted via STARTTLS; the DKIM signature verified against the published key.

   What you can do: if you registered before today, resend the confirmation mail from your settings. If your server was paused during this time, open a ticket and we restore its runtime.

All 2 updates