← LOTSE

Support

One person answers these. Expect a real reply, not a ticket number.

Use the contact form, or write to support@lotse.cloud

Both reach the same mailbox. German or English, whichever you prefer.

Please allow a few working days — LOTSE is built by one person, and an honest wait is better than an automated acknowledgement. A message sent through the form usually becomes visible within about fifteen minutes, but it is collected by a machine that has to be awake, so overnight it can wait until morning. Neither route is faster than the other in practice.

Found a security problem instead? security@lotse.cloud, and please read security.txt first.

What to send

Three lines beat three paragraphs: what you did, what happened, and what you expected instead. Beyond that, two things make almost any report solvable on the first reply.

Your version

LOTSE → Settings → General → About. It reads like 2026.08 (Build 08271006). Please include the build number — the version alone changes only once a month.

The log

LOTSE → Settings → Logs. It records what the app actually did — which network it saw, when the tunnel came up, what a measurement returned. Copy the minute around the problem.

The log is written for you to read, not to be sent blindly. Have a look before you paste it: it names the networks you joined, which you may not want to share. Trimming it is fine.

Things worth checking first

A feature is greyed out

Some capabilities need privileges the App Store sandbox cannot grant — automatic MTU tuning is the main one. They unlock when the optional LOTSE Helper is installed, and LOTSE notices it within a minute. Everything else keeps working without it.

A network loads for other devices but not for you

That pattern is usually packet size, not the network being broken. LOTSE measures the path and adjusts; Settings → Current Network shows what it found. If a VPN is up, try it once with the VPN off — the difference tells you which side the problem is on.

A hotel or café portal will not open

Portals live on the local network, which a full-tunnel VPN can route away from you. Switch LOTSE off for a moment, sign in, switch it back on.

The VPN says connected but nothing loads

A WireGuard tunnel reports “connected” as soon as the local interface exists — before it has heard from the server. LOTSE checks separately whether the far end is answering and says so in the menu bar. If it reports the endpoint unreachable, the tunnel is up and the server is not.

Feature requests

Welcome, and genuinely read. Telling us the situation helps more than proposing the fix — the network you were on and what you were trying to do usually suggests a better answer than either of us had in mind.