The error I am receiving is: Connection to http://localhost:8081/debugger-proxy?role=client timed out. Are you running node proxy? If you are running on the device, check if you have the right IP address in RCTWebSocketExecutor.m
I have tried changing from localhost to my computer's ip address as mentioned in other stackoverflow post's but it still doesn't seem to be working.
Related
Before updating to Mac OS Monterey I was able to connect to localhost and any port as long as I was on the same internal network. However this no longer seems to be working.
I have also tried to access via xxxx.local which only prints an html page that says "It Works!" which is located in /Library/Documents/WebServer/index.html.en. But if I navigate to any port, things just seem to just hangup.
Steps taken:
System Preference > Network > IP Address
Connect device to same network
Enter in ipaddress:port into browser
Get failed to connect message.
Suggestions?
I have a server running on localhost:5000 on my desktop, and when I make http requests through my react-native app when running on the iOS simulation to it, it works. However, when I connect to a real device, the http requests don't work. What am I doing wrong? Is there something I have to configure?
localhost in your desktop is not the same ip of the localhost of your device.
Get the ip of your computer by typing ifconfig in a terminal, then replace localhost by this ip, you should type something like that in your device browser:
192.168.0.23:5000
Maybe my answer is too late but I ran into a similar situation today and I got it to work by running my node server using the IPv4 of my desktop and then making the request to that IP.
For example, I am running my nodejs development server at http://192.168.0.135:3000(local IP of my desktop) instead of localhost and then I make the fetch API request from my react-native app to http://192.168.0.135:3000/.
Just make sure your nodejs server and your app are on the same local network. My react-native server (metro bundler) is running on a separate PC also in the same wifi network.
If your are on macOS go to settings -> Wifi / and show more,
on bottom you see "IP address", it's your correct localhost for ios physical device !
I've been testing my project on my iPhone6s and it worked perfectly. But today Xcode and Node.js keeps giving me the 'Unable to execute JS call: __fbBatchedBridge is undefined' error.
I'm sure the IP address is correct, my phone is under the same Wifi network with server. The simulator works fine with the server ip. To test if it is something wrong with the project I start another AwesomeProject and changed the IP but still not working. Anyone know any possible solutions?
I faced the same issue in my office Wifi network connection also. This is because of the router configuration. There are two ways to make it work.
Expose the local server using ngrok. But, It will be slow since it is sending everything to server.
Connect your phone using USB cable and type the following command in the computer adb reverce tcp:8081 tcp:8081
I'm trying to run a Xcode server with remote access.
I've been trying to log in from a client/node PC, with no success. There's a message with the IP and a warning "No services unavailable".
Is there something I'm missing here?
Screenshot is attached.
Thanks.
Since from attached picture everything is running perfectly locally, I'm almost sure that the problem is in your router. So on router in port forwarding you have to open:
For Xcode Integration the only ports needed are 20300,20343-20345
For Website 80,443
And you have to make sure that you're have global IP address
I did install Opennms in a VM Ubuntu on PROXMOX. Everything went well until I did change the interface IP address because the VM must work in a LAN without Internet access. Since then the opennms start correctly but the browser give me the error:
Jetty: HTTP ERROR: 503
Problem accessing /opennms/. Reason:
Service Unavailable
The problem seems to be related with the connection to Internet at the starting of opennms. When I start opens without Internet connection the server do to start correctly.
OpenNMS has a bugfix that may take care of it.
http://issues.opennms.org/browse/NMS-7683