Symptoms
-
The page
https://manager.diekasse.apporhttps://manager.diekassa.appdoes not load or stays stuck while loading. -
However, a ping to the domain works.
-
When testing with
curl -I https://manager.diekasse.app, the connection takes a very long time or aborts.
Cause
Our platform is reachable via IPv4 and IPv6.
Some internet connections signal IPv6 support but cannot establish a working IPv6 connection.
Browsers prefer IPv6 by default. If this connection fails, long wait times or a connection timeout occur, even though the IPv4 connection would actually work.
Quick Tests
-
IPv4 test via cURL
bash curl -4 -I https://manager.diekasse.appIf you receive an immediate response (e.g.HTTP/2 200), the issue is most likely a broken or misconfigured IPv6 connection. -
Check the network path (traceroute / tracert)
-
macOS / Linux:
bash traceroute manager.diekasse.appWindows:```bash tracert manager.diekasse.app
4. With this information, our support team can quickly determine whether it is, in fact, a routing or ISP issue rather than an IPv6 problem.
### Solutions
1. **Repair IPv6**
2. Contact your internet provider and ask them to check or activate a working IPv6 connection.
3. Alternatively, you can ensure in your router or operating system that IPv6 is correctly set up.
4. **Temporarily disable IPv6**
5. On the individual computer or local network, you can disable IPv6 so that the browser uses IPv4 only.
6. This is a quick fix when an immediate correction via the provider is not possible.
### Why We Cannot Disable IPv6
Many of our customers already use functioning IPv6.
To ensure the best possible reachability, IPv6 support remains active on our side.
### Summary
If `manager.diekasse.app` does not load for you despite a successful ping, in most cases this is due to a **missing or faulty IPv6 connection**.
With the `curl -4`, `traceroute` or `tracert` commands, the issue can be quickly narrowed down and other possible causes can be specifically checked by support.