Nothing happening
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 42/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Quiet
- Domain
- mobile, networking
Research direction
Start by reproducing the connection attempt with the reported Android 15, Pangolin, Gerbil, Traefik, and Newt versions on the described NixOS rootless Podman setup. Compare the Android app behavior with Pangolin and Gerbil logs, noting that only GET /api/v1/ appeared and no app log files were created. Done means identifying why the client remains disconnected or documenting the missing permission or diagnostic step.
Written by the indexing model from the issue text.
Description
Describe the Bug
Unfortunately there is not a lot to describe. I am using a somewhat exotic setup, deploying pangolin using rootless podman quadlets on nixos. However, the setup is working with public ressources and everything is running smoothely. Firewall is open on UDP Ports 51820 and 21820 and TCP Ports 80 and 443.
I just installed the Android App and setup the device, which works great, the device shows up in Pangolin and gets added to my organizations. However, when I try to connect, nothing happens except for the button in the app moving. It stays at disconnected, also in the web UI. What I tried:
- Debug mode on panglin server shows a single request to
2026-01-31T07:39:44+00:00 [debug]: GET /api/v1/ - Debug mode on gerbil does not show anything
- Turning on the logs in the app does not help, no logfiles are created
Is there anything else I can try to debug this? The only thing that comes to mind is trying to setup a new pangolin instance using the standard installer and see if anything is different. But I basically translated the installer for my setup, so I cannot see how this would make a difference...
Edit: I should add: The app did not ask for any permissions after opening and installing, maybe this is the issue?
Environment
- OS Type & Version: nixos unstable
- Pangolin Version: EE-1.15.1
- Gerbil Version: 1.3.0
- Traefik Version: 3.6
- Newt Version: 1.9.0
- Client Version: Android, 0.1.4 on Android 15, Samsung Galaxy S21 5G
To Reproduce
Setup as described above with the same phone model and versions, see if it works.
Expected Behavior
Client should connect.
- Dominant language
- Kotlin
- Stars
- 44
- Forks
- 11
- Avg merge
- 1m
- Merged PRs (30d)
- 6
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from fosrl/android
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
needs investigating
Difficulty 4/5 3-5 days Newbie friendliness 42/100
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
-
Switching organizations breaks Olm hole punching for the same client installationPossibly taken @oschwartz10612 claimed this 8 days ago. Openneeds investigating
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
home-assistant/android#7561 ·
Maintainers usually reply within 1 day
-
contributor: external needs review
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
fwcd/tree-sitter-kotlin#289 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
navikt/syfo-oppfolgingsplan-backend#482 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100