New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error starting tunnel: Error: Error: failed to start tunnel #283
Comments
The tunnel software we use is ngrok (https://ngrok.com) so I'd try testing ngrok out to make sure it works on your computer before spending more time. (XDE and exp have a LAN option where your project URLs contain LAN IP addresses instead of the exp.direct tunnel URLs.) If ngrok works I'd recommend a few things while debugging:
|
Thanks for your help, James. I tried running ngrok and it works without issues. When I try to load the URL from the Expo client through the browser, I get Could there be communication issues with |
@mariotacke Is your Expo username mariotacke.mobile? I'm wondering if it has a dot in it and if that's messing up the subdomain.... |
Nope, it is only |
I switched back and forth between
|
|
Interesting. I wonder where the Not sure if this could be related to the |
Is your project slug called "mobile"? I think that might be where it came from. Glad to hear it is working for you now and sorry about the temporary unavailability. Will close this issue now. |
No, my project slug is "manifest" (product name), my actual project folder is "mobile" (git). Who knows what happened, I'm glad it is back to normal. :) |
I also had this problem today. It looks like sometimes |
Expo and react-devtools conflict!!! If you are using react-devtools, you must uninstall it: |
Neither the tunneling nor LAN have been working all day, but without even changing anything tonight the tunneling suddenly works again. Any idea why this happens? |
|
running ngrok.exe in the background, appears to be the workaround |
wow...... I needed this so bad. Might be worth adding a warning? |
@gregbenner delete devtools works for me |
I believe there are multiple causes for the 'Error: failed to start tunnel' notification is shown - for me (on windows 10), I realized that the error didn't come up and tunnel url was successful when a physical android was plugged in for debugging. My attempts to deploy to 'genymotion' continued to get the 'failed to start tunnel' notification until I added the android 'platform-tools' directory to my path. It must be looking for adb and can't find it unless this is done. Not having the 'platform-tools' added to my path is what was causing the error on my system. |
"We noticed your tunnel is having issues. This may be due to intermittent problems with our tunnel provider. If you have trouble connecting to your app, try to Restart the project, or switch Host to LAN." please help me solve this error. |
Hi @vikulkumar123, have you tried restarting the project, switching host to lan and all other tips above? |
I was somehow able to identify the problem. You just need to do ipconfig /all (windows) or ifconfig (unix) and check for Wireless LAN adapter WIFI IPV4 Address and replace the host in exp URL with it. exp://192.168.84.161:19000 (This published URL on expo start was using ethernet IPV4 adress instead of Wireless LanIPV4 192.168.0.10) Changing the host and directly hitting it on safari opens a expo app and loads the react app successfully Hope this will help everyone facing this problem. |
Start getting |
I've been happily developing all day through the Expo tunnel feature until I restarted my project. I receive a valid
exp://
link, but the device says "No experience can be found at ...". I have restarted my Expo XDE and tried starting through theexp
CLI. I tried clearing the Expo XDE cache to no avail.The Expo XDE client log shows:
Any idea how to further debug this? It looks like the packager starts properly and the tunnel URL gets created.
I ran a
netstat
to look for any orphaned process that blocks the port, but I got nothing.System: Windows 10
SDK: 17.0
The text was updated successfully, but these errors were encountered: