Jamil
Jamil
One small UX request, instead of disconnecting the socket, can you `put_flash("Your session expired")` or maybe `JS.alert("Your session expired. Click Ok to return to the sign in page")` first
Ah I see, maybe the fix here is just to show a flash message "You must be signed in to do that" so that when the socket disconnects and the...
It seems like the portal isn't including this Gateway in the selection algorithm for connected clients: ``` {"time":"2024-01-05T01:22:28.565643Z","target":"connlib_shared::control","logging.googleapis.com/sourceLocation":{"file":"connlib/shared/src/control.rs","line":"230"},"severity":"WARNING","message":"Portal error: Offline"} {"time":"2024-01-05T01:22:28.565714Z","target":"connlib_client_shared::control","logging.googleapis.com/sourceLocation":{"file":"connlib/clients/shared/src/control.rs","line":"280"},"severity":"ERROR","message":"An offline error came back with a reference to a...
Happening with both Docker and Systemd deploys. Perhaps the Relays are having issues?
Edit: Seems like the issue is with CentOS 7 in particular. Gateway comes online OK but doesn't seem to be used by the portal for connections.
~~Edit: This ended up being an SELinux issue. It would be helpful if we could detect these somehow, but for the time being I'll mark this as a docs issue...
Seems to be resolved now.
We can table the major refactoring for later, but the primary point of this issue is to handle client-detected network changes and propagate this to connlib to react appropriately.