SVI/netbird
1
0
Fork 0
mirror of https://github.com/netbirdio/netbird.git synced 2026-08-04 19:55:09 -04:00
Code Issues 3.0k Packages Projects Releases 10 Wiki Activity

ios app can't connect when use mobile network #576

New Issue
Closed
opened 2025-11-20 05:14:02 -05:00 by saavagebueno · 11 comments
saavagebueno commented 2025-11-20 05:14:02 -05:00
Owner
Copy Link

Originally created by @NatureLR on GitHub (Jan 10, 2024).

Describe the problem

ios app can't connect when use mobile network

截屏 2024-01-10 16 11 15
Snipaste_2024-01-10_16-10-02

Originally created by @NatureLR on GitHub (Jan 10, 2024). **Describe the problem** ios app can't connect when use mobile network ![截屏 2024-01-10 16 11 15](https://github.com/netbirdio/netbird/assets/30221928/b4005837-951a-4b3e-bc48-0ca15e9c05e8) ![Snipaste_2024-01-10_16-10-02](https://github.com/netbirdio/netbird/assets/30221928/6fd17ad7-628f-46d0-a8d7-3e8d50dad4b2)
saavagebueno added the bugioswaiting-feedback labels 2025-11-20 05:14:02 -05:00
saavagebueno commented 2025-11-20 05:14:03 -05:00
Author
Owner
Copy Link

@oldwang12 commented on GitHub (Jan 10, 2024):

I had the same problem on my iphone, fuck iphone.

@oldwang12 commented on GitHub (Jan 10, 2024): I had the same problem on my iphone, fuck iphone.
saavagebueno commented 2025-11-20 05:14:03 -05:00
Author
Owner
Copy Link

@surik commented on GitHub (Jan 10, 2024):

Hi @NatureLR and @oldwang12, this is some limitation we already identified. We will be working on solving this soon.

@surik commented on GitHub (Jan 10, 2024): Hi @NatureLR and @oldwang12, this is some limitation we already identified. We will be working on solving this soon.
saavagebueno commented 2025-11-20 05:14:03 -05:00
Author
Owner
Copy Link

@surik commented on GitHub (Jan 10, 2024):

Also, as I see this is self-hosted. Can you confirm that your relay service is configured properly?

To test your TURN configuration by accessing the link https://webrtc.github.io/samples/src/content/peerconnection/trickle-ice/. There you will find an ICE servers input box, where you can select and remove the existing server, then add your turn server configuration as follows:

Please replace netbird.DOMAIN.com and PASSWORD with the information from the management.json TURNConfig, then click on Add server.

Run the candidate gathering by clicking on Gather Candidates.

@surik commented on GitHub (Jan 10, 2024): Also, as I see this is self-hosted. Can you confirm that your relay service is configured properly? To test your TURN configuration by accessing the link https://webrtc.github.io/samples/src/content/peerconnection/trickle-ice/. There you will find an ICE servers input box, where you can select and remove the existing server, then add your turn server configuration as follows: Please replace [netbird.DOMAIN.com](http://netbird.domain.com/) and PASSWORD with the information from the management.json TURNConfig, then click on Add server. Run the candidate gathering by clicking on Gather Candidates.
saavagebueno commented 2025-11-20 05:14:03 -05:00
Author
Owner
Copy Link

@NatureLR commented on GitHub (Jan 10, 2024):

Also, as I see this is self-hosted. Can you confirm that your relay service is configured properly?

To test your TURN configuration by accessing the link https://webrtc.github.io/samples/src/content/peerconnection/trickle-ice/. There you will find an ICE servers input box, where you can select and remove the existing server, then add your turn server configuration as follows:

Please replace netbird.DOMAIN.com and PASSWORD with the information from the management.json TURNConfig, then click on Add server.

Run the candidate gathering by clicking on Gather Candidates.

yes,i use getting-started-with-zitadel.sh deploy my server

Snipaste_2024-01-11_10-42-55

@NatureLR commented on GitHub (Jan 10, 2024): > Also, as I see this is self-hosted. Can you confirm that your relay service is configured properly? > > To test your TURN configuration by accessing the link https://webrtc.github.io/samples/src/content/peerconnection/trickle-ice/. There you will find an ICE servers input box, where you can select and remove the existing server, then add your turn server configuration as follows: > > Please replace [netbird.DOMAIN.com](http://netbird.domain.com/) and PASSWORD with the information from the management.json TURNConfig, then click on Add server. > > Run the candidate gathering by clicking on Gather Candidates. yes,i use `getting-started-with-zitadel.sh` deploy my server ![Snipaste_2024-01-11_10-42-55](https://github.com/netbirdio/netbird/assets/30221928/47921f2d-bd28-4f9f-9d08-1e4f84a58654)
saavagebueno commented 2025-11-20 05:14:03 -05:00
Author
Owner
Copy Link

