Hello, I was commenting to say this same issue has resurfaced in a new update I did yesterday.

However, I see XO-Server was updated to 5.177.4 (from 5.177.3) which seemed to have fixed this after applying the update and rebooting.

Hopefully this issue does not appear again in another release.

Seems like now I have another thing to fix and update

Hello, I was commenting to say this same issue has resurfaced in a new update I did yesterday.

However, I see XO-Server was updated to 5.177.4 (from 5.177.3) which seemed to have fixed this after applying the update and rebooting.

Hopefully this issue does not appear again in another release.

Seems like now I have another thing to fix and update