I have built a production NextJS (v11.1) web-app with React (v17.0.2). I then compiled a Docker (v20.10.8) image on an Apple MacBook Air M1 using buildx to ensure compatibility with amd64 processors. I then deployed the image to AWS EC2 on Ubuntu 20.04 with an x86_64 processor. I am also using Node (v14.17.5), Apollo Client (v3.4.8), GraphQL (v15.5.1) and finally NGINX (v1.18.0) as a reverse proxy server.
The image successfully deployed. I can visit my webpage on a laptop (macOS Big Sur v11.5.2) over WiFi, on an iPhone (iOS v14.7.1) over WiFi, and on Android phones with either WiFi or a cellular connection. Unfortunately, I cannot visit my webpage on an iPhone over cellular connection. I was hoping that connecting to the webpage on my laptop, but through the iPhone's hotspot feature would provide more insight. However, the page failed to load and I still didn't see much useful information.
To the best of my knowledge each technology is using the latest, stable version. Does anyone know why a NextJS web-app would fail to load specifically on an iPhone using a cellular connection? Or even have additional insight into how I might debug this issue?
Yes. The problem was that I had disabled NGINX support for IPv6, while I had forgotten to disable IPv6 support in Route 53 / AWS. I chose to disable IPv6 and the issue is resolved.
Related
My App has now gotten rejected twice for not working on an IPv6 network on a device running IOS 10.2 My App was built using these resources and I was hoping someone could give me some insight on where to start looking.
Server:
Amazon EC2 t2.micro
IP address is IPv4 however the server says IPv6 is enabled
All traffic is allowed in security groups
Windows Server 2016
Libraries:
LibGDX 1.9.5
Kryo 2.23.1-SNAPSHOT
Kryonet 2.18
MobiDevelop's RoboVM fork 2.3.0
Please let me know which of these is most likely the culprit so I can proceed to fix it thank you!
I got this fixed. I was originally connecting to my servers by the IP address and have now switched it to the DNS. Works fine and made it through app review!
I developing a mobile application using React Native. For testing, I run the application on a physical iPhone which means pointing the device to the React Native server running on port 8081 of my laptop. As a remote developer, I often work in coffee shops, libraries, or other public places with WiFi.
My issue is some of these public places block traffic between devices so even if the phone and development machine are on the same network, the mobile device is unable to reach the React Native server.
One remedy I have found is to create a private network between the iPhone and my Macbook. While this solved the issue of connecting to the React Native server, it cuts my laptop off from a public internet connection so this is not a viable option.
Is there a solution to this problem which retains a public internet connection for my devices and also allows comunication between the phone and the React server?
https://ngrok.com allows you to setup secure tunnels to localhost that you can access on the public internet.
Test mobile apps against a development backend running on your
machine. Point ngrok at your local dev server and then configure your
app to use the ngrok URL. It won't change, even when you change
networks.
I have searched high and low for a solution to this which I am sure must exist but I have failed to find one that works.
I am running XCode 7.3 and iOS 9.2 on an iPhone.
I have a test server running on 127.0.0.1:8000
I cannot get my app running on the iPhone to connect to either 127.0.0.1:8000 or 192.168.1.200:8000 (which is the local ip address of my server).
There must be a way to give the iPhone app access to the local server if only I knew how!
The best solution to this problem, that many app developers have, is to download ngrok which acts as a proxy website.
ngrok is insanely easy to use:
Download from https://ngrok.com/
Run: ngrok http 8000 in terminal (where 8000 is your port)
Cut and paste the displayed ngrok url (e.g. http://a021v2tc.ngrok.io) into your app
So simple. And works!
Check if iPhone connect the same wifi with your server.
You can use Fiddler as iPhone agent to get the detail error message.
There is the link how to capture traffic from IOS device.
here
I am developing a backend server for an app using PyCharm. This runs on my laptop as 127.0.0.1:8000
I need to access this server for testing from an iPhone. This is connected by wifi to my local network to which the laptop is also connected.
I have tried entering http://mycomputer.local:8000 in safari on the iPhone but I get the message "Safari could not open the page because the server stopped working. I am using the real name of my computer instead of 'mycomputer'.
I am running OS X Yosemite so Web Sharing is not available in System Preferences.
How can I give access to the 127.0.0.1:8000 server to my iPhone?
When you say "backend server", what is the Python project written in? Django, Flask, Pyramid, something else?
I am using Android ICS 4.0.4 source code for enabling the Wi-Fi Direct and run on i.MX6 board with Wi-Fi module which supports marvell 8787 chipset.
I was able to make the wfd0 interface up for wifi direct but the other p2p operations such as device discovery was failing.
I was using WEXT as driver interface .After googling I came to know for the p2p operations nl80211 must be used.
I changed the configurations from WEXT to nl80211. But the wpa_supplicant stopped working.Even though I am starting the wpa_supplicant service from init.rc file the wpa_supplicant does not seems to be running.
Does Android ICS 4.0.4 provide a complete support for Wi-Fi Direct?
Could anyone help me with this issue. ?
The support for Wi-Fi Direct on Android has began for the 4.1 version (source).
Moreover, as you said, the WEXT drivers does not support P2P. So you have to use nl80211 drivers. But are you sure that your device have a valid nl80211 driver?
If you want to known why your wpa_supplicant is crashing, you can start it by hand in a shell without the -B option and with the -dd option and check the log.