@Ben7on commented on GitHub (Jan 11, 2024):

I believe I had the same issue. After some support from the team on slack, I was able to resolve it.

You need to add the public ip of your server in the turn configuration file as follow:

externalip=193.224.22.37

As seen in your screenshot, your turn server currently advertise an internal ip:

Screenshot 2024-01-11 at 14 45 27

@Ben7on commented on GitHub (Jan 11, 2024): I believe I had the same issue. After some [support from the team on slack](https://netbirdio.slack.com/archives/C05T5K65X7U/p1704320426366559), I was able to resolve it. You need to add the public ip of your server in the turn configuration file as follow: `externalip=193.224.22.37` As seen in your screenshot, your turn server currently advertise an internal ip: ![Screenshot 2024-01-11 at 14 45 27](https://github.com/netbirdio/netbird/assets/58401596/e18e72ba-7203-4263-b48d-5f66be23a562)
saavagebueno commented 2025-11-20 05:14:04 -05:00
Author
Owner
Copy Link

@NatureLR commented on GitHub (Jan 11, 2024):

I believe I had the same issue. After some support from the team on slack, I was able to resolve it.

You need to add the public ip of your server in the turn configuration file as follow:

externalip=193.224.22.37

As seen in your screenshot, your turn server currently advertise an internal ip:

Screenshot 2024-01-11 at 14 45 27

oh Successful ！！！ 😄

i add external-ip=<eip> to turnserver.conf and use

docker compose up -d --force-recreate coturn
@NatureLR commented on GitHub (Jan 11, 2024): > I believe I had the same issue. After some [support from the team on slack](https://netbirdio.slack.com/archives/C05T5K65X7U/p1704320426366559), I was able to resolve it. > > You need to add the public ip of your server in the turn configuration file as follow: > > `externalip=193.224.22.37` > > As seen in your screenshot, your turn server currently advertise an internal ip: > > ![Screenshot 2024-01-11 at 14 45 27](https://private-user-images.githubusercontent.com/58401596/295934470-e18e72ba-7203-4263-b48d-5f66be23a562.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MDUwMjc2MjEsIm5iZiI6MTcwNTAyNzMyMSwicGF0aCI6Ii81ODQwMTU5Ni8yOTU5MzQ0NzAtZTE4ZTcyYmEtNzIwMy00MjYzLWI0OGQtNWY2NmJlMjNhNTYyLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDAxMTIlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwMTEyVDAyNDIwMVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTk3ZTkxMTdmMTlkODY3ZWQwMjFjNGFhZTRiNmRiYjliYjI3ZmNjN2Y0YTI2M2JkMzM5MGE0MmNjMDNmZThjODgmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.deE2DUzqCdlFtuyZZazbuSImDHTJv5BtQpo-xMjFxn0) oh Successful ！！！ 😄 i add `external-ip=<eip>` to turnserver.conf and use ```shell docker compose up -d --force-recreate coturn ```
saavagebueno commented 2025-11-20 05:14:04 -05:00
Author
Owner
Copy Link

@jiangslee commented on GitHub (Jan 15, 2024):

I believe I had the same issue. After some support from the team on slack, I was able to resolve it.
You need to add the public ip of your server in the turn configuration file as follow:
externalip=193.224.22.37
As seen in your screenshot, your turn server currently advertise an internal ip:
Screenshot 2024-01-11 at 14 45 27

oh Successful ！！！ 😄

i add external-ip=<eip> to turnserver.conf and use

docker compose up -d --force-recreate coturn

It works for me too!!!

@jiangslee commented on GitHub (Jan 15, 2024): > > I believe I had the same issue. After some [support from the team on slack](https://netbirdio.slack.com/archives/C05T5K65X7U/p1704320426366559), I was able to resolve it. > > You need to add the public ip of your server in the turn configuration file as follow: > > `externalip=193.224.22.37` > > As seen in your screenshot, your turn server currently advertise an internal ip: > > ![Screenshot 2024-01-11 at 14 45 27](https://private-user-images.githubusercontent.com/58401596/295934470-e18e72ba-7203-4263-b48d-5f66be23a562.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MDUwMjc2MjEsIm5iZiI6MTcwNTAyNzMyMSwicGF0aCI6Ii81ODQwMTU5Ni8yOTU5MzQ0NzAtZTE4ZTcyYmEtNzIwMy00MjYzLWI0OGQtNWY2NmJlMjNhNTYyLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDAxMTIlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwMTEyVDAyNDIwMVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTk3ZTkxMTdmMTlkODY3ZWQwMjFjNGFhZTRiNmRiYjliYjI3ZmNjN2Y0YTI2M2JkMzM5MGE0MmNjMDNmZThjODgmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.deE2DUzqCdlFtuyZZazbuSImDHTJv5BtQpo-xMjFxn0) > > oh Successful ！！！ 😄 > > i add `external-ip=<eip>` to turnserver.conf and use > > ```shell > docker compose up -d --force-recreate coturn > ``` It works for me too!!!
saavagebueno commented 2025-11-20 05:14:04 -05:00
Author
Owner
Copy Link

@collse commented on GitHub (Aug 16, 2024):

unfortunately this solution only works with fixed ip addresses and not with dynamic IPs

@collse commented on GitHub (Aug 16, 2024): unfortunately this solution only works with fixed ip addresses and not with dynamic IPs
saavagebueno commented 2025-11-20 05:14:04 -05:00
Author
Owner
Copy Link

@SvenSapphire commented on GitHub (Aug 23, 2024):

Unfortunately this doesn't work for me. I double checked the TURN configuration and the test indicated the correct IP-Address. This behavior only appears on cellular connection.
I can exclude the DNS and Network-Route functionality because turning them off will not resolve the issue.

Now the interesting part:
If I connect my Mac with mobile hotspot to the iPhone, the Mac can connect to the peers without any problem. So I guess the problem is in the iOS app itself.

@SvenSapphire commented on GitHub (Aug 23, 2024): Unfortunately this doesn't work for me. I double checked the TURN configuration and the test indicated the correct IP-Address. This behavior only appears on cellular connection. I can exclude the DNS and Network-Route functionality because turning them off will not resolve the issue. Now the interesting part: If I connect my Mac with mobile hotspot to the iPhone, the Mac **can** connect to the peers without any problem. So I guess the problem is in the iOS app itself.
saavagebueno commented 2025-11-20 05:14:04 -05:00
Author
Owner
Copy Link

@nazarewk commented on GitHub (Apr 28, 2025):

Hello @NatureLR,

We're currently reviewing our open issues and would like to verify if this problem still exists in the latest NetBird version.

Could you please confirm if the issue is still there?

We may close this issue temporarily if we don't hear back from you within 2 weeks, but feel free to reopen it with updated information.

Thanks for your contribution to improving the project!

@nazarewk commented on GitHub (Apr 28, 2025): Hello @NatureLR, We're currently reviewing our open issues and would like to verify if this problem still exists in the [latest NetBird version](https://github.com/netbirdio/netbird/releases). Could you please confirm if the issue is still there? We may close this issue temporarily if we don't hear back from you within **2 weeks**, but feel free to reopen it with updated information. Thanks for your contribution to improving the project!
saavagebueno commented 2025-11-20 05:14:04 -05:00
Author
Owner
Copy Link

@mlsmaycon commented on GitHub (Jun 1, 2025):

closing issue due to no recent feedback. Feel free to open a new one if the issue persist or reopen if this was a feature request.

@mlsmaycon commented on GitHub (Jun 1, 2025): closing issue due to no recent feedback. Feel free to open a new one if the issue persist or reopen if this was a feature request.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
2021 Q4
2022 Q1
2022 Q1
accessibility
acl
agent
agent
Android
Android
api
authentik
automation
azure
battery-usage
bug
cache
client
client-ui
cloud
cloud-only
cloudflare
community
compatibility
config-idp
config-issue
connection
contribution
coturn
cross-vpn
dashboard
data-usage
distribution
dns
docker
documentation
duplicate
enhancement
enhancement
event-stream
feature-request
freebsd
getting-started
go
good first issue
gui
help wanted
home-assistant
idp
inconsistency
integration
integrations
ios
ipv6
jwt
k8s
keycloak
linux
login
macos
management-service
missing-docs
mobile
moved-internal
needs-review
netbird-ui
networking
new-platform
nginx
notification
okta
openwrt
packaging
peer-management
peer-management
peer-management
performance
postgres
posture-checks
psk
pull-request
Mirrored from GitHub Pull Request
 question
refactor
relay
release
rfc
routes
security
security-related
self-hosting
server
signal
sleep-issue
ssh
ssl
status
store
synology
system-compatibility-issue
test-suite
third-party-integration
triage
triage-needed
troubleshooting
UX
waiting-feedback
windows
wontfix
zitadel
No Label bug ios waiting-feedback
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/netbird#576
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?