Skip to content

client: rejected user handling #105

@dalalama

Description

@dalalama

User rejected ends up in doublezero user list as rejected.
This should
a) trigger an alert of sorts
b) clear if the user connects again and is not rejected as currently if the user is rejected and tries to reconnect they're unable to unless this is cleared.
c) clear after a period of time <3 days?>

Also, we should make the error clearer:
a) that there were no ip addresses available to allocate instead of "No available tunnel block" or indicate the device is full.
b) the connected message at the end should probably be not-connected.

🔗 Start Provisioning User...
Using Public IP:
🔍 Provisioning User for IP:
Creating an account for the IP:
The Device has been selected: frk-dz01
User rejected

  • Reading logs...
    "Error: No available tunnel block"
    / Connected

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions