I need to deploy a trigger.io app on a wifi net with a heavy firewall. What ports will the net need to have open to function properly?
I'm guessing the answer is ports 80 and 443, with outbound access to trigger.io and maybe (guessing here) reload.trigger.io.
Can anyone confirm the correct access requirements? Thanks!
All the reload requests are done over HTTPS (port 443), the domains accessed are trigger.io and s3.amazonaws.com.
That is unless you use the external reload feature, which downloads the resources from the domain you specify.
Related
I need to add webcheck monitoring in zabbix for some of my domains. But the problem is this urls will only can be accessed if we connect to the corresponding pritunl VPN Client.
Anyone please guide me on this?
Our firewall restricts outbound network connections. Hence we need to know the list of IP addresses to which we need to open up the port for outbound network connections that connects to Twilio for the REST API for sending sms.
How to find out what are the list of IP addresses that twilio uses for outbound connections so that we can open those in our firewall?
As per the Twilio docs it says we need to open up for https://api.twilio.com.
Unfortunately our firewall needs to define a list of IP addresses instead of a URL and it looks like the IP Addresses keep changing and is not static.
Does the following hold good for outbound connections from Twilio for Messages via their REST API?
https://forums.aws.amazon.com/ann.jspa?annID=1701
Please advise.
From the FAQ article on this topic:
Twilio makes HTTP requests to your server to fetch your app’s TwiML instructions. Some users prefer to know which IP address the request from Twilio is coming from in order to open up specific ports in a firewall. However, due to the fluid nature of our cloud architecture, we don’t have a set range of IPs that requests are sent from or know in advance what they will be.
Because Twilio’s requests will be coming from different IP addresses, we instead recommend that you validate that a request came from Twilio by other means. Please see our documentation on securing your application for more details.
If the inability to have a request come from a static IP address is a serious concern, please contact our sales department to discuss other options which might be available.
It's common when developing a web application to want to test it on mobile devices to ensure touch fallbacks and responsiveness.
As it happens, it's easy to do this over a Wi-Fi network. You just join the network on both your computer running the localhost and the mobile device you want to access it on and then enter the url on your mobile device:
http://<YOUR_COMPUTERS_IP>:3000
replacing <YOUR_COMPUTERS_IP> with your computer's ip address and 3000 with the port you are using.
This worked for basic routing.
The site i'm now working on however uses dynamic subdomains (users get their own subdomain) so is there any way to configure this to work with any subdomain?, so that you would be able to access
http://<SUBDOMAIN>.<YOUR_COMPUTERS_IP>:3000
on both your mobile and computer.
You can't put a subdomain onto an IP address directly, but there is a service called xip.io that was built to do just this.
http://<SUBDOMAIN>.<YOUR_COMPUTERS_IP>.xip.io:3000
I hope someone here had the question. I want to monitor one of iphone's application' internet (http) traffic, I know the application sends out http request but I can't monitoring them, so now what tool I should use?
I tried fiddler but it seems the I can only get the first few request, I lose the traffic right after I logged in within that application.
So I can use fiddler to monitor iphone's browser traffice without any issue, but for applications I can't.
Try Charles HTTP proxy debugger. There's even a section in the help for iOS applications.
If you want to debug HTTPS traffic as well you'll need to right click on the requests in the list and select SSL proxying and then re-attempt the request.
I am successfully seeing https traffic from a proxy setup on an iPhone to a wifi network so that it is routed through a desktop running fiddler. However, some http requests fail. I have all items checked under options > https. Ideas?
See http://groups.google.com/group/httpfiddler/browse_thread/thread/55b865509faaf119
Short answer is that a different certificate generation strategy is needed to interoperate with iOS based products. This will be coming in the next few weeks.