Connection Security in ProjectX42

Connection security in ProjectX42

ProjectX42 can be reached in two ways: on your local network (at home, on the same Wi-Fi) and remotely (over the internet when you're away). The companion app lets you choose how strict it should be about the security of each connection.

Why it matters

• At home, your traffic stays on your own network, so a plain http:// connection to your server is usually fine and fast.
• Away from home, your traffic travels over the internet. You should always use a secure https:// connection with a valid certificate so nobody can read or tamper with it.

Security levels

When you add a server, ProjectX42 asks how you want to connect:

• Standard — recommended for most people. Uses your home network directly when you're home and your secure external address when you're away.
• Strict — only ever connects over a verified secure (https://) connection, even at home. Choose this if you want the highest assurance and have set up TLS on your local network.

Recommendation

Use a secure external URL (https://) for remote access, keep your server updated, and never expose the plain http:// port directly to the internet. If you need certificate- based device authentication, see Client certificates (mTLS).