When I enter my server hostname/address without a port, the app successfully logs in. However, after login, the saved server URL appears to be modified by appending ":4096" to the address.
On the next reconnect attempt, the app tries to connect using the modified URL with ":4096", which fails. To reconnect successfully, I need to manually delete ":4096" from the saved server URL.
Steps to reproduce
- Open the app.
- Enter a server hostname/address without specifying port "4096".
- Log in successfully.
- Close/reopen the app or trigger reconnect.
- Observe that the saved server URL now includes ":4096".
- Reconnect fails.
- Manually remove ":4096" from the server URL.
- Reconnect works again.
Expected behavior
The app should preserve the server URL exactly as entered, unless the user explicitly specifies a port.
For example:
"https://my-host.example.com"
should remain:
"https://my-host.example.com"
Actual behavior
The app modifies the saved server URL by appending ":4096".
For example:
"https://my-host.example.com"
becomes:
"https://my-host.example.com:4096"
This causes reconnect to fail when the server is not exposed on port "4096".
Notes
It seems like the app may be applying a default port after successful login and persisting that modified URL, instead of preserving the original user-provided URL.
When I enter my server hostname/address without a port, the app successfully logs in. However, after login, the saved server URL appears to be modified by appending ":4096" to the address.
On the next reconnect attempt, the app tries to connect using the modified URL with ":4096", which fails. To reconnect successfully, I need to manually delete ":4096" from the saved server URL.
Steps to reproduce
Expected behavior
The app should preserve the server URL exactly as entered, unless the user explicitly specifies a port.
For example:
"https://my-host.example.com"
should remain:
"https://my-host.example.com"
Actual behavior
The app modifies the saved server URL by appending ":4096".
For example:
"https://my-host.example.com"
becomes:
"https://my-host.example.com:4096"
This causes reconnect to fail when the server is not exposed on port "4096".
Notes
It seems like the app may be applying a default port after successful login and persisting that modified URL, instead of preserving the original user-provided URL.