I have setup jenkins server on aws and provided access to only my org public IP.
I want to open it with my organization vpn for some people working from home so he want access the server.
Also jenkins have google auth.
how to setup for this problem
Related
I have build a Express REST API.I tried to deploy aws ec2 instance and did configure the instance public ip point subdomain (hostinger or godaddy) then run subdomain via ec2 instance enable https to the API
I will call the subdomain in React Client it will runs Express API or any possible way to run my express api in subdomain
Anybody can explain step by step or share any resources
I am looking for guide who have experience with Interactive Brokers Client Portal API. The Interactive Brokers CLient Portal API provides a gateway service.
I have tested this IB Gateway in my local and locally it is working fine.
The gateway is running on https://localhost:5000
I want to put this service on the windows server and want to access by server ip.
for example: https://52.xx.xx.12:5000 like this
I also tried solution from this reference Running interactive brokers client portal API in cloud server but not got success
Thanks
You need to set your server IP address in IB gateway setting as a trusted IP, and you should open 5000 port in firewall as well.
Most articles or answers I find deal with proxying a localhost url to a localhost backend server on a different port, or to a non-authenticated remote server (no log in required). However, what I am unable to find is how to generically proxy requests to a remote server that requires authentication.
A common practice in web development is to create multiple instances of the app (beta/dev, integration/test, production, etc.) so you can test and deploy gradually before the code hits production. Each instances has it's own backend server and data that is typically accessible through public urls (e.g. beta.app.com/api).
The difficulty comes when the api requires user authentication to access. Setting up a typical proxy won't work as the credentials from localhost will be different from those of the remote server.
What I want to be able to do is be able to proxy all localhost api calls to one of the remote servers so I don't have to run a backend server locally, or be able to test local code against remote data (great for debugging prod only bugs). What I don't want to have to do is hardcode credentials to the remote server into the proxy, as that won't work for anyone else who runs the app locally (so no hardcoding proxy headers that add auth cookies, etc.).
I image the solution will require more than just a proxy to work, and that's fine. Assume I have full control of both the frontend and backend and can make any changes needed to make this work.
I have an intranet website setup at my house. I'm running under XAMPP. Everything works fine. I'd like to give access to specific users in order for them to test the website (private testing) instead of making it available to the internet. Specifically, I want specific users to have private access to my intranet website and others would be denied access to that site.
I already configured port forwarding on my router. What would be the extra steps I'd need to take?
if the testers have static IPs you can configure ACLs on your router or even on your Server.
if there are dynamic IPs you can create openVPN to your tester's site and use DDNS as remote peer's IP.
hope that helps!
I'm the one who is configuring the server. It has a SVN+SSH as well as an SSL for the company who will be accessing it. I am able to browse AND checkout repos. The firewall has been configured to allow access to another company. They can browse the repos in a browser, but they get an error message when trying to SVN check-out the repo. Error message: "Access to 'https://servernameaddress/path/to/repo' forbidden". Why would they be able to browse the repo in a web browser, but not be able to checkout using an SVN client?
Are they connecting to the internet via a proxy?
If they had a proxy configured in the browser perhaps Tortoise is not using this proxy.