Skip to content

feat(mob): add an explicit HTTPS/WSS switch for custom servers - #164

Merged
mrsumanbiswas merged 1 commit into
CommandLineCoding:v0.3.5from
mrsumanbiswas:161-feat-https-toggle-for-self-hosted-servers
Nov 7, 2026
Merged

mrsumanbiswas merged 1 commit into
CommandLineCoding:v0.3.5from
mrsumanbiswas:161-feat-https-toggle-for-self-hosted-servers

Conversation

@mrsumanbiswas

Copy link
Copy Markdown
Member

The app only used TLS when the port was 443 or the host was Elephant Cloud, so a self-hosted TLS server on e.g. 8443 was contacted over plain HTTP/WS, login included. Server settings now has a "Use HTTPS/WSS" switch (on by default, follows ports 80/443), stored with the host and port. REST, WebSocket and the health check share one URL builder. Servers saved before this keep their previous scheme.

Closes #161

The app only used TLS when the port was 443 or the host was Elephant
Cloud, so a self-hosted TLS server on e.g. 8443 was contacted over plain
HTTP/WS, login included. Server settings now has a "Use HTTPS/WSS"
switch (on by default, follows ports 80/443), stored with the host and
port. REST, WebSocket and the health check share one URL builder.
Servers saved before this keep their previous scheme.

Closes CommandLineCoding#161
@mrsumanbiswas
mrsumanbiswas merged commit 19e257c into CommandLineCoding:v0.3.5 Nov 7, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[FEAT]: Explicit HTTPS/WSS toggle for self-hosted servers

1 participant