-
Notifications
You must be signed in to change notification settings - Fork 2
Accessing your internal web interfaces
Many times you have to access to some web interface of a internal server in your portal, to a port that is nor public for security reasons, like the solr admin interface.
You can use ssh port redirection but if you have to access to many other ports or to many other software (jenkins, spark, hadoop) is better to use other approach (like add some auth proxy vhost in your frontend to access to these interfaces). In this page we'll show you how to use a socks proxy in a GNU/Linux environment or similar free sophisticated tanks, but you can do something equivalent in Windows or Mac.
apt install autossh
Create some script like:
#!/bin/bash
autossh -f -M 0 -o "ServerAliveInterval 10" -o "ServerAliveCountMax 3" -D localhost:8765 -N ubuntu@your-portal-gateway
and execute it. Let's say that ssh ubuntu@your-portal-gateway
is how access to your portal gateway.
This configure a socks
ssh proxy in your local port 8765. Using this proxy in a browser will redirect all your web petitions as they were accessing from your-portal-gateway
. autossh
maintains that socks proxy open.
You can change your proxy in your computer to use that 8765
but it's better to only use it for some subdomains and use direct Internet connection to the rest. We recommend Proxy SwitchyOmega.
Now we'll configure the extension to automatic use the socks ssh proxy for some of our internal servers (those starting with gbif-es-*
names in the /etc/hosts
or our portal gateway).
With this you can access to these internal interfaces using your proxy and not for the rest of webs.
Index
- Wiki home
- Community
- Getting Started
- Support
- Portals in production
- ALA modules
- Demonstration portal
- Data management in ALA Architecture
- DataHub
- Customization
- Internationalization (i18n)
- Administration system
- Contribution to main project
- Study case