Is there a way to configure a Paypal sandbox IPN for local networks? Since I am testing it on my personal computer I cannot provide a static IP.
PayPal delivers IPNs to a URL that you provide. It has to be reachable by PayPal.
The question doesn't make sense.
I have found a solution to work with paypal sandbox on local networks.
Install ngrok. This creates a public address for your local network so that it can be accessible from outside networks. You can use the ipaddress generated by it to test ipn.
Related
I just configured an NGINX instance on the Jelastic platform.
In my environment's firewall inbound rules there are now a few default rules added.
With source All. (HTTP, HTTPS, ...)
I changed the source of these firewall rules to Local LAN.
So I expect that when I go to my Jelastic public URL in my browser on my own computer, I do not get a website but I'm blocked by the firewall.
This is not happening. I do not want the website to be used from the outside. This environment will host some REST API's and workers running on the inside and only triggered by other environments I have.
Kind regards.
Roel
We recommend following this guide to disable access to your container (CT) from the outside: https://docs.jelastic.com/release-notes-59/#restrict-node-access-via-shared-load-balancer-slb
However, please keep in mind that you'll not be able to access this CT from another CT too.
UPDATE:
little clarification
If "Access via SLB" disabled, the nodes within the layer are inaccessible via SLB (including the Open in Browser button in the dashboard) and return the 403 "Forbidden error" instead of the intended service. Herewith, access via the private network from the other nodes of the environment, access via SSH and access via endpoints from the public network is not affected.
We also want to draw your attention to that described feature is available from the Jelastic PaaS 5.9 release
I'm developing a web application using Laravel hosting on a public cloud. Now, the application can be accessed publicly on the internet via domain address. However, I want to restrict to only users who are connecting to the organization networks to be able to use the application since we do not want the application to be used at home or elsewhere.
At the moment, the organization has 2 places (2 public internet networks) where they must be able to access to the application. Both of them are using home-standard internet where IP address changes every time the internet reconnects. As we do not have static IP addresses, I cannot filter user by using IP address filter. The IP filter rule must be changed every time when the organization network reconnected.
My application already have solid authentication and authorization mechanism and, of course, the users must know this information since they must access the app for work. However, this doesn't meet the requirement.
I have thought about the VPN but it (probably) doesn't not work because if we allow user the access to the VPN, they still be able to access the VPN anywhere and use the application outside the work places. If we restrict the VPN client to access from specific IP address, then when the IP changes, the same problem occurs.
To sum up, I would like to ask for the advice on how to restrict the access of web application, hosted on public internet, to the users that are connecting from the public IP address that can change every time when the internet reconnected. The requirement may sound strange but it is as it is. Please feel free to ask for more details if you want to and have a discussions on the suggestions.
Thank you in advance.
You could setup a client for a dynamic dns service (e.g. dyndns) on the client-side.
Then you could use that on the server-side to always check against current IP using that dns.
As alternative you could bind the website to localhost only and only let it be accessed via an pubkey-enforced SSH tunnel (and make that get auto-established by a script/scheduler on the client side, on a permission level outside of the users' reach, so that they can't take the private key needed for the connection anywhere)
You can use different PHP methods and variables to detect from where the request has been originated. Just whitelist your domains and organizations, and allow only them by adding a middleware.
Additionally, you can generate a token using Laravel Passport or you can create your own mechanism, and then use that token to authenticate if the request is valid or not.
Since the IP changes, you can setup a dynamic dns or as suggested on the comment above.
I currently have a SQL Database and REST API residing on an in house development server. When on the premises my Mac uses a Reverse Proxy (in Apache) to connect and use the REST API on the in house development server. This is to avoid CORS issues. The reverse proxy looks like the following:
ProxyPass /api/ http://192.168.1.250:80/
I wish to move the in house SQL Database and REST API to a Windows Azure Virtual Machine.
Is it possible to do this/is this a viable solution to accessing the REST API remotely? When publishing a website in IIS on a Windows Azure VM access is allowed via a cloudapp.net domain. Is it possible to access the site via an IP address?
I have looked into setting up a VM with a static IP but I am unsure if this would actually solve the above problem - so before spending any more time on this it would be great if someone better versed in this area could chime in!
Any help and guidance is greatly appreciated.
Thanks,
Rich
I have installed a magento extension to connect my magento store to facebook store. I want to test the functionality in localhost before I set it in live server. This is the extension I have installed in local.
http://connect20.magentocommerce.com/community/fbshops
This is the error I am facing with the facebook extension.
Error! You are using local host, or your IP is not accessible from outside, please contact your hosting provider.
Is there any way available to test this facebook module in localserver ?
I am using magento 1.7.
You will need to make your IP accessible to the outside world, this you can do if you have a static IP. You will need to forward all the request to your IP by port forwarding it to the web server.
And you will have to use your External IP Address instead of localhost in magento to check this. You can get your external ip address from here.
I am hosting a website using XAMPP. The website uses PayPal API for Express Checkout. If I move the website to a real hosted server (i.e. www.website.com), the PayPal checkout system will work. If I use it from XAMPP (localhost), it won't even connect to PayPal. How would I make this work from my localhost?
Step 1: Port forwarding. Your router has a public ip (not 127.0.0.1) Configure your router to accept requests from the interwebs.
Step 2. Have a spare domain name? Configure your domain # your registar: Point "A" Record to your newly forwarded IP.
Step 3. Add a fake HTTPS cert http://curl.haxx.se/ca/cacert.pem to the root folder of your XAMPP installation.
Not the end-all, say, all-a guideline. Tricky, but a starting point.
With this approach, you can test Paypal IPN's, use the sandbox, all the good stuff, as well as monkey around with all the other major vendors' api's on your local server.
These links will be helpful for you.
http://demos.ipn-easy.com/Howto/TestEnvironment.aspx
Can I test paypal api's from localhost