starred/headscale
1
0
Fork 0
mirror of https://github.com/juanfont/headscale.git synced 2026-01-11 20:00:28 +01:00
Code Issues 98 Packages Projects Releases 10 Wiki Activity

iOS does not take custom Coordination URL into account #446

New Issue
Closed
opened 2025-12-29 01:29:28 +01:00 by adam · 6 comments
adam commented 2025-12-29 01:29:28 +01:00
Owner
Copy Link

Originally created by @matbgn on GitHub (Mar 20, 2023).

Bug description

The 1.38.1 iOS app does not respect custom coordination server URL and goes either on tailscale.com or, after multiple try/error on 127.0.0.1 (without any port)

To Reproduce

Mount a Headscale server on Ubuntu 22.04 and successfully connect from other device. Download last iOS app, set custom URL in settings and try to start app for authentication process.

Context info

  • Version of headscale used: 0.21.0
  • Version of tailscale client: 1.38.1
  • OS (e.g. Linux, Mac, Cygwin, WSL, etc.) and version: Ubuntu 22.04
  • Kernel version: 6.2.6
  • The relevant config parameters you used: local server discoverable on 192.168.x.x even by AirCast with UxPlay and iSH ping command
  • Log output: unfortunately none known
Originally created by @matbgn on GitHub (Mar 20, 2023). **Bug description** The 1.38.1 iOS app does not respect custom coordination server URL and goes either on tailscale.com or, after multiple try/error on 127.0.0.1 (without any port) **To Reproduce** Mount a Headscale server on Ubuntu 22.04 and successfully connect from other device. Download last iOS app, set custom URL in settings and try to start app for authentication process. **Context info** - Version of headscale used: 0.21.0 - Version of tailscale client: 1.38.1 - OS (e.g. Linux, Mac, Cygwin, WSL, etc.) and version: Ubuntu 22.04 - Kernel version: 6.2.6 - The relevant config parameters you used: local server discoverable on 192.168.x.x even by AirCast with UxPlay and iSH ping command - Log output: unfortunately none known
adam added the stalebug labels 2025-12-29 01:29:28 +01:00
adam closed this issue 2025-12-29 01:29:29 +01:00
adam commented 2025-12-29 01:29:29 +01:00
Author
Owner
Copy Link

@prom3theu5 commented on GitHub (Mar 21, 2023):

Sorry not seeing this myself.
I just set it up on my mobile after updating my server to 0.21.0

I ensured tailscale was closed on my iPhone
Then went into settings -> tailscale.
Toggled reset keychain to true and input my controller url

After that I started Tailscale.
The initial auth popup was tailscale.com, which I hit cancel on
I then opened the menu in the app and chose reauthenticate which then used my controller and showed nodekey

@prom3theu5 commented on GitHub (Mar 21, 2023): Sorry not seeing this myself. I just set it up on my mobile after updating my server to 0.21.0 I ensured tailscale was closed on my iPhone Then went into settings -> tailscale. Toggled reset keychain to true and input my controller url After that I started Tailscale. The initial auth popup was tailscale.com, which I hit cancel on I then opened the menu in the app and chose reauthenticate which then used my controller and showed nodekey
adam commented 2025-12-29 01:29:30 +01:00
Author
Owner
Copy Link

@stas-stelle commented on GitHub (Mar 27, 2023):

The initial auth popup was tailscale.com, which I hit cancel on
I then opened the menu in the app and chose reauthenticate which then used my controller and showed nodekey

I upgraded my server to 0.21.0 and the ios app to 1.38.1.

If I do as you said, choosing reauthenticate after canceling the tailscale popup, nothing happens.
The access logs on my nginx reverse proxy remain silent. It does not look like the app is even trying.
Does the ALTERNATE COORDINATION SERVER URL require some special format?

@stas-stelle commented on GitHub (Mar 27, 2023): > The initial auth popup was tailscale.com, which I hit cancel on I then opened the menu in the app and chose reauthenticate which then used my controller and showed nodekey I upgraded my server to 0.21.0 and the ios app to 1.38.1. If I do as you said, choosing reauthenticate after canceling the tailscale popup, nothing happens. The access logs on my nginx reverse proxy remain silent. It does not look like the app is even trying. Does the `ALTERNATE COORDINATION SERVER URL` require some special format?
adam commented 2025-12-29 01:29:30 +01:00
Author
Owner
Copy Link

@mentos1386 commented on GitHub (Apr 6, 2023):

I'm experiencing the same issue (on ipad). This is my first time setting this up.

I tried https://vpn.example.com, vpn.example.com and https://vpn.example.com:443 but non of them work. I'm trying to use OIDC as well if that matters.

It works on my linux and android machines.

Edit: Somehow after giving it some time and opening the app again, clicking the "re-authenticate" it worked 🤷

@mentos1386 commented on GitHub (Apr 6, 2023): I'm experiencing the same issue (on ipad). This is my first time setting this up. I tried `https://vpn.example.com`, `vpn.example.com` and `https://vpn.example.com:443` but non of them work. I'm trying to use OIDC as well if that matters. It works on my linux and android machines. Edit: Somehow after giving it some time and opening the app again, clicking the "re-authenticate" it worked :shrug:
adam commented 2025-12-29 01:29:31 +01:00
Author
Owner
Copy Link

@travisboss commented on GitHub (May 8, 2023):

I think I see an error here that it goes to the port of 8080 but I have a reverse proxy that it will hit on 443 but I cannot change the domain it seems to go to 443?

EDIT: I figured it out, once it fails on the reauth copy the url and just go to safari and paste it in without the 8080 it will give me the creds I need to setup the device.

@travisboss commented on GitHub (May 8, 2023): I think I see an error here that it goes to the port of `8080` but I have a reverse proxy that it will hit on `443` but I cannot change the domain it seems to go to `443`? EDIT: I figured it out, once it fails on the reauth copy the url and just go to safari and paste it in without the `8080` it will give me the creds I need to setup the device.
adam commented 2025-12-29 01:29:31 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Nov 5, 2023):

This issue is stale because it has been open for 180 days with no activity.

@github-actions[bot] commented on GitHub (Nov 5, 2023): This issue is stale because it has been open for 180 days with no activity.
adam commented 2025-12-29 01:29:31 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Nov 19, 2023):

This issue was closed because it has been inactive for 14 days since being marked as stale.

@github-actions[bot] commented on GitHub (Nov 19, 2023): This issue was closed because it has been inactive for 14 days since being marked as stale.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
CLI
DERP
DNS
Nix
OIDC
SSH
bug
database
documentation
duplicate
enhancement
faq
good first issue
grants
help wanted
might-come
needs design doc
needs investigation
no-stale-bot
out of scope
performance
policy 📝
pull-request
Mirrored from GitHub Pull Request
 question
regression
routes
stale
tags
tailscale-feature-gap
well described ❤️
wontfix
No Label bug stale
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/headscale#446
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?