iOS and MacOS Pangolin clients sudden disconnections from private HTTP resources
- Dominant language
- TypeScript
- Stars
- 22.8k
- Forks
- 783
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 52
Description
### Describe the Bug
I've a video streaming service only accessible via a private resource. I can connect to it and start the playback of some video, but after 30s or so the playback stops. I noticed that it's because the private resource is no longer accessible (when reloading I get the private resource page informing that the resource is only accessible using a client). It happens the same without playing any video BTW, that is not a factor, even doing nothing triggers the disconnection.
**NOTE** I say the client disconnects, but to be precise, what I really mean is that the resource is no longer accessible, the client still reports it's connected.
Tested with both iOS and MacOS clients
### Environment
- OS Type & Version: debian
- Pangolin Version: 1.21.1
- Edition (Community or Enterprise): enterprise
- Gerbil Version: gerbil:latest (1.4.3 I guess?)
- Traefik Version: 3.6.25
- Newt Version: 1.16.0
- Client Version: 0.9.1 (iOS) 0.11.0 (MacOS)
### To Reproduce
1. setup some private HTTP resource (accessible via HTTPS)
2. connect iOS or MacOS client
3. access the HTTP resource with browser
4. wait for ~30s
5. reload the page in the browser to check that it's still available
### Expected Behavior
The private resource should be available as long as the client is connected
Contributor guide
Research direction
Reproduce the disconnection using the listed iOS and macOS client versions, a private HTTPS resource, and the Pangolin, Gerbil, Traefik, and Newt versions from the report; observe the resource after about 30 seconds. Trace the client/resource connectivity path and verify that the private resource remains accessible while the client still reports a connection.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ios, macos, typescript
- Domain
- desktop-dev, mobile-dev, networking, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100