I am trying to reach a clients API in the code. I suceed establishing connection using Postmand. But when I send them my Devboxs public IP to be whitelisted eg: 52.xxx.xxx.165 but the calls thy get come from a completely different ip eg: 52.xx.xx.129 - and after whitelisting that IP i can then connect to the API without a problem through Postman. But when trying to reach it directly through Visual Studios, with both IPs whitelisted, i get the error that i am not autorizised (IP not whitelisted).
Which IP does Visual Studios in Devbox use when calling and API? How can I find out?
Related
Is it possible to use domain or localhost with serverless-appsync-simulator endpoint?
I don't want the endpoint to change.
When I start simulator, it uses a private IP address (192.168.x.x:20002/graphql) for the endpoint.
So restarting the PC will change the endpoint.
I want to connect watson assistant to an API running on a server. But I don't know why it gives the error "Invalid URL".
192.168.*.* is a private IP address. Watson won't be able to access it. You need a publicly accessible URL. For testing purposes, you can expose your server via something like ngrok.
I have Outbound IP range from partner system(server) whose HTTPS URL we are trying to connect to transfer files but since no APIs are involved , how to check if IP's are whitelisted or is it any way to Whitelist that IP range in anypoint Studio7 using Mule4
Not finding way to do it via Anypoint studio as my code is deployed locally and not on any CloudHub or on-premise as of now, as its just a POC
It is the other way around. The other side, which exposes the HTTPS service you are connecting to, restricts access to their service by whitelisting some IPs. If your IP, from where you connect to the service, is whitelisted, then you will be able to connect to it. If not, you might not even get an error response. It is up to the side whitelisting, which is usually the server.
I have the starting shell of a SMAPI service programmed in Node.js. The service is running off of a local IP address.
When I goto the customSD page for my Sonos Play:1 and add the service details to it and it returns 'Success!' upon clicking submit.
When I open the Sonos Controllers on both my desktop and mobile, the service does not show up in the list of music services you can add.
I have logging on the server turned on to max and there are no connection attempts ( either SSL or HTTP ) at all.
From what I've read, a running service is not needed for it to show up in the list. Once it's added via customSD it should show up in the Music Service settings.
TO NOTE: A self signed cert is being used for https for connection testing only. I have certificate request logging turned on and there is NO connection attempt from the Sonos Play:1 to the local server at all. From everything I've read this shouldn't matter as it should show up in the Music Service list until you try to add it and then it will connect to the service.
The only thing I can think of is if this service needs to be registered with Sonos before it can be added via customSD, however at this time nothing I've read says that.
The other thing is if this service needs to be running off a domain name for some reason. However in the documentation it lists IP address so it would be bad documentation then.
I expect the service added via customSD should show up in the list. It does not appear when clicking on add.
Understood the issue and YvesGrantSonos has updated the documentation.
If you're developing locally a non-https IP address should be used for both the secure and non-secure API URI's.
You should be able enter a local IP address for the SMAPI service. For testing, this should be on the same local network as the Sonos player. Be sure to include the port number that the service is running on (i.e. http://192.168.1.2:8080/musicservice). You can use the same IP and port for secure and insecure connections.
Are Shared hosting IP OK for Mandrill API Requests?
I'm trying figure out if a Nightmare is true or simply pure work overload. :)
Mandrill comes with a Shared and Dedicated IP Options for sending out emails. What I fully 100% agree with. But do I need a Dedicated IP for sending out API Requests to Mandrill? Or can Shared Hosting IP work as a starting point. (e.g Bluehost / Hostgator Shared Plans ).
Is there a possibility, that tow Account will use the same IP and lead to very Angry Mandrill? :{
I am planing to apply for a Dedicated IP. But would like to not rush with buy every feature to quickly.
The Mandrill dedicated IP option is an IP that is only used for sending your emails. You don't make API calls to that address. You would still make API calls to the same API endpoint described in the Mandrill API docs - with a dedicated IP, once we receive and process your mail, we would then route it over a dedicated IP address instead of the shared pool of sending IP addresses. All of the sending IPs are only used for sending emails. They aren't used for other portions of the application or API.