Windows Client removes FQDN

When I add a new server to mattermost, using the FQDN such as:
http://wasmatmo.myfqdhere.com:8065 the FQDN portion is removed, and just left with this:

This is incredibly annoying because I have to edit it each time I load it, then it will connect, but saves without the FQDN.

Is there something I can do on my end to get it to save the FQDN?

Hi @jagauthier, thanks for bringing this up! This behavior might be related to how the server URL is being parsed in the Windows Desktop App. Please check out our Troubleshooting mattermost issues guide for potential solutions. If the issue persists, let us know, and we’ll work with you to find a resolution!