Use Paypal webhooks simulator in nodejs - node.js

I'm try to send events from webhooks simulator to test my app I provided the URL and select the event from dropdown and click send it show event is successfully queued ... waiting few minutes but not got anything to that URL. Can you please let me know why it's not sending anything I tried different events but nothing happen

Without knowing what the webhook URL is, we can't comment specifically, but typical problems are:
Non-standard port (must be https on 443)
Firewall issue (must be publicly accessible)
A domain PayPal cannot resolve or connect to (try a different domain or IP address)

Related

IFTTT Webhooks doesn't allow localhopst

I am trying to build something that will allow IFTTT to send a web request to a localhost (127.0.0.1:8080) using webhooks. I have a web server running on my android device for this reason. The web server will then parse the request and forward this to the Tasker application as an event. My Kronaby watch has the ability to activate an IFTTT applet with a button push. In order to expand the possibilities, I am trying to integrate Tasker via a webhook.
The current issue I have is that webhooks doesn't allow requests to 127.0.0.1 per the error I am getting.
In the end my question would be how I could get IFTTT to send an action to Tasker.
How would the IFTTT service - running on their servers know how to resolve your localhost (not running into their servers)?
I think you need to expose your server's IP address to (eg) IFTTT. Probably scary.

GraphQL subscription does not receive messages after successful handshake

I have created a simple GraphQL Subscription using Nest.js/Apollo GraphQL over Node.js. My client application which is a react.js/apollo client works find with the server. The client subscibes to the server via GraphQL similar to:
subscription
{
studentAdded
{
id
}
}
My problem is that it works only locally. When I deploy my server back-end to a hosted docker over internet, client won't receive data anymore.
I have traced the client, it sends GET request on ws://api.example.com:8010/graphql and receives the successful HTTP/1.1 101 Switching Protocols response. However, nothing is received from server like when the server was on my local machine. Checking the remote server log showed me that the client successfully connects to server. There, I can see onConnect log messages.
Now I need any guidance to solve the problem.
I check several things myself. Firstly, I thought WebSocket address is prohibited in the network but then realized that it is on same port as normal HTTP. Secondly, supposed that WebSocket messages/frames are transmitted over UDP but I was not correct, it is over TCP and no need to worry about network settings.
Additionally I have read several github threads and StackOverflow questions. But did not find any clue. I am not directly using Node.js/WebSocket, instead, I am using Nest.js/GraphqQL subscription. It has made my search tougher.
Your help is highly appreciated.

How did an IP send Get requests to my code?

I am new to web development. I am developing a flask web server on my linode linux web server on port 5000. I got this output from an unknown ip. I researched the ip and found out that this is a whitelisted IP address and is "harmless", but I dont know. It looks like it sent GET requests to my cover photo, the javascript, the css, an icon on the page, and an unknown request. What does sending a GET request to these items even entail? I dont have any button or anything that sends a get request to these items. Whenever I am developing the web server while on port 5000 I am usually the only IP on the output. Additionally, this web server communicates with a raspberry pi over mqtt over the non-encrypted port 1883.
Again, I am new to this world and am wondering if anyone can help me decipher what this means that would be very helpful. In the meantime should I will configure the servers firewall to only allow requests from my computers ip to my server? Anyone think this is a reasonable next step or have any additional advice?
I believe what's happening is that your website is sending a GET request to retrieve those assets (e.g. your images) which are stored under your localhost address and the paths that you see in the console output.

Spotify spotilocal.com removed?

I am currently testing with the Spotify API. Saterday I was able to send a request to https://79777278.spotilocal.com:4371/simplecsrf/token.json (a local Spotify webserver) i updated to version 10.0.62 and it didn't respond anymore. On my other pc (version 10.0.60) its working perfectly. I tried sending the request to https://172.0.0.1:4371/simplecsrf/token.json but I got a connection timeout.
Does anybody know if this API is moved or removed?
It might have been removed. Going to http endpoint directly by ip address a few ports up probably still work. http://127.0.0.1:4381/simplecsrf/token.json

Limit dev environment to e-mail only certain domains for testing (XP smtp IIS)

I'm developing a website on an XP virtual machine and have an SMTP virtual server set up in IIS -- it delivers mail just fine. What I would like is to confirm that any emails the site sends are only going to a specific domain.
The XP firewall seems to only involve incoming connections, I can't block outgoing TCP on port 25. And I haven't been able to configure the SMTP server to filter by delivery address.
With this setup, is there any easy way to filter outgoing email by destination address?
Here's one idea:
Under Advanced Delivery options (SMTP Virtual Server Properties > Delivery tab > Advanced). There you can set a "Smart Host" which is the SMTP server that will be used to actually send the mail, so you could possibly have it deliver directly to the specific domain's incoming SMTP server.
I think the easiest way would be to add a check to your mail sending code on the website (there's got to be some class which is in charge of sending the mails out).
You could include a check which is only active when the code is compiled in debug mode (using compiler directives). Thus, when you are developing and building the site in debug mode, this code checks if the outgoing messages are valid (specific domain) or not. If they are it lets them go, else it doesn't send the mail.

Resources