Can't Access Server With Using 3g, 4g or LTE - node.js

I have a Node.js server and mobile React Native client application.
After switching to static ip, I can not connect to application server using mobile data. Mobile devices or computers which uses wifi can take response from my server but any device using mobile data can not. If my client application switch to wifi it reaches server perfectly but when I switch back to mobile data it throws 'network error'. Additionally anyone using mobile data can reach server with Chrome Mobile but other mobile browsers can't.
Summary:
Chrome can access server with wifi, 3g, 4g, LTE.
My application and any browser can access server with wifi.
My application and the browsers except Chrome can not access server with 3g, 4g and LTE.
I am really confusing about this situation. Can this problem related with internet provider? or I need to add same configuration to server application for coming request from who uses mobile data? any ideas? Sorry for my bad English.

Related

Can i run flutter web build offline

I have a Flutter Web Application which uses a NodeJS and ExpressJS server as a backend. I have deployed this application on a server which is connected to a LAN. When I browse to the server on a computer which has permission to access the internet, the application works fine. But when I browse to the website on a computer with no internet connection, it gives me an error:'Failed to load resource:net::ERR_CONNECTION_RESET canvaskit.js:1'.
Do i always need to have internet access for a Flutter Web Application to work? Can I make the app work without internet connection?

secure connection from mobile device to application server

I am after a little bit of help.
I have a mobile application that currently runs on both iOS and Android. this application uses in house APIs to do most of the back end work.
I have a need to start using some legacy services that sit within the back end servers in my company.
I have proposed that we use a new application server that will sit in the DMZ and this will run an application that will contact the services and get me the data i need.
My question is how can i ensure that the connection from the Mobile device to this application server is secure? what protocol should i use?
thanks in advance.
If the Application Server exposes an HTTP-based end-point which the Mobile app calls, then it can be secured by SSL. Based on the flavor of your Application Server, look into how to setup an SSL-endpoint and your mobile app can then talk to the SSL-enabled HTTP endpoint (HTTPS).

webapp wont connect over mobile networks

I have setup a webapp to work with websockets.
This webapp worked fine over local/wired network.
I realiced (maybe im wrong) that websockets cannot work over mobile network 3G/4G because of ISP proxies. But then i saw that secured connection pass through mobile networks proxies (https://github.com/websockets/ws/issues/257).
So i created a simple self signed cert using openssl.
Finally my application works over https to host WSS protocol. So now i tried to connect with my phone using 4G but page does not load. But it works perfectly over WIFI connections, also with my desktop PC.
https://ciroreed.net:8080/
Can i provide other useful information?
EDIT
The problem was that mobile networks sometimes wont load ws:// protocol.
We solve this setting up an https server, and ofc use wss protocol also.this package for sockets https://www.npmjs.com/package/ws
To ensure websocket works here is my advice:
use wss, not ws
use a valid signed certificate
check your wss endpoint with ssllabs.com (especially for missing intermediate certificate, the most common error)

WP8 app with large signalr component only works on Emulator

I have a SignalR enabled Web API server on Azure, and I have created a Windows Phone 8 client app that works perfectly well with the server on my WP8 Emulator.
After deploying to my Nokia Lumia 925 device, none of the components that demonstrate Server - Client push work.
Like, literally, nothing Signal R works on the app, but when I run it again on my Emulator everything works.
I just don't get what is going on.
I need help, please.
Thanks
UPDATE
The REST API and the SignalR powered streaming API are live on Azure.
Basically, I can make posts to the rest API, but then the Streaming API which is meant to broadcast that post to all connected clients including the originating client fails on the deployed device, but not on the emulator.
Could be proxy/connection related.
On the emulator you could be using a debug/emulated version of your Azure Service in which case the WP8 client app can see it fine. You may want to make sure the WCF Service has actually been deployed to Azure it is accessible over the web and its not actually pointing to locahost.
Then once your sure of all that just make sure your phone's browser can see the services end-points on azure and the client app should see it fine.
Maybe also try using Fiddler to see what network traffic is coming from your emulator and also the app once on-device. Also check you're not trying to hit "localhost" once deployed to your device. See here for how to use Fiddler with WP8 emulator and devices: http://www.spikie.be/blog/post/2013/01/04/Windows-Phone-8-and-Fiddler.aspx

Restrict Web App Access to a set of tablet computers

A client has asked for additional security for a web app which would allow only company owned and approved tablet computers (brand not yet known) to connect to a PHP web app.
The app will be un/pw protected but the company would like to prevent all access except via the tablets.
MAC addresses would be great for this but these will be used in the field and use a myFi portable wifi to connect to the server so the MAC address will not be available.
Can anyone point me to a sound method for this secondary validation?
Your best solution here would be to deploy mutually-authenticated SSL between your client tablets and your server. You can use self-signed certificates here so you don't need to buy any from a CA. This will ensure that your server only accepts requests from tablets that have the client-side certificate (configure your server to only accept the self-signed client certificates deployed on your tablets for client authentication).

Resources