Not able to connect to <id>@public if i use a selfhosted/Pro

Cannot use @public while configured for self-hosted instance / no GitHub or Google login option available

Description

I manage and control multiple devices through my own self-hosted RustDesk instance. This works well for my internal devices.

However, I also regularly need to connect to external devices from different companies for one-time setup or support of my product. These external devices are usually not part of my self-hosted RustDesk instance and should not be permanently added to it.

For this use case, ID@public would be the expected solution. Unfortunately, I cannot use it because RustDesk requires me to log in for the public server.

The problem is that my client is configured for my self-hosted instance, so the account login only shows the login for my self-hosted server. I do not see any option to log in with GitHub, Google, or another public RustDesk login provider.

Current behavior

• My RustDesk client is configured for a self-hosted server.
• Account login only points to my self-hosted instance.
• When I try to connect to an external device using ID@public, RustDesk asks me to log in.
• I am already logged in to my self-hosted instance, but this does not seem to count for the public server.
• There is no visible option to log in to the public server using GitHub, Google, or another third-party provider.
• The only workaround seems to be removing or changing my existing self-hosted configuration temporarily, which is impractical and error-prone.

Use case

I need to keep my self-hosted RustDesk configuration for my own devices, but sometimes I must connect to external company devices for one-time support or setup.

I do not want to:

• delete or modify my self-hosted configuration every time,
• ask external companies to join my self-hosted instance,
• permanently register one-time support devices,
• use a separate Windows user, VM, or different PC just to access @public.

Question

What is the recommended way to handle this use case?

Is there currently a supported way to use @public from a client that is configured for a self-hosted instance?

If not, could RustDesk consider adding support for a separate public login or a simple server/profile switcher so that self-hosted users can still perform one-time external support sessions through the public server?

Start by reproducing the ID@public flow from a client configured for a self-hosted instance, focusing on account login and server configuration. Done means users can retain their self-hosted configuration while accessing the public server without deleting or changing it, with the supported login or switching behavior documented and tested